-
Notifications
You must be signed in to change notification settings - Fork 33
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
Add new http default metrics #65
Comments
Hi. Do you mean "total" in general, not per route? In general all those metrics are available through Prometheus query. For rps/rpm you can use Do those promql calculations cover your case? Or you have something specific? |
My case (platformatic) is specific, but it doesn't matter. Actually, you're right. Especially about rate metrics. If we talk about metrics like failure rate, I will have to specify all possible successful status codes and all failure status codes in the prom request. I thought it could be done much simpler in the code. WDYT? |
@ivan-tymoshenko for error codes, there's an option to group them https://github.com/SkeLLLa/fastify-metrics/blob/master/docs/fastify-metrics.iroutemetricsconfig.groupstatuscodes.md. Also you can use regex syntax in promql label matching. |
|
If I understood correctly, you can use https://prometheus.io/docs/prometheus/latest/querying/functions/#histogram_quantile Does this cover your case? PS: Btw, those cases you've described above could be a part of docs for this repo, e.g. we can add some "how-to" recopies. |
@SkeLLLa What do you think about adding new HTTP-related default metrics like total req count, req per sec, req per min, failure req count?
You already have a lot of what it takes to support these metrics: ignoring http methods/routes, subscriptions on fastify hooks, gathering status codes, etc.
The text was updated successfully, but these errors were encountered: