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

tracing: support multiple providers #25347

Open
kyessenov opened this issue Feb 3, 2023 · 1 comment
Open

tracing: support multiple providers #25347

kyessenov opened this issue Feb 3, 2023 · 1 comment
Labels
area/tracing enhancement Feature requests. Not bugs or questions. help wanted Needs help!

Comments

@kyessenov
Copy link
Contributor

To support migration from one sink to another, it would be good to support multiple tracing providers simultaneously. For example, users may want to test out OTel first before turning off zipkin.
@kyessenov kyessenov added enhancement Feature requests. Not bugs or questions. triage Issue requires triage area/tracing and removed triage Issue requires triage labels Feb 3, 2023
@github-actions
Copy link

github-actions bot commented Mar 5, 2023

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale stalebot believes this issue/PR has not been touched recently label Mar 5, 2023
@kyessenov kyessenov added help wanted Needs help! and removed stale stalebot believes this issue/PR has not been touched recently labels Mar 6, 2023
@holycheater holycheater mentioned this issue Apr 6, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/tracing enhancement Feature requests. Not bugs or questions. help wanted Needs help!
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kyessenov