Set environment variables without injection #990
Labels
area:auto-instrumentation
Issues for auto-instrumentation
Comments
|
This use-case has been discussed in the past, but I cannot find the ticket/PR. I think it makes sense to inject just the SDK config. It could be supported by: instrumentation.opentelemetry.io/inject-sdk: "true"It would inject only core SDK env vars like the exporter, sampler, propagation, resource attributes. https://github.com/open-telemetry/opentelemetry-operator/blob/main/pkg/instrumentation/sdk.go#L100 |
bilbof
added a commit
to bilbof/opentelemetry-operator
that referenced
this issue
Jul 23, 2022
Closes open-telemetry#990. Adds support for injecting SDK environment variables only, without injecting language-specific libraries or config. Usage: ```bash instrumentation.opentelemetry.io/inject-sdk: "true" ```
bilbof
added a commit
to bilbof/opentelemetry-operator
that referenced
this issue
Jul 23, 2022
Closes open-telemetry#990. Adds support for injecting SDK environment variables only, without injecting language-specific libraries or config. Usage: ```bash instrumentation.opentelemetry.io/inject-sdk: "true" ```
bilbof
added a commit
to bilbof/opentelemetry-operator
that referenced
this issue
Jul 23, 2022
Closes open-telemetry#990. Adds support for injecting SDK environment variables only, without injecting language-specific libraries or config. Usage: ```bash instrumentation.opentelemetry.io/inject-sdk: "true" ```
bilbof
added a commit
to bilbof/opentelemetry-operator
that referenced
this issue
Jul 23, 2022
Closes open-telemetry#990. Adds support for injecting SDK environment variables only, without injecting language-specific libraries or config. Usage: ```bash instrumentation.opentelemetry.io/inject-sdk: "true" ```
|
@pavolloffay I've added a PR for this at #1000 |
bilbof
added a commit
to bilbof/opentelemetry-operator
that referenced
this issue
Jul 25, 2022
Closes open-telemetry#990. Adds support for injecting SDK environment variables only, without injecting language-specific libraries or config. Usage: ```bash instrumentation.opentelemetry.io/inject-sdk: "true" ```
bilbof
added a commit
to bilbof/opentelemetry-operator
that referenced
this issue
Jul 25, 2022
Closes open-telemetry#990. Adds support for injecting SDK environment variables only, without injecting language-specific libraries or config. Usage: ```bash instrumentation.opentelemetry.io/inject-sdk: "true" ```
bilbof
added a commit
to bilbof/opentelemetry-operator
that referenced
this issue
Jul 25, 2022
Closes open-telemetry#990. Adds support for injecting SDK environment variables only, without injecting language-specific libraries or config. Usage: ```bash instrumentation.opentelemetry.io/inject-sdk: "true" ```
bilbof
added a commit
to bilbof/opentelemetry-operator
that referenced
this issue
Jul 26, 2022
Closes open-telemetry#990. Adds support for injecting SDK environment variables only, without injecting language-specific libraries or config. Usage: ```bash instrumentation.opentelemetry.io/inject-sdk: "true" ```
bilbof
added a commit
to bilbof/opentelemetry-operator
that referenced
this issue
Jul 26, 2022
Closes open-telemetry#990. Adds support for injecting SDK environment variables only, without injecting language-specific libraries or config. Usage: ```bash instrumentation.opentelemetry.io/inject-sdk: "true" ```
pavolloffay
pushed a commit
that referenced
this issue
Jul 27, 2022
Closes #990. Adds support for injecting SDK environment variables only, without injecting language-specific libraries or config. Usage: ```bash instrumentation.opentelemetry.io/inject-sdk: "true" ```
ItielOlenick
pushed a commit
to ItielOlenick/opentelemetry-operator
that referenced
this issue
May 1, 2024
…#1000) Closes open-telemetry#990. Adds support for injecting SDK environment variables only, without injecting language-specific libraries or config. Usage: ```bash instrumentation.opentelemetry.io/inject-sdk: "true" ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey folks, it would be nice for the Instrumentation CRD to support adding OTEL environment variables to a Pod without injecting the init container / updating libraries and modifying env vars such as
NODE_OPTIONS.My use case is that I have many services written in Go, Rust, C++, etc. which aren't supported by the Instrumentation CRD but which I'd like to configure in the same way.
I could re-use the autoinstrumentation for another language like using an annotation
instrumentation.../language-python: "true"on a Rust application PodSpec, but that feels a bit wrong, and I would expect this not to be supported.Is there a way to set the generated OTEL environment variables on Pods which aren't using a supported language?
The text was updated successfully, but these errors were encountered: