25.3.1 Key concepts of event monitoring
This subsection describes briefly the major changes that were made from NNM to NNMi. For details about NNMi incidents, see Configuring Incidents in NNMi Help.
Event subsystems are not used in process-to-process communication. For this reason, the event volume has been reduced significantly. The administrator no longer needs to specify whether to display or log individual IPC messages.
Only traps configured to be received are received. Traps that are not configured are filtered out of the event pipeline.
All received traps are displayed.
The trap filter of the NNMi event subsystem process is configured based on what is selected on the Incident Configuration form.
NNMi's nnmincidentcfg.ovpl command loads only the trap definition of the specified MIB module.
Pairwise correlation, rate correlation, and deduplication correlation that occur in the event pipeline are provided (NNMi does not include an event correlation system (ECS)).
You can configure the actions that will occur in an incident's lifecycle. You can configure all scripts, executable files, or Jython actions as actions.