Duplicate message suppression

As messages arrive from various managed nodes, they are compared to existing messages on the management server. If a duplicate is found, the system increments the original message's duplicate count, discards the new message, and forwards notification of the change to the original message's duplicate count to all interested message browsers.

You can configure duplicate message suppression to store the most important attributes of the new message with the original message before the duplicate is discarded. A maximum of 10 duplicate annotations, plus 1 duplicate annotation containing the original message attributes, is stored by default with the original message. You can also configure the management server to add automatic action responses as annotations to original messages.

If you do not want to suppress message duplicates indefinitely, you can configure the management server to create a new message after a specific interval, or after a specific number of duplicates.

By default, the management server does not start remote automatic actions for duplicate messages, but you can change this behavior.

Message suppression and new policy creation and testing

When creating and testing new policy versions, you should do one of the following:

Disable message suppression temporarily
Acknowledge all messages which were created by the old policy version.

This prevents messages created by the new policy from being recognized as duplicates of the messages created by the old policy.

NOTE:
If server-based flexible management is enabled, all participating servers have to be configured in exactly the same way concerning message suppression to prevent inconsistencies between the servers.

Related Topics: