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 upMetrics within prometheus is not real time #1462
Comments
This comment has been minimized.
This comment has been minimized.
|
It sounds like you're running into a staleness issue, as old timeseries that are no longer exported are still considered for 5 minutes. I'd suggest alerting on something that represents direct user experience, rather than trying to catch every possible failure mode such as a drop in clients. |
brian-brazil
added
the
question
label
Mar 4, 2016
This comment has been minimized.
This comment has been minimized.
|
thanx -query.staleness-delta 5s is solved my issue |
ArtemChekunov
closed this
Mar 4, 2016
This comment has been minimized.
This comment has been minimized.
|
I'd strongly advise against dropping |
This comment has been minimized.
This comment has been minimized.
fuzzyami
commented
Nov 27, 2016
|
@brian-brazil what would you consider a safe minimum? 1m? |
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. |
ArtemChekunov commentedMar 4, 2016
I made a bunch with consul, consul_exporter and prometheus.
After that i made alert rule:
but in case when consul client is down the alert is worked out only after ~5m
P.S. consul_exporter returns data correctly