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

2024-03-12 Thread Alexander Wilke
At the moment I am running the job with name "node_exporter" which has 20 different targets. (instances) With this configuration there should not be any conflict. my idea is to install the prometheus agent on the nodes itself. technically it looks like it work if I use the same job_name on the

[prometheus-users] prometheus agent 2.49.1 - remote_write metrics while disconnected

2024-03-12 Thread Alexander Wilke
Hello, I am running a prometheus server as a central instance. I configured prometheus in agent mode on another system and send the logs via remote_write from agent to central prometheus. This works. I changed the password in web.config.yml on the central server so it does not match for the

Re: [prometheus-users] Import/Export asynchronously

2024-03-12 Thread Ben Kochie
If you can make outbound TCP connections, you can use remote write. On Tue, Mar 12, 2024 at 5:46 PM T F wrote: > Hello, > > I would like to monitor applications runing on several private client > network. > The only way to communicate with them is to use sftp. > We can run promotheus agent on

[prometheus-users] Import/Export asynchronously

2024-03-12 Thread T F
Hello, I would like to monitor applications runing on several private client network. The only way to communicate with them is to use sftp. We can run promotheus agent on client's node. How can I export to a file all collected data for a short period and then import that on our main promotheus

[prometheus-users] Re: disable all alerts for a job

2024-03-12 Thread mel
ah, thank you for the suggestions On Tuesday, March 12, 2024 at 7:13:50 AM UTC-7 Brian Candler wrote: > option 1: filter them out in alertmanager, with an extra routing rule that > matches on the 'job' label and delivers to a null receiver. > option 1b: create a long-lived silence in

[prometheus-users] Re: disable all alerts for a job

2024-03-12 Thread 'Brian Candler' via Prometheus Users
option 1: filter them out in alertmanager, with an extra routing rule that matches on the 'job' label and delivers to a null receiver. option 1b: create a long-lived silence in alertmanager that matches on the 'job' label option 2: drop them in alert_relabel_configs

[prometheus-users] disable all alerts for a job

2024-03-12 Thread mel
How do I disable all alerts for a job without having to modify each alert rule and excluding the job? -- 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] Re: drop all some metrics based on regex

2024-03-12 Thread 'Brian Candler' via Prometheus Users
Thanks. I always forget that labels starting with __ are automatically dropped after target relabelling, but not metric relabelling. On Monday 11 March 2024 at 20:49:42 UTC Ben Kochie wrote: > The other way you can do this is with the "__tmp_keep" pattern. This is > where you positively tag