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

Tempo Support - Rename to Tracing instead of Jaeger when applicable #6537

Closed
Tracked by #6538
josunect opened this issue Aug 30, 2023 · 0 comments · Fixed by #6662
Closed
Tracked by #6538

Tempo Support - Rename to Tracing instead of Jaeger when applicable #6537

josunect opened this issue Aug 30, 2023 · 0 comments · Fixed by #6662
Assignees
Labels
backlog Triaged Issue added to backlog enhancement This is the preferred way to describe new end-to-end features. sub-task Ties an issue to an epic

Comments

@josunect
Copy link
Contributor

This is a refactoring task to use Tracing instead of Jaeger for types and package names because there was included support for other than Jaeger trace providers (Tempo at the moment).

Please note, Tempo client reads the traces in OpenTelementry format and they are converted into Jaeger Traces, so in case of a Jaeger trace types the rename is not applicable.

Some examples:

@josunect josunect added enhancement This is the preferred way to describe new end-to-end features. sub-task Ties an issue to an epic labels Aug 30, 2023
@jshaughn jshaughn added the backlog Triaged Issue added to backlog label Aug 30, 2023
@josunect josunect changed the title Tempo Support - Rename to Tracing insted of Jaeger when applicable Tempo Support - Rename to Tracing instead of Jaeger when applicable Sep 18, 2023
@josunect josunect self-assigned this Sep 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Triaged Issue added to backlog enhancement This is the preferred way to describe new end-to-end features. sub-task Ties an issue to an epic
Projects
Development

Successfully merging a pull request may close this issue.

2 participants