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

Default SDK Configuration mechanisms #390

Closed
jkwatson opened this issue Dec 16, 2019 · 2 comments · Fixed by #439
Closed

Default SDK Configuration mechanisms #390

jkwatson opened this issue Dec 16, 2019 · 2 comments · Fixed by #439
Assignees

Comments

@jkwatson
Copy link
Contributor

The default SDK should have a specified mechanism for configuration. This issue is not to track the specification of what is configurable, but rather how configuration should be made available to SDK users.

In general, the underlying mechanism should be programmatic. Every piece of the default SDK that requires configuration should have that configuration exposed to code. Declarative options (eg. JSON, YAML, env vars, etc) can then be built on top of that programmatic mechanism, as appropriate to the language of the SDK.

@jkwatson
Copy link
Contributor Author

Note: I am working on a PR to provide the skeleton of this specification.

@mwear
Copy link
Member

mwear commented Jan 23, 2020

Ruby has a streamlined way to configure the SDK. I think it is similar to what you are proposing here. Take a look at this PR for examples: open-telemetry/opentelemetry-ruby#171.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants