Administer > Configure Incidents > Configure SNMP Trap Incidents > SNMP Trap Configuration Form > Configure Enrichment Settings for an SNMP Trap Incident

Configure Enrichment Settings for an SNMP Trap Incident

[This is the Context-Sensitive Help topic for the Incident Config: Suppress Tab for all Incident Configurations.]

For information about each SNMP Traps tab: Concept Link IconSee Also

For information about each Enrichment tab: Concept Link IconSee Also

NNMi enables you to fine tune and enhance incidents based on Interface Group, Node Group, or default Enrichment settings. NNMi applies your Enrichment settings in the following order. Only the first match applies:

  1. Interface Group (SNMP Trap Configuration Form: Interface Settings tab)
  2. Node Group (SNMP Trap Configuration Form: Node Settings tab)
  3. Enrich configuration settings without specifying an Interface Group or Node Group (SNMP Trap Configuration Form: Enrichment tab)

The types of items you can fine tune and enhance for a selected incident configuration, include:

  • Category
  • Family
  • Severity
  • Priority
  • Correlation Nature
  • Message
  • Assigned To

Note Any configuration you specify for Severity, Priority, or Message overrides those values provided in the SNMP Trap Configuration Form: Basics information.

You can also add a Custom Incident Attribute that is provided by NNMi to the incoming incident.

Note You cannot create Custom Incident Attributes.

When configuring Interface Settings, Node Settings, or other Suppress Configuration, Enrich Configuration, or Dampening configuration settings for an incident, you can specify a Payload Filter. Payload Filters enables you to use the data that is included with any of the following items before they are stored as incidents in NNMi:

  • Traps generated from an SNMP agent
  • Syslog Messages
  • Management incidents that are generated by NNMi

Examples of the type of data that can be used as a Payload Filter include SNMP trap varbind names and values as well as Management Event CIA (Custom Incident Attribute) names and values. For example, you might want NNMi to enrich an incident based on a particular status change notification trap and participation within a specified Node Group or Interface Group. To do so, you would first specify participation in the Node Group or Interface Group for the trap you want to enrich. You would also specify a Payload Filter that includes the name of the trap varbind that stores the status information as well as the status change value string of interest.

See Configure Incident Enrichment Settings for an Interface Group (SNMP Trap Incident) for information about how to enrich an incident for an Interface Group with or without a Payload Filter.

See Configure Incident Enrichment Settings for a Node Group (SNMP Trap Incident) for more information about how to enrich an incident for a Node Group with or without a Payload Filter.

To configure Enrichment settings for an incident using a Payload Filter without an Interface Group or Node Group Filter:

  1. Select the Enrichment tab.
  2. Do one of the following:

    1. To create a new configuration, click the  New icon.
    2. To edit an existing configuration, select a row, click the  Open icon, and continue.
  3. Provide the required information (see table)
  4. Click  Save and Close to save your changes and return to the previous form.
Enrichment Attributes
Name Description
Category

Use the Category attribute to customize the category for this incident configuration. Possible values include:

  • Accounting
  • Application Status
  • Configuration
  • Fault
  • Performance
  • Security
  • Status
Family

Use the Family attribute to customize the Family for this incident configuration. Select from the drop-down list or create a new value. For example, some of the values provided by NNMi include:

  • Address
  • Aggregated Port (Interfaces using Link Aggregation or Split Link Aggregation protocol.)
  • Card
  • Connection
  • Correlation
  • Interface
  • Node
Severity

The incident Severity represents the seriousness calculated for the incident. Use the Severity attribute to specify the severity that should be assigned to the incident you are configuring. Possible values are described below:

Normal - Indicates there are no known problems related to the associated object. This Severity is meant to be informational. Generally, no action is needed for these incidents.

Warning - Indicates there might be a problem related to the associated object.

Minor - Indicates NNMi has detected problems related to the associated object that require further investigation.

Major - Indicates NNMi has detected problems related to the associated object to be resolved before they become critical.

Critical - Indicates NNMi has detected problems related to the associated object that require immediate attention.

Priority

Used to communicate the urgency of resolving the selected incident. You control this value. NNMi sets this value to null by default. The lower the number the higher the priority.

Possible values are:

None

Low 

Medium

High 

Top

Note: The icons are displayed only in table views.

Correlation Nature

Use the Correlation Nature to customize the Correlation Nature for this incident configuration. Possible values include:

  • Info
  • None
  • Root Cause (or User Root Cause)

    Tip When using Incident views:

    •  Root Cause value = determined by NNMi's Causal Engine
    •  User Root Cause = your NNMi administrator configured NNMi to always treat this Incident as Correlation Nature: Root Cause
  • Secondary Root Cause
  • Symptom
  • Stream Correlation
  • Service Impact
  • Dedup Stream Correlation
  • Rate Stream Correlation
Message Format

When configuring an incident, specify how the incident message appears in the incident view. The string you specify in the Message Format attribute is visible in an incident view.

The incident message limit is 1024 characters. If you exceed this limit, NNMi truncates the value starting from the right.

You can use any combination of default and custom attributes.

Valid Parameters for Configuring Incident Messages (SNMP Trap Incident)

Include Custom Incident Attributes in Your Message Format (SNMP Trap Incident)

Assigned To

Use to specify the owner of any incident generated for this incident configuration.

Click the  Lookup icon and select  Quick Find to select a valid user name.

Note You can also begin to type a valid user name and use the auto-complete feature to select the user name of interest.

Description

Use the Description attribute to provide additional information that you want to note about the current enhancement configuration. This description applies only to the enhancement configuration and does not appear when NNMi displays any associated incident.

Type a maximum of 1024 characters. Alpha-numeric and special characters (~ ! @ # $ % ^ & * ( ) _+ -) are permitted.