Example: Suppressing temporary high memory usage warnings

You might want to suppress certain events to stop them from forming an incident or becoming part of existing incidents. Suppressing events can prevent effort spent on temporary issues that do not present a persistent problem.

About this task

For example, you might have brief periods of high application usage that cause the database memory consumption to grow over normal levels. Unless the high consumption levels become persistent, you can ignore such spikes. To avoid getting distracted by events warning about high memory consumption, you can set a policy to suppress such events for the database server unless more than 5 corresponding events are raised within 15 minutes.

Important: This is an example. Consider your setup and environment when determining the conditions for any policy.

To set up this policy:

Procedure

  1. Click Policies on the IBM® Cloud App Management Administration page.
  2. Click Create event policy.
  3. Go to Details and enter a name in Policy name, for example, Suppress temporary high memory warnings. You can also add an explanation of the policy in Description to help you and others understand the purpose of the policy, for example, Suppress high memory usage warnings from database server unless they become persistent.
  4. Click Specify conditions in Events, and set the following conditions:
    1. Set Condition 1 as follows: select Hostname from the list of attributes, select is from the list of operators, and enter the host name in the field.
    2. Ensure you have AND set and click Add condition.
    3. Set Condition 2 as follows: select Event Type from the list of attributes, select is from the list of operators, and enter memoryUsage in the field.
    4. Click Add condition.
    5. Set Condition 3 as follows: click Add predefined condition and select Severity of event is Critical.
  5. Optional: When selecting Specify conditions, you can check to see how many events would have matched the conditions you set. Go to the end of the Events section, select the number of days between 1 and 30, and click Test. The result shows how many events would have matched the policy conditions.
    Click Show results to view a list of all the events that would have matched the conditions in the set time. Click New test to change the time frame for testing, or if you changed conditions and want to check again for matching events.
    Note: If your event policy enriches fields used by the conditions of your policy, you might not find any matching events after the policy is enabled and applied.
  6. Select the Suppress check box in Action, and expand the section.
  7. Click Supress until and use the arrows to select a value of 5 identical events to occur within 15 minutes.
    Note: When an event is suppressed, no further actions from other policies are used for that event.
  8. Set Enable to On to start using the policy. The policy might take up to 30 seconds to become active and its settings to take effect.
  9. Click Save.