What is the preferred setup for deploying OpenTelemetry on a Kubernetes cluster? Is OpenTelemetry the choice today?

I am running a few projects on a minimal Hetzner K3S cluster and just want some cheap easy observability to store logs, reduce log noise and instead rely on counters/metrics without paying an arm and a leg.

Languages used are Rust, Javascript and Python mostly.

▲

jitl 2 days ago | parent | next [-]

Otel collector or complete Otel stack with data storage and ui etc?

The collector is a helm chart, someone on my project added it to our K8s clusters last week. It was like 30 lines of YAML/Terraform in total. Logs, trace forwarding, Prometheus scraping. That bit is easy.

Idk about deploying the ui/storage. I’ve used Grafana Loki stuff in Docker Compose locally without much head scratching for local development.

https://github.com/grafana/docker-otel-lgtm

	▲	ViewTrick1002 2 days ago \| parent [-]
		Was thinking storage and UI. Making something useful of the work spent collecting the information!

▲

nijave 2 days ago | parent | prev [-]

Not sure about preferred but Jaeger is pretty simple for tracing only. Hyperdx looks interesting but brings in both Mongo and Clickhouse which imo is pretty heavy

Native k8s logs + Prometheus is probably more on the lighter weight side but you don't get traces. You could find some middle ground using the otel collector to extract trace metrics so you get RED metrics but you wouldn't have full traces