Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,467,449
Community Members
 
Community Events
177
Community Groups

Prometheus Exporter apps and Histograms

In this article we will talk how to use histograms in Prometheus Exporter apps(Jira, Confluence, Bitbucket, Bamboo).

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):

Screenshot 2020-10-12 at 18.52.22.png

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:

  1. jira_request_duration_on_path_count - contains the number of times the event happened. Here is an example:

Screenshot 2020-10-12 at 18.58.12.png

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:

Screenshot 2020-10-12 at 19.02.05.png

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:

This image has an empty alt attribute; its file name is Screenshot-2020-10-12-at-19.02.05-1024x372.png

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.

 

0 comments

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events