[prometheus-users] Re: Hisorical data

On Monday, 26 September 2022 at 13:10:57 UTC+1 chembakay...@gmail.com wrote: > *Query:* up{instance=~"$unreachbale_instance"} and up > > This query is giving me some instances which were already removed from > promethues.yml > > Is it still the same after waiting at least 5 minutes? -- You

[prometheus-users] Least used instances

Hello All, I have 100 instances where I install node exporter and through Prometheus, I am pulling those instances metrics. Now I want to find the least used instances among those based on certain parameters like Total CPU cores, CPU used, Total Memory, and Memory Used. For example, we will

Re: [prometheus-users] Re: Hisorical data

On 26/09/2022 14:33, BHARATH KUMAR wrote: Thanks for your reply. If I use deletion API will it delete all the stored data or will it delete the instances data I deleted in the Prometheus.yml file. It will delete whatever you tell it to delete:

Re: [prometheus-users] Re: Hisorical data

Thanks for your reply. If I use deletion API will it delete all the stored data or will it delete the instances data I deleted in the Prometheus.yml file. Thanks & regards, Bharath Kumar. On Monday, 26 September 2022 at 18:33:12 UTC+5:30 Stuart Clark wrote: > On 26/09/2022 13:10, BHARATH

Re: [prometheus-users] Re: Hisorical data

On 26/09/2022 13:10, BHARATH KUMAR wrote: *Query:* up{instance=~"$unreachbale_instance"} and up This query is giving me some instances which were already removed from promethues.yml That's expected. The jobs in prometheus.yaml and the targets referenced are just what Prometheus should

[prometheus-users] Alertmanager configuration for Telegram

Hello everybody, I am trying to send alerts to Telegram from Alertmanager but I am getting below error: *ts=2022-09-26T10:40:11.512Z caller=notify.go:732 level=warn component=dispatcher receiver=telegram integration=telegram[0] msg="Notify attemp failed, will retry later" attempts=1

[prometheus-users] Re: Hisorical data

*Query:* up{instance=~"$unreachbale_instance"} and up This query is giving me some instances which were already removed from promethues.yml Is there any mistake I am doing? On Friday, 23 September 2022 at 22:05:51 UTC+5:30 Brian Candler wrote: >

Re: [prometheus-users] is it already a known issue with alertmanager integration to pagerduty

On 26/09/2022 12:02, Brian Candler wrote: > When, I have multiple alerts for the same route with same severity, all ended up in pagerduty as expected Yes, because these are separate alerts that are not grouped together. > But, when I have alerts triggered for the same instance with different

Re: [prometheus-users] is it already a known issue with alertmanager integration to pagerduty

> When, I have multiple alerts for the same route with same severity, all ended up in pagerduty as expected Yes, because these are separate alerts that are not grouped together. > But, when I have alerts triggered for the same instance with different severity, then I have only one (may be also

Re: [prometheus-users] is it already a known issue with alertmanager integration to pagerduty

Hi, Thanks for the reply. I have only one route per environment and doesn't have separate routes per severity within environment. When, I have multiple alerts for the same route with same severity, all ended up in pagerduty as expected. But, when I have alerts triggered for the same instance