Yeah I just checked relabelling .I need only few metrics and labels.
ex.container_memory_usage_bytes
container_memory_usage_bytes
container_cpu_usage_seconds_total
On Thursday, April 16, 2020 at 12:39:24 PM UTC+5:30, Brian Candler wrote:
>
> > So can Prometheus handle so much load and monitor each container?
>
> In short yes, although the important figure is the total number of
> *metrics* (servers x containers-per-server x metrics-per-container), and
> this will affect how much resource you need to throw at your prometheus
> server. If it's too much, you may choose to filter the metrics you ingest
> to just the ones of interest, using metric relabelling.
>
> Assuming you are using a modern version of prometheus (2.14 or later) then
> the web interface on port 9090 will tell you the stats you need to know,
> under Status > Runtime & Build Information.
>
> As for grafana "hanging": you probably need to configure your dashboards
> to select a small enough subset of timeseries up-front, e.g. using
> dashboard variables. If you run an initial query which returns thousands
> of timeseries, it will indeed take an extremely long time to (a) return the
> results from prometheus, and (b) render them.
>
--
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/66801fc8-b130-47d0-848e-5944cb79d070%40googlegroups.com.
