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

Specify configuration mechanism for native instrumentations #3535

Closed
estolfo opened this issue Jun 5, 2023 · 0 comments · Fixed by #4128
Closed

Specify configuration mechanism for native instrumentations #3535

estolfo opened this issue Jun 5, 2023 · 0 comments · Fixed by #4128
Labels
sig-issue spec:miscellaneous For issues that don't match any other spec label

Comments

@estolfo
Copy link

estolfo commented Jun 5, 2023

Having Open Telemetry instrumentation natively in libraries has the advantage of keeping ownership of the instrumentation with the library authors; it's a more sustainable way of maintaining instrumentations and is preferable to auto-instrumentations contributed to the language OTel projects.
With that said, there is no specified mechanism for defining and reading configuration for native instrumentations. This issue is meant to propose writing one.

As we discussed in the Specification SIG on 23 May, this may be a discussion for the Configuration SIG and we'd like to pull in opinions from language groups on current conventions.
For example, environment variables are used in Ruby OTel native instrumentations with the formats:
OTEL_RUBY_INSTRUMENTATION_${name}_ENABLED
OTEL_RUBY_INSTRUMENTATION_${name}_CONFIG_OPTS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig-issue spec:miscellaneous For issues that don't match any other spec label
Development

Successfully merging a pull request may close this issue.

3 participants