[prometheus-users] Re: Best practive: "job_name in prometheus agent? Same job_name allowed ?

2024-03-15 Thread 'Brian Candler' via Prometheus Users
> What would you recommend in a situation with several hundredes or thousands of servers or systems within a kubernetes cluster which should have the node_exporter installed. I would just scrape them normally, using service discovery to identify the nodes to be scraped. Implicitly you're

[prometheus-users] Re: Best practive: "job_name in prometheus agent? Same job_name allowed ?

2024-03-14 Thread Alexander Wilke
Thanks for your response. What would you recommend in a situation with several hundredes or thousands of servers or systems within a kubernetes cluster which should have the node_exporter installed. my idea was to install the node_exporter + prometheus agent. agent scrapes local node_exporter

[prometheus-users] Re: Best practive: "job_name in prometheus agent? Same job_name allowed ?

2024-03-14 Thread 'Brian Candler' via Prometheus Users
As long as all the time series have distinct label sets (in particular, different "instance" labels), and you're not mixing scraping with remote-writing for the same targets, then I don't see any problem with all the agents using the same "job" label when remote-writing. On Tuesday 12 March