Summary
When OpenTelemetry tracing is configured via OTEL_* environment variables (Option 2 or Option 3 from the observability architecture), these settings are currently not visible through the LCORE v1/config endpoint. This makes it difficult for administrators to:
- Verify which tracing configuration is active
- Diagnose tracing-related problems
- Understand the effective OpenTelemetry configuration at runtime
Proposed Solution
Collect all environment variables with the OTEL_ prefix and inject them into the v1/config response model, providing administrators visibility into the active tracing configuration alongside other LCORE settings.
Note: As OTEL_* environment variables are read at process startup, any configuration changes require a service restart/redeployment to take effect. This should be clearly communicated in the config endpoint response or documentation.
Related
Summary
When OpenTelemetry tracing is configured via
OTEL_*environment variables (Option 2 or Option 3 from the observability architecture), these settings are currently not visible through the LCOREv1/configendpoint. This makes it difficult for administrators to:Proposed Solution
Collect all environment variables with the
OTEL_prefix and inject them into thev1/configresponse model, providing administrators visibility into the active tracing configuration alongside other LCORE settings.Note: As
OTEL_*environment variables are read at process startup, any configuration changes require a service restart/redeployment to take effect. This should be clearly communicated in the config endpoint response or documentation.Related