The gauge issue and having to restart prom-aggregation-gateway to delete stale metrics was a no go for our use case. That's why I created the *Metrics Accumulator* https://github.com/bpoole6/metrics-accumulator.
The Metrics Accumulator doesn't add gauge values together, it instead takes the latest value pushed for a gauge (There is some customization here <https://github.com/bpoole6/metrics-accumulator/tree/main#gauges>). I also made it where your metrics are partitioned into what I call *metric groups*. Using the service discovery feature within Prometheus it can scrape different metrics path on the same host to read the separate group... Or you could just dump it all in metric group and just scrape that. It also has a *TTL* for your metrics. On Thursday, June 28, 2018 at 3:54:58 PM UTC-4 Björn Rabenstein wrote: > As Ben said... > > The first non-goal listed in > https://github.com/prometheus/pushgateway#non-goals is dealing with > the topic. > > The reason why we don't have any "native" support for distributed > counters within the Prometheus Github org is mostly that it is hard to > get right. I would try to avoid being in a situation where you need > distributed counting, but I know that's not always an option. > > Efforts like https://github.com/weaveworks/prom-aggregation-gateway > will create some experience with that in the Prometheus context. > Perhaps we will eventually have an "official" story how to do it. > -- 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 prometheus-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/aab2317e-3a6d-49aa-9372-17429b42189an%40googlegroups.com.
