Skip to content
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

Inject OTEL environment variables into containers #4152

Closed
ngehrsitz opened this issue Dec 3, 2024 · 2 comments
Closed

Inject OTEL environment variables into containers #4152

ngehrsitz opened this issue Dec 3, 2024 · 2 comments
Labels
feature request Request for a non-existing feature

Comments

@ngehrsitz
Copy link

Is your feature request related to a problem? Please describe.
At the moment you need to manually set the OTEL_ environment variables to use OpenTelemetry SDK instrumentation in your application.
But the required information is already available to a container in /var/lib/dynatrace/enrichment/endpoint/endpoint.properties and /var/lib/dynatrace/enrichment/dt_metadata.properties if the annotations oneagent.dynatrace.com/inject and metadata-enrichment.dynatrace.com/inject are enabled.
This works by having the operator create the dynatrace-metadata-enrichment-endpoint secret and then mounting that as a file to the container. This means all of the required information is already present in the container, but requires additional code in the application to read this custom format.

Describe the solution you'd like
A better approach would be for the operator to create a secret with the credentials or add them to the existing secret. This would make it possible to inject the credentials into a container as the standardized OTEL_ environment variables. This feature should of course also be enabled separately using a feature flag.

Describe alternatives you've considered
The current alternative to this is to either manually create such a kubernetes secret or adapt your application to read the dynatrace format which is rather inconvenient.

@luhi-DT luhi-DT added the feature request Request for a non-existing feature label Dec 4, 2024
Copy link
Contributor

github-actions bot commented Dec 4, 2024

Thank you for opening a Dynatrace Operator Issue. We've identified and tagged the issue as a "Feature request".

Dynatrace reviews feature requests in the Dynatrace community rather than Github. This helps our team consolidate, rank, and prioritize important input like yours.

Please search for similar requests, collaborate, and ask questions using the link above. Remember to add the labels "kubernetes" and "dynatrace-operator" to help get the attention you deserve.

Thanks for your help!

@github-actions github-actions bot closed this as completed Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Request for a non-existing feature
Projects
None yet
Development

No branches or pull requests

2 participants