Applying Robust, Prioritized Filtering Rules To Categorized SAN Events
Original Publication Date: 2004-May-27
Included in the Prior Art Database: 2004-May-27
One of the main purposes of SAN Management applications is to alert users about changes in the SANs that are being monitored. Users are typically made aware of these changes in the monitored SANs by changes to a graphical representation of the SAN the application might be displaying, and also by receiving events published by the application. Due to the specific nature of these events, a simple change to the SAN, such as breaking a connection between two ports, can result in a huge flood of events getting published alerting the user about diverse things such as missing switches, HBAs, LUNs, PVs, etc.. Publishing large numbers of events can lead to two problems: 1) The client applications that receive the events may not be able to process all of them, resulting in the user not getting notified of possibly critical changes. 2) Useful events may be hard to spot amidst a flood of other events that may not be of interest to a particular user. This problem is solved by allowing the user to create a set of priority based event filtering rules that are used by the SAN Management application. Each rule can be written to cover a very specific condition or can be made to be very general. Rules are assigned a priority value when they are created, and can be used to specify that events should be published if the conditions specified in the rule are met, or if they should be suppressed for those conditions. To add another dimension of control, the events themselves are placed in heirarchical categories when they are created. When combined, these features allow the user to have extensive control over the publication of events with a minimum number of rules.