[prometheus-users] Re: Prometheus using a large amount of memory when managing storage.

At this point I am the only one running queries. When I have no target defined the memory seems to be flat. When I changed the follow in non-pro it seemed to stabilize the memory usage. --storage.tsdb.max-block-duration 15d --storage.tsdb.min-block-duration 1h I will try copying the binaries

[prometheus-users] Re: Labels replacing

You can use target relabelling, where each target entry can contain both a name and an IP address and you separate them out in relabelling rules. This also lets you generate meaningful instance labels that don't have the

[prometheus-users] Prometheus using a large amount of memory when managing storage.

We have been running prometheus for 3 or 4 years now. In production we have 6 month retention and in non-production we have a retention of 45 days. in production we are capturing 1.8 million metrics with 2,300 targets. In non-prod we are capturing 800 K metrics with 2,200 targets. The

[prometheus-users] Re: Prometheus using a large amount of memory when managing storage.

Look at Status > TSDB Status from the web interface of both systems. In particular, what does the first entry ("Head Stats") show for each system? Do you have any idea of series churn, i.e. how many new series are being created and deleted per hour? (Although if you're scraping a subset of