News for hackers. Stuff that matters.

A comment on Monitoring Cloudflare's edge network with Prometheus. Parent comment

Re:Monitoring Cloudflare's edge network with Prometheus by user5994461 on Sunday September 24, 2017 @05:57PM (#15326696)
We are both describing the same thing, you end up with "agents" spread on various systems to collect the metrics you are interested in, which is the point I wanted to outline.

They can be called agents, exporters, collectors, whatever, the name is not important, the design pattern is.

A system that would be exclusively pull-based from the prometheus server does not work practically.

[ Parent | on HN ]
Re:Monitoring Cloudflare's edge network with Prometheus by sagichmal on Monday September 25, 2017 @04:22AM (#15328780)
No, you don't generally end up with agents or exporters everywhere. You might have node_exporter running on each host to collect system metrics (load, iops, etc.) but those are exceptions. The rule is that the software under instrumentation is mounting /metrics endpoints and exposing Prometheus metrics to the Prometheus server directly.

Unless you take the presence of node_exporter to invalidate the premise (which would be stupid) a system that's exclusively pull-based is entirely practical.

[ Parent | on HN ]