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

Monitor Tab: Reduce ratePer window #879

Closed
albertteoh opened this issue Feb 9, 2022 · 0 comments · Fixed by #885
Closed

Monitor Tab: Reduce ratePer window #879

albertteoh opened this issue Feb 9, 2022 · 0 comments · Fixed by #885

Comments

@albertteoh
Copy link
Contributor

Requirement - what kind of business use case are you trying to solve?

Reduce confusion in per-second request/error rates in graphs.

Problem - what in Jaeger blocks you from solving the requirement?

The rate duration defaults to 1 hr which can result in quite low rates (e.g. 0.013 requests/sec), which can be confusing.

Proposal - what do you suggest to solve the problem or improve the existing situation?

Online examples of prometheus queries using rate commonly quote a window of 5 mins. As such, changing the ratePer to a smaller window, say, 10m for starters might be a reasonable compromise. It still results in quite a low rate (e.g. 0.08), but it should reach a more expected rate sooner.

The other alternative is to use irate in jaeger-query, however, this only considers the last 2 points in the rate window, and all other information is lost. irate is ideal for a short demo, but in a production environment, I expect rate to be the preferred function.

We can later iterate on whether if this would be useful as a configurable parameter (either through the UI or json config), if not already possible.

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

Successfully merging a pull request may close this issue.

1 participant