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.

Sign up for GitHub

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

Jump to bottom

Support using multiple tracer instances #2431

Open
ahmed-mez opened this issue Dec 13, 2023 · 1 comment
Open

Support using multiple tracer instances #2431

ahmed-mez opened this issue Dec 13, 2023 · 1 comment
Labels
enhancement quick change/addition that does not need full team approval proposal more in depth change that requires full team approval

Comments

@ahmed-mez
Copy link
Contributor

Opening this issue on behalf of @iamricard

Currently there can be only one tracer instance, this doesn't work in advanced scenarios where a traced service generates traces for a different service. Ideally, like in otel Go SDK and other dd tracers, the user could hold 2 or more tracer instances to configure them differently (e.g different service name, sampling rate etc).
@ahmed-mez ahmed-mez added enhancement quick change/addition that does not need full team approval proposal more in depth change that requires full team approval labels Dec 13, 2023
@ahmed-mez
Copy link
Contributor Author

Another potential use-case is sending traces to different agents.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement quick change/addition that does not need full team approval proposal more in depth change that requires full team approval
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ahmed-mez