How Notifications and Latencies work together
How Notifications and Latencies work together
Here is what happens if a sensor fails:
· Initial Event: For the first time a request of a sensor is slow or fails
· Now the sensor will be shown with the slow state (yellow color)
· If the “latency for warnings” is zero a warning notification will be triggered immediately
· If the “latency for warnings” is not zero and if consecutive requests are also slow a warning notification will be triggered as soon as the “latency for warnings” has expired.
· A second sensor request is sent out immediately by IPCheck Server Monitor automatically
· If the second request is fine, nothing happens
· If the second request is “down”
· the sensor will be shown with the DOWN state (red color)
· If the “latency for errors” is zero an error notification will be triggered immediately
· If the “latency for errors” is not zero and if consecutive requests also fail an error notification will be triggered as soon as the “latency for errors” has expired.
· If consecutive requests still fail an error notification will be triggered as soon as the “latency for Escalations” has expired.
· If sometime later a request runs through without problems
· the sensor will be shown with the UP state (green color)
· An OK notification will be triggered immediately
And there are more aspects that influence this behaviour:
· If you have selected a dependency for a sensor then the sensor is not scanned as long a the dependency sensor is not in an UP state
· If you have selected a dependency for a notification then the notification is not triggered and sent out as long a the dependency sensor is not in an UP state
· If you have selected a schedule for a sensor then the sensor is only scanned in the time intervals defined by the schedule.
· If you have selected a schedule for a notification then the notification is only triggered during the time intervals defined by the schedule.