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

Add tracer_provider exporters and span_processors #17

Merged
merged 1 commit into from
Dec 2, 2022

Conversation

jack-berg
Copy link
Collaborator

An alternative to #16 which breaks out a separate tracer_provider.exporters block whose keys can be referenced in span processor configuration.

This is related to the suggestion from @srikanthccv here.

Copy link
Collaborator

@codeboten codeboten left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes sense to me, the only question would be whether exporters should be a top level configuration group, but we can always move forward with this and revisit later if we find that commonalities across signals make sense to pull up.

config.yaml Show resolved Hide resolved
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 this pull request may close these issues.

4 participants