-
Notifications
You must be signed in to change notification settings - Fork 107
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
feat: allow to reset histograms #305
Comments
Just out of curiosity, what would be the shape of the API? Along with that, do you have a distributed setup? How do you measure the distribution among hosts? |
This issue has been marked as stale because it has been opened 30 days without activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
This issue has been marked as stale because it has been opened 30 days without activity. Remove stale label or comment or this will be closed in 5 days. |
@metcoder95 Sorry for some reason i never say your comment
i've suggested
Yes i don't think it requires something more, it match the underlying implementation used (https://nodejs.org/api/perf_hooks.html#histogramreset)
Yes, prometheus is actually pretty good at re-constructing histogram across different instances |
I'm collecting
runTime
andwaitTime
metrics for my pool with otel:However over the lifetime of the pool, those histogram are never reset so the p99 and p99_9 take a lot of time to get back to a current value since it stores old one. I would like to be able to call
this.workers.runTime.reset()
to clear the buckets after each value collection.If that's something you are okay with, i can make a PR for it
The text was updated successfully, but these errors were encountered: