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
Is your feature request related to a problem? Please describe.
We are setting OTEL_SERVICE_NAME in the container image Dockerfile across many deployments.
We don't want the auto-instrumentation to inject this OTEL_SERVICE_NAME, so is there a way exclude injection of certain Env variables.
Describe the solution you'd like
I believe these are the default ENVs injected when instrumentation.opentelemetry.io/inject-sdk annotation is added to a PodSpec,
Is there a way to exclude injection of them using the Intrumentation CR.
Describe alternatives you've considered
I understand that we can explicitly pass these ENVs in the pod directly to override the default values. and also add an annotation to add custom attributes.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Component(s)
auto-instrumentation
Is your feature request related to a problem? Please describe.
We are setting OTEL_SERVICE_NAME in the container image Dockerfile across many deployments.
We don't want the auto-instrumentation to inject this OTEL_SERVICE_NAME, so is there a way exclude injection of certain Env variables.
Describe the solution you'd like
I believe these are the default ENVs injected when instrumentation.opentelemetry.io/inject-sdk annotation is added to a PodSpec,
Is there a way to exclude injection of them using the Intrumentation CR.
Describe alternatives you've considered
I understand that we can explicitly pass these ENVs in the pod directly to override the default values. and also add an annotation to add custom attributes.
Additional context
No response
The text was updated successfully, but these errors were encountered: