Skip to content

[TRI-5390] Ignore any OTEL_ env vars users set (they mess up our tracing/logging) #2044

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
matt-aitken opened this issue May 13, 2025 · 1 comment

Comments

@matt-aitken
Copy link
Member

matt-aitken commented May 13, 2025

It's currently possible for users to to set the OTEL_ env vars when deploying, like OTEL_EXPORTER_OTLP_ENDPOINT and OTEL_EXPORTER_OTLP_HEADERS.

This is mostly when using our sync env vars extensions.

This messes things up because we need these to be set to specific values and the user provided ones are overriding ours. The result is that no logs get sent to us and the Run page is empty.

Fix

Ignore any env vars starting OTEL_, I think we already have an array of env vars to ignore. Don't throw an error because it will make the sync script painful for users.

TRI-5390

@matt-aitken matt-aitken changed the title Ignore any OTEL_ env vars users set (they mess up our tracing/logging) [TRI-5390] Ignore any OTEL_ env vars users set (they mess up our tracing/logging) May 13, 2025
@siddharthsharma94
Copy link

Had this exactly happen here, and explained my findings in the issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants