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

Trace Quality Metrics #367

Open
yurishkuro opened this issue Sep 1, 2017 · 6 comments
Open

Trace Quality Metrics #367

yurishkuro opened this issue Sep 1, 2017 · 6 comments

Comments

@yurishkuro
Copy link
Member

When deploying a distributed tracing solution like Jaeger in large organizations, especially those whose architectures are composed of many different technologies, there are always questions about how much of the architecture is actually integrated with tracing, what is the quality of the instrumentation, are there microservices that are using stale versions of instrumentation libraries, etc.

Trace Quality engine runs analysis on all traces collected in the backend, inspects then for known completeness and quality problems, and provides summary reports to service owners with suggestions on improving the quality metrics and links to sample traces that exhibit the issues.

image

@jordo1138
Copy link

any idea if it's on the radar for 2018? Thanks

@jpkrohling
Copy link
Contributor

I think this might depend on the data pipeline feature (#414).

@vvvprabhakar
Copy link

Is it available now ? in 1.18.1?

@pavolloffay
Copy link
Member

It has been open-sourced in https://github.com/jaegertracing/jaeger-analytics-flink. However the codebase is not OSS friendly nad it might be difficult to build and deploy.

There is also a new module https://github.com/jaegertracing/jaeger-analytics-java#trace-quality-metrics. It depends only on p8s and grafana. However it's not that advanced as the original app.

@jkowall
Copy link
Contributor

jkowall commented Jan 26, 2021

@yurishkuro You can close this out I believe.

@yurishkuro
Copy link
Member Author

Well, the code is not in a usable state yet. Closing means we're not going to do it imo.

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

No branches or pull requests

6 participants