Configure OTel tracing endpoint with custom headers
⚙️Configuration🏬Self-hosted🧩Integrations❓Question✅Solved
Hello ZITADEL team,
Context: we are running Zitadel v4.10.1 self hosted in nonprod and production usage on AWS EKS, using latest HelmChart 9.17.0
We have our own Loki / Grafana / Tempo / Prometheus stack as well.
Our Tempo instance requires username/password with
Exploring Zitadel instrumentation configuration options (
I've seen
Taking a look at the current config from main, it guess our values would look like:
https://github.com/zitadel/zitadel/blob/main/cmd/defaults.yaml
Question: is it supported to define custom headers for the tracing endpoint?
Context: we are running Zitadel v4.10.1 self hosted in nonprod and production usage on AWS EKS, using latest HelmChart 9.17.0
We have our own Loki / Grafana / Tempo / Prometheus stack as well.
Our Tempo instance requires username/password with
AuthorizationExploring Zitadel instrumentation configuration options (
Instrumentation.TraceI've seen
Telemetry.HeadersTaking a look at the current config from main, it guess our values would look like:
https://github.com/zitadel/zitadel/blob/main/cmd/defaults.yaml
Question: is it supported to define custom headers for the tracing endpoint?
