Each filter has attributes as described in the following table.
|
Attribute |
Description |
Example |
|---|---|---|
|
Name |
Filter name as stored in the configuration database. This name must be unique for each filter. |
Archive directory cleanup |
|
Information |
Description to clarify what the filter does. |
Clear out archive directory when full |
|
Interval |
The period within which subsequent events matching the filter definition are ignored. |
60 (duplicate events are ignored for 60 seconds) |
|
Event Interval |
The period within which all events matching the filter and event name are ignored. |
0 (no events are ignored) |
|
Events1 |
Event names that must match the detected event's name before it is allowed to be dispatched to the action routines. |
CMgr Archive Area Full |
|
Classes1 |
Class names, which must match the detected event's class before it can dispatch to the action routines. |
CONSOLEmanager |
|
Systems2 |
Systems that the event must come from before can dispatch to the action routines. |
All |
|
Subsystems |
Events whose subsystems match the definition list. |
Console |
|
Groups2 |
Group of systems that events must come from before they are dispatched to the routines. |
GROUP1 |
|
Priorities |
The individual priority levels that the events selected for the filter must match for the dispatch entries to be invoked. |
Critical |
|
Dispatches |
Actions to which the event is dispatched when the filter criteria are met. |
Archive Cleanup |
|
1Also, if a subset of Events is selected, and All Classes is also selected, then All Classes overrides the intended subset of Events definitions. 2If a subset of Systems is selected, and All Groups is also selected, then All Groups overrides the intended subset of Systems definitions. |
||
|
Copyright © 2010 CA.
All rights reserved.
|
|