On 10/13/2020 12:42 AM, Brian Candler wrote:
The minimum useful scrape time for Prometheus is 2 minutes (120
seconds).
Ah, interesting. The 300 second to staleness is not configurable?
Polling the devices faster is not practical. All of the samples will be
coming out of an existing poller - in some cases it takes ~ 10 minutes
to the poller to complete taking the stats off a single device (limited
by the device management plane's pitiful CPU). We could write our own
cache layer that would allow prometheus to poll, oversampling if
necessary, if that's architecturally better than using the push gateway.
Despite what the docs say, people have reported using prometheus for
long-term storage successfully.
You'd never know it. ;)
However, 8 million series for a single prometheus instance might be
pushing it a bit too much. I would be more comfortable with sharding
across a few smaller instances than having one monster instance.
Any hints on what server specs would be required for an instance that
big? Projecting costs and what scale out is always a bit tricky when
you've never run an application before.
-K
--
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/29383f8f-2af0-61d7-ac58-ae08dcbf35ca%40sontrak.net.
