I agree, the best practice here is to have Prometheus as close to the
targets as possible. This way any WAN links, VPNs, or proxies are not
monitored as a side effect.
The remote write feature is designed for this. It can stream data to a
central service like Cortex or Thanos. Or a hosted service
Hi,
On 2020-12-14 11:24, Patrick Macdonald wrote:
If we have a Prometheus server on site-A and an arbitrary number of
client sites, each with hardware we might want monitor, is there best
practice for how to achieve this?
I'm assuming pushgateway isn't the correct use-case here? Is the only
On 2020-12-14 10:24, Patrick Macdonald wrote:
This might be more of a general networking question than a Prometheus
question, but I thought I'd ask anyway.
If we have a Prometheus server on site-A and an arbitrary number of
client sites, each with hardware we might want monitor, is there best
This might be more of a general networking question than a Prometheus
question, but I thought I'd ask anyway.
If we have a Prometheus server on site-A and an arbitrary number of client
sites, each with hardware we might want monitor, is there best practice for
how to achieve this?
I'm
4 matches
Mail list logo
