Administer > Configure Incidents

Configure Incidents

[This is the Context-Sensitive Help topic for the Incident Configuration form.]

Incidents are information that NNMi considers important to bring to your attention regarding your network. See How NNMi Gathers Incidents for more information.

NNMi provides a set of incident configurations for the following:

  • Traps generated from an SNMP agent (SNMPv1, SNMPv2c, or SNMPv3)
  • Syslog Messages
  • Management incidents that are generated by NNMi

See Incident Configurations Provided by NNMi for more information about the configurations provided.

Note If a node is deleted, only an NNMi administrator can view the incidents associated with that node.

NNMi provides one centralized location, the incident views, where the management events, SNMP traps, and Syslog Message Incidents are visible to your team. You control which SNMP traps and Syslog Messages are considered important enough to show up as incidents. You can also configure how incidents that are generated by NNMi are displayed. You and your team can easily monitor the incidents and take appropriate action to preserve the health of your network.

You can modify the incident configurations provided by NNMi or create new incident configurations. To do so, see the following topics:

Tip See Configure a Correlation Rule and Configure a Causal Rule for information about creating incidents for use in Custom Correlations.

Caution If you make changes to an incident configuration provided by NNMi, those changes are at risk of being overwritten in the future. See Author form for important information.

You can also use the Incident Configuration form to define relationships between multiple incidents by creating deduplication and rate configurations. See Manage the Number of Incoming Incidents, Correlate Duplicate Incidents (Deduplication Configuration), and Track Incident Frequency (Rate: Time Period and Count), for more information.

You can use the Incident Configuration form to control how NNMi handles incoming SNMP traps. See Handle Unresolved Incoming Traps and Control which Incoming Traps Are Visible in Incident Views for more information.

Note Each time you stop and restart ovjboss, any incidents that have not yet been correlated or persisted are lost. This means that after a restart of ovjboss, an incoming incident might not be correlated as expected. For example, after a restart of ovjboss, a duplicate incident might not be correlated under its original parent incident. Instead, a new parent incident might be generated. See Stop or Start an NNMi Process for more information about starting and stopping the ovjboss process.