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
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. But is there a way to exclude injection of them using the Intrumentation CR.
Our usecase example:
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.
The text was updated successfully, but these errors were encountered:
dkPranav
changed the title
Option to exclude certain ENV variable from auto-instrumentation
Option to exclude certain ENV variables from auto-instrumentation
Nov 15, 2024
These environment variables aren't part of this repository. Transferring to to opentelemetry-operator, which I believe is responsible for setting these.
jack-berg
transferred this issue from open-telemetry/opentelemetry-configuration
Nov 15, 2024
I believe these are the default ENVs injected when
instrumentation.opentelemetry.io/inject-sdk
annotation is added to a PodSpec,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. But is there a way to exclude injection of them using the Intrumentation CR.
Our usecase example:
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.
The text was updated successfully, but these errors were encountered: