On 2022-04-19 08:58, Aniket Kulkarni wrote:
Hi,
I have referred below links:
I understand this was a problem with 1.x
https://github.com/prometheus/prometheus/issues/398
I also got this link as a solution
https://promcon.io/2017-munich/talks/staleness-in-prometheus-2-0/
No doubt it's a great session. But I am still not clear as to what
change I have to make and where?
I also couldn't find the prometheus docs useful for this.
I am using following tech stack:
Gatling -> graphite-exporter -> prometheus-> grafana.
I am still facing staleness issue. Please guide me on the solution or
any extra configuration needed?
I am using the default storage system by prometheus and not any
external one.
Could you describe a bit more of the problem you are seeing and what you
are wanting to do?
All time series will be marked as stale if they have not been scraped
for a while, which causes data to stop being returned by queries, which
is important as things like labels will change over time (especially for
things like Kubernetes which include pod names). It is expected that
targets will be regularly scraped, so things shouldn't otherwise
disapear (unless there is an error, which should be visible via
something like the "up" metric).
As the standard staleness interval is 5 minutes it is recommended that
the maximum scrape period should be no more that 2 minutes (to allow for
a failed scrape without the time series being marked as stale).
--
Stuart Clark
--
You received this message because you are subscribed to the Google Groups
"Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/prometheus-users/a97e8140ebdc538c0553192e3dacaf71%40Jahingo.com.
