Browse Prior Art Database

Associated event filtering

IP.com Disclosure Number: IPCOM000224079D
Publication Date: 2012-Dec-06
Document File: 1 page(s) / 17K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method to efficiently track current software status by defining supersede associations between alerts.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 86% of the total text.

Page 01 of 1

Associated event filtering

Tracking current status is a challenge for modern software. Polling can be expensive, especially when a large number of endpoints are being managed, and does not detect changes immediately. Using alerts, changes can be detected immediately, but it is difficult to determine whether/which previously detected states are still in effect given the new alert.

Some current alert systems attempt to solve this by placing the onus on the alert listener to determine what is still active. This requires more intelligent listener code, and is wasteful when the alert sender also needs to be able to report active problems. Other current alert systems attempt to solve this by sending alert and recovery notifications with the same event id, but this approach results in more alerts than would otherwise be needed in some cases. For example, component removal may clear multiple problems associated with that component which would have to be communicated via alerts as well as the removal. Another example is temperature changes across multiple thresholds. In order for accurate status to be maintained by the listening software, alerts would be needed for each threshold crossing, rather than only for the most significant threshold crossing when multiple crossings are simultaneously detected by the alert sender. Extra alerts put more load on the system and leads to quicker log scrolling.

The solution is to define supersede associations between alerts. The sendin...