Page 1 of 1

Incident ageing setting?

Posted: Wed Oct 03, 2012 10:10 am
by kubben
We are using pagerduty for notifications and escalations, which is all working as expected, save for though i have set notification interval to 0 via a service template, we get another notification hours later.

looking at inherited configuration, it states there is no multiple alerts, i believe the incident itself is aging off, because there is no direct acknowledgment on the nagios level. since the warning or critical state still exists, it sees it as a new event, and triggers another, new event.

i am sure this setting can be altered in core, but don't seem to be able to find it.

thoughts?

Re: Incident ageing setting?

Posted: Wed Oct 03, 2012 11:34 am
by kubben
ah, the status was actually changing between warning and critical, thus creating new alerts. kindly disregard.