Helm chart: make the OTLP trace endpoint configurable (otelEndpoint) #186

Closed
opened 2026-09-28 12:31:37 +00:00 by not · 0 comments
Contributor

The chart hard-codes OTEL_EXPORTER_OTLP_ENDPOINT: http://tempo:4317. The chart's own tempo workload is off by default, so on the labs cluster every trace export fails, and each failure is counted in dotnet_exceptions_total.

Change: add an otelEndpoint chart value (default: unchanged, http://tempo:4317) and let deploy.yaml override it from the repo variable OTEL_ENDPOINT, e.g. the monitoring stack's http://tempo.monitoring.svc:4317.

Done when: helm template --set otelEndpoint=X renders X into the otel env group, and deploy passes it through when the variable is set.

The chart hard-codes `OTEL_EXPORTER_OTLP_ENDPOINT: http://tempo:4317`. The chart's own `tempo` workload is off by default, so on the labs cluster every trace export fails, and each failure is counted in `dotnet_exceptions_total`. **Change:** add an `otelEndpoint` chart value (default: unchanged, `http://tempo:4317`) and let `deploy.yaml` override it from the repo variable `OTEL_ENDPOINT`, e.g. the monitoring stack's `http://tempo.monitoring.svc:4317`. **Done when:** `helm template --set otelEndpoint=X` renders X into the otel env group, and deploy passes it through when the variable is set.
not added this to the Iteration 6 — Production Posture milestone 2026-09-28 12:31:37 +00:00
not added the type:chorearea:infra labels 2026-09-28 12:31:37 +00:00
not closed this issue 2026-09-28 13:47:48 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: eho/register-referentie#186