You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've learned the semantic-conventions, and found that no matter http.server.xxx or rpc.server.xxx, there's no metrics for counting the request total. I'm curious about the reason. Like we have http.server.request.duration histogram and http.server.active_requests updowncounter, but don't have http.server.request.total count, why is that? Most people care about the qps which requires the xx.total metrics, but we don't have that, I don't know if it's designed to be so, and why
The text was updated successfully, but these errors were encountered:
hi @caibirdme! the total is available via the http.server.request.duration histogram, does this work for you?
Could you elaborate more please? How the histogram "http.server.request.duration" that measures request duration can be transformed into a counter metric? So that it can be calculated the number of requests per second (rps) for each http.target?
I've learned the semantic-conventions, and found that no matter
http.server.xxx
orrpc.server.xxx
, there's no metrics for counting the request total. I'm curious about the reason. Like we havehttp.server.request.duration
histogram andhttp.server.active_requests
updowncounter, but don't havehttp.server.request.total
count, why is that? Most people care about the qps which requires thexx.total
metrics, but we don't have that, I don't know if it's designed to be so, and whyThe text was updated successfully, but these errors were encountered: