Comments on: Foiled by the Firewall: A Tale of Transition From Prometheus to VictoriaMetrics https://www.percona.com/blog/foiled-by-the-firewall-a-tale-of-transition-from-prometheus-to-victoriametrics/ Fri, 04 Dec 2020 16:49:33 +0000 hourly 1 https://wordpress.org/?v=6.5.2 By: Steve Hoffman https://www.percona.com/blog/foiled-by-the-firewall-a-tale-of-transition-from-prometheus-to-victoriametrics/#comment-10972887 Fri, 04 Dec 2020 16:49:33 +0000 https://www.percona.com/blog/?p=72881#comment-10972887 In reply to Ben Kochie.

If our goal was purely resolving the Push vs Pull model, yes I’m sure that project could have worked just fine but there was more we were trying to resolve with one effort. PMM Server requires pretty sizable resources even for a small number of nodes monitored and Prometheus is always the worst offender inside our container from a RAM perspective (not saying it’s Prometheus that’s to blame at all, just how we’re using it) so seeing the reduced memory consumption under the same loads and better storage compression was an instant win. We also suffer from “holes” in the data during network blips/outages, restarts, or overloaded systems so eventually unlocking the client-side caching will help eliminate that as well. In the end there were lots of options evaluated but this route seemed to give us the biggest bang for our development dollar.

]]>
By: Ben Kochie https://www.percona.com/blog/foiled-by-the-firewall-a-tale-of-transition-from-prometheus-to-victoriametrics/#comment-10972881 Wed, 02 Dec 2020 17:55:38 +0000 https://www.percona.com/blog/?p=72881#comment-10972881 Wouldn’t it have been easier to implement PushProx? This is the officially supported, lightweight, reverse agent for “dial home” situations.

https://github.com/prometheus-community/PushProx

]]>