HP Operations Manager for Windows

Configure duplicate message suppression


The message suppression tab in the server configuration dialog enables you to configure how the management server handles duplicate messages.

To configure duplicate message suppression

  1. In the console tree, right-click Operations Manager, and then click Configurearrow Server.... The Server Configuration dialog appears.
  2. Click the Message Suppression tab.
  3. Check the Suppress and count duplicate messages check box. The number of duplicate messages appears in the message browser headline in the Duplicates column. Selecting this option can improve performance if a message storm occurs. Suppressing messages delays their arrival in the browser for the specified number of seconds and can prevent message storms. One message is sent to the browser and the count indicates whether a storm is in progress.
  4. To specify the criteria for a duplicate message, click Message Fields to open the Duplicate Message Comparison Fields dialog box and use it to indicate your choice.
  5. Specify the severity level, the message text, or both, to display in the browser using the options in the Display the severity of: list box. You can display the following options:

    If messages are not matched by severity, message text, or both, (for example, if they contain a message key) you could have a duplicate with different severity or message text, or both. You would want to see the data of the most recent duplicate, for example, if the severity had changed from Major to Normal. You should not change the default Display the severity and the text of the most recent duplicate because some SPI-generated messages would cause the console to show the wrong severity and message text.

  6. Delay duplicate message notification (in seconds): Specify the time interval at which the duplicate counter is refreshed in the message browser, rather than the real-time arrival of messages. This helps to control message storms.
  7. Maximum number of duplicates cached before notification: Specify the number of cached duplicates to be consolidated on the server side before they are sent to the console. This setting is only functional when Delay duplicate message notification is set to a value higher than 0.

    Whenever the time interval for adding duplicates to the browser expires, or the maximum number of duplicates cached is reached, the duplicates are sent consolidated to the console. If you have specified 5 seconds, for example, and 1,000 duplicates, if 5 seconds is reached before 1,000 duplicate have arrived, the duplicates are posted anyway. If 1,000 duplicates arrive before the 5 second interval is up, they will be posted even though the interval has not been exceeded.

  8. Duplicate Message Storage Settings: Check the box Store duplicate messages if you want to include the duplicate as a duplicate annotation in the Message Browser dialog box Duplicates tab.
  9. Maximum number of duplicates to store: Enter a number in the field for the maximum number of duplicates you want to keep. The Unlimited choice is usually not recommended because the number could become extremely high.

Related Topics: