Observed at v3.9.2
Two Jaeger config options have a CLI flag whose name diverges from the env var name. All other --traces-exporter-jaeger-* options keep exporter in both:
| CLI flag |
env var |
--traces-exporter-jaeger-agent-host |
INFLUXDB3_TRACES_EXPORTER_JAEGER_AGENT_HOST |
--traces-exporter-jaeger-agent-port |
INFLUXDB3_TRACES_EXPORTER_JAEGER_AGENT_PORT |
--traces-exporter-jaeger-service-name |
INFLUXDB3_TRACES_EXPORTER_JAEGER_SERVICE_NAME |
--traces-exporter-jaeger-trace-context-header-name |
INFLUXDB3_TRACES_EXPORTER_JAEGER_TRACE_CONTEXT_HEADER_NAME |
--traces-jaeger-debug-name |
INFLUXDB3_TRACES_EXPORTER_JAEGER_DEBUG_NAME |
--traces-jaeger-tags |
INFLUXDB3_TRACES_EXPORTER_JAEGER_TAGS |
--traces-jaeger-max-msgs-per-second |
INFLUXDB3_TRACES_JAEGER_MAX_MSGS_PER_SECOND |
Source:
core/trace_exporters/src/lib.rs defines flag --traces-jaeger-debug-name with env TRACES_EXPORTER_JAEGER_DEBUG_NAME, and flag --traces-jaeger-tags with env TRACES_EXPORTER_JAEGER_TAGS.influxdb3_startup/src/env_compat.rs::ENV_ALIASES then aliases the legacy names to INFLUXDB3_TRACES_EXPORTER_JAEGER_DEBUG_NAME and INFLUXDB3_TRACES_EXPORTER_JAEGER_TAGS.
Why it matters
The mismatch is easy to misread; it has already produced a docs error (since corrected in influxdata/docs-v2#7182) and a downstream Helm-chart error (influxdata/helm-charts#783, fix in #786).
Suggested resolution
Pick one shape and use it consistently. Either:
- Rename the flags to
--traces-exporter-jaeger-debug-name and --traces-exporter-jaeger-tags (matches the env names and the rest of the family), keeping the current names as deprecated aliases for one release.
- Rename the env vars to
INFLUXDB3_TRACES_JAEGER_DEBUG_NAME and INFLUXDB3_TRACES_JAEGER_TAGS, with current names aliased.
(1) is probably less disruptive — env vars are referenced by Helm charts, systemd units, and CI configs in the wild; the flags are more often typed by humans.
Refs
Observed at v3.9.2
Two Jaeger config options have a CLI flag whose name diverges from the env var name. All other
--traces-exporter-jaeger-*options keepexporterin both:--traces-exporter-jaeger-agent-hostINFLUXDB3_TRACES_EXPORTER_JAEGER_AGENT_HOST--traces-exporter-jaeger-agent-portINFLUXDB3_TRACES_EXPORTER_JAEGER_AGENT_PORT--traces-exporter-jaeger-service-nameINFLUXDB3_TRACES_EXPORTER_JAEGER_SERVICE_NAME--traces-exporter-jaeger-trace-context-header-nameINFLUXDB3_TRACES_EXPORTER_JAEGER_TRACE_CONTEXT_HEADER_NAME--traces-jaeger-debug-nameINFLUXDB3_TRACES_EXPORTER_JAEGER_DEBUG_NAME--traces-jaeger-tagsINFLUXDB3_TRACES_EXPORTER_JAEGER_TAGS--traces-jaeger-max-msgs-per-secondINFLUXDB3_TRACES_JAEGER_MAX_MSGS_PER_SECONDSource:
core/trace_exporters/src/lib.rsdefines flag--traces-jaeger-debug-namewith envTRACES_EXPORTER_JAEGER_DEBUG_NAME, and flag--traces-jaeger-tagswith envTRACES_EXPORTER_JAEGER_TAGS.influxdb3_startup/src/env_compat.rs::ENV_ALIASESthen aliases the legacy names toINFLUXDB3_TRACES_EXPORTER_JAEGER_DEBUG_NAMEandINFLUXDB3_TRACES_EXPORTER_JAEGER_TAGS.Why it matters
The mismatch is easy to misread; it has already produced a docs error (since corrected in influxdata/docs-v2#7182) and a downstream Helm-chart error (influxdata/helm-charts#783, fix in #786).
Suggested resolution
Pick one shape and use it consistently. Either:
--traces-exporter-jaeger-debug-nameand--traces-exporter-jaeger-tags(matches the env names and the rest of the family), keeping the current names as deprecated aliases for one release.INFLUXDB3_TRACES_JAEGER_DEBUG_NAMEandINFLUXDB3_TRACES_JAEGER_TAGS, with current names aliased.(1) is probably less disruptive — env vars are referenced by Helm charts, systemd units, and CI configs in the wild; the flags are more often typed by humans.
Refs