Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upthe quantile line of prometheus_remote_storage_send_latency_seconds has a wrong value. #1796
Comments
This comment has been minimized.
This comment has been minimized.
|
The baseline might be right, but the problem here is the rounding to full seconds. I'll fix the latter, and then we'll see how the baseline looks then. |
beorn7
added a commit
that referenced
this issue
Jul 7, 2016
beorn7
referenced this issue
Jul 7, 2016
Merged
Consistently use the `Seconds()` method for conversion of durations #1797
fabxc
closed this
in
#1797
Jul 7, 2016
This comment has been minimized.
This comment has been minimized.
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
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.
guanglinlv commentedJul 7, 2016
What did you do?
config the
--storage.remote.timeoutto5s, keep the prometheus running, take a look theprometheus_remote_storage_send_latency_seconds.What did you expect to see?
any line of
prometheus_remote_storage_send_latency_secondshas a value between 0 and 5sWhat did you see instead? Under which circumstances?
the
quantile=0.99line has a value from 1 to 6s.Environment
System information:
Linux 3.10.0-229.el7.x86_64 x86_64Prometheus version: