You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
Uh oh!
There was an error while loading. Please reload this page.
It's currently possible for users to to set the
OTEL_
env vars when deploying, likeOTEL_EXPORTER_OTLP_ENDPOINT
andOTEL_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
The text was updated successfully, but these errors were encountered: