Use this pane to select sources of events within the network as filtering
criteria. All categories are organized in a tree (hierarchical) format.
Categories that contain subcategories are indicated by the expansion icon
(
) beside the category's name.
Double-click on the category or single-click the (
)
icon to view its subcategories.
The types of categories displayed are dynamic; the %ProductServerName% increases
its knowledge of event types as components register, acquire information from
the network, and report various event sources.
For example: if a network discovery operation is performed,
the Topology subcategory is added to the %ProductName% category.
Within the Topology category are various subcategories such as Online and
Offline.
You can select these categories to specify the filtering criteria. The higher in
the hierarchy you select, the broader the filtering criteria that is used. Each
subcategory is inclusive of its parent categories.
For example: to create a filtering category for all discovered
systems, expand the %ProductName% category, then select the Topology category.
To create a filtering category for systems that are determined to be offline,
expand the %ProductName% category, then expand the Topology category,
then select Offline.
The following categories are examples of known event origins. Additional event
origins can be discovered and added:
-
After the server is started and network activity is generated
-
If third party event adapters are installed on the %ProductServerName%
-
If user-defined events are created through the
genevent utility
- CIM
- If one or more CIM-enabled systems are discovered with CIM event
structures, the event structures associated with these systems are displayed to
enable filtering on CIM events. You can also use the Extended Attributes tab
to narrow the filtering criteria, if this information is provided in the CIM
events.
Note: If you qualify the CIM filter using one or more extended
attributes, only the events that meet the selected filtering criteria are
included in the %ProductName% event log.
- %ProductName%
- The event originated from an %ProductName% component. The following are
typical subcategories that can be added to the %ProductName% category as
events are generated:
- Test
- The Test => Action category reflects the built-in testing
function you can use to execute an action you have defined. The Test function
is started through the context menu in the Actions pane of the Event
Action Plan Builder window.
- Topology
- When a discovery operation is performed to determine the topology of the %ProductName%
network, this category is created. You can use Topology subcategories as
criteria to build event filters.
- DMI
- If one or more DMI-enabled systems are discovered with DMI event
structures, the event structures associated with these systems are displayed to
enable filtering on DMI events. You can also use the Extended Attributes tab
to narrow the filtering criteria, if this information is provided in the DMI
events.
Note: If you qualify the DMI filter using one or more extended
attributes, only the events that meet the selected filtering criteria are
included in the %ProductName% event log.
- SNMP
- The event originated from an SNMP network as an SNMP trap. To send SNMP
traps to the %ProductName% server, configure SNMP devices on the network to
specify the IP address of the %ProductName% server as a trap destination.
- Windows Event Log
- Activates the inclusion of events in the %ProductName% event log and enables
filtering on events. If you create a filter for the root Windows Event Log category,
extended attributes received by the server on which %ProductName% is installed
is also used to provide the filtering criteria for these events. To qualify
filtering on the basis of extended attribute information, you can use the Extended
Attributes tab.
Note: If you qualify the Event filter using one or more
extended attributes, only the events that meet the selected filtering criteria
will be included in the %ProductName% event log.