Zenoss Core continuously monitors devices and will continue to generate events for problems it has previously detected. However, Zenoss Core builds some intelligence into its event handling by recognizing duplicate events.
An example of a duplicate event might be a file system that's operating at 98% capacity on a server. We want Zenoss Core to notify us when that threshold is crossed, but we don't need a "reminder" every time Zenoss polls the device. That would clog up the Event Console and clog up our e-mail with dubious alerts.
Think about this. If Zenoss Core monitors a device every 60 seconds, it could generate 1,440 events a day for a single problem. Thankfully, Zenoss suppresses all that noise with event de-duplication.
If Zenoss determines that the event is a duplicate of an existing event, it increments the count on the existing event, rather than generate a new event. Events trigger alerts, and by suppressing duplicate events we avoid duplicate alerts, thereby...