Skip to content
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

[Question]How to understand prometheus_remote_storage_sedn_latency_seconds? #1666

Closed
guanglinlv opened this Issue May 26, 2016 · 5 comments

Comments

Projects
None yet
2 participants
@guanglinlv
Copy link

guanglinlv commented May 26, 2016

hi, i'm a little poor on the histogram and quantile slot, what's the graph means ?

sedn_latency

thanks a lot.

@grobie

This comment has been minimized.

Copy link
Member

grobie commented May 26, 2016

In Prometheus we usually use 100-quantiles also called percentiles. They represent the range of values in 100 equally sized groups.

In the example above the latency of all calls to the OpenTSDB remote storage is recorded in seconds. The 0.5 quantile means 50% of all calls took at most $value seconds, 0.9 means 90% of all calls took at most $value seconds, etc. So at the end of the time range you can see that 90% of all calls to OpenTSDB were not slower than 1s.

@guanglinlv

This comment has been minimized.

Copy link
Author

guanglinlv commented May 26, 2016

oh, percentiles is fit for me. is it means that we don't need the statistic of sends in various time region [0.1,0.5,1,2,5]s? named like prometheus_remote_storage_send_latency_seconds_bucket. prometheus will do the statistic internal and calculate it to the percentiles.

thanks @grobie .

@grobie

This comment has been minimized.

Copy link
Member

grobie commented May 26, 2016

The difference are summaries (quantile labels) vs. histograms (_bucket metrics). Read more about the differences here: https://prometheus.io/docs/practices/histograms/

@guanglinlv

This comment has been minimized.

Copy link
Author

guanglinlv commented Jun 13, 2016

thanks. closing it.

@guanglinlv guanglinlv closed this Jun 13, 2016

@lock

This comment has been minimized.

Copy link

lock bot commented Mar 24, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 24, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.