We are in the process of converting from a different monitoring application to NPM. In the other alerting application we were able to create 2 different alerting schedules, one for 6:00am to 10:00pm and a second one for 10:00pm to 6:00am. Basically, we wanted to get notified almost immediately during regular daytime hours if something went down. We weren't as concerned about getting immediate notification after hours as in Oklahoma high winds and storms quite often will cause a circuit to bounce momentarily. By the time the e-mail alert went out, woke the oncall person up, and said person connected in to find out what the problem was the circuit was back up and there was nothing to check.
We can do this with NPM as well by setting different time of day for any particular alert. The problems comes that when someting is down and we cross that threshold into the new alerting period, NPM will issue an alert saying the device is down. In other words, let's say we have 2 schedules, 5:00am to 10:00pm where we get notified immediately and 11:00pm to 5:00am where we set the delay on the trigger condition to 15 minutes. If a device goes down at 1:00am we will get a notification at the 15 minute mark just like we're supposed to. If that device hasn't come back up by 6:00am, when we convert to the daytime schedule set of alerts, NPM will alert again saying that the device is down.
Is there some way to keep the state of the device constant between the different monitoring schedules? It's disconcerting to be woken up at 5:00am by a notification that something is still down. Thanks!
