I will use the jira_request_duration_on_path metric as an example, but you can apply the same principles to all histogram metrics.
Here is how the metric looks in the documentation (https://confluence.cprime.io/display/CADS/PE+-+Using+Prometheus+Exporter+for+Jira):
As you can see in the second column (the Type column) it is written that the type of the metric is Histogram.
How to query the metric?
Any histogram metric contains three metrics inside: count, sum and bucket. That is why you can query this metric like this:
Let's take the browse path. We can see that the browse path was requested 4 times.
2. jira_request_duration_on_path_sum - the sum of event values.
Here is an example:
As you can see that our 4 requests for the browse path took 1.083622161 seconds to complete.
3. jira_request_duration_on_path_bucket - shows buckets for the metric.
Here is an example:
The "le" label means "less than the number of seconds" and it shows how many requests had duration less than the specified amount of time. For example, 0 requests were executed for less than 0.005 seconds. But 2 requests were executed for less than 0.25 seconds and 4 requests were executed for less than 0.5 seconds (those 4 requests include the two requests which were executed for less than 0.25 seconds).
As you can see there have been only 4 requests and jira_request_duration_on_path_count also confirms it.
Alexey Matveev _Appfire_Community Leader
This month the spotlight is on AppLiger. We caught up with Pavel Pavlovsky, CEO and Product Manager, to learn how the company started and what fuels the team's creativity. Atlassian:...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events