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 · 2 comments

Comments

Projects
None yet
3 participants
@yurishkuro
Member

yurishkuro commented Sep 1, 2017

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

This comment has been minimized.

jordo1138 commented May 11, 2018

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

@jpkrohling

This comment has been minimized.

Member

jpkrohling commented May 11, 2018

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

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