Go to All Forums

On Agent Restart Pagerduty is Notified Immediately - This should not happen

Problem: When I reload the agent on a linux machine, it IMMEDIATELY triggers a pagerduty notification. 

Ideally what I want is for it to wait - pause before escalating. It ends up triggering a lot of false alarms and annoys our DevOps team. 

Is there a way to change the priority or the immediacy of the pagerduty alert when it loses contact with the plugin/agent. 

Like (0) Reply
Replies (1)

 

Hi,

  One suggestion is that you can use "Downtime Notification Delay" in your "Notification Profile". You set the value to "Notify after two/three continuous failures". (see image)

Based on the polling frequency (in server's case 5 min) you will be notified only when there is 2 or 3 continuous downtime. We will do an internal recheck between the poll frequency if the server (monitor) is up we will not trigger any Alerts (In your case PagerDuty Notification). 

Steps to do configure

Goto -> server monitor -> click on the hamburger icon -> Edit -> Notification Profile -> Click on the Pen icon -> Downtime Notification Delay -> Select your delay.

-Jasper

 

 

 

Attachments
Like (0) Reply

Was this post helpful?