Skip to main content
Solved

Event Suppression for CPU Util overnight

  • February 10, 2025
  • 2 replies
  • 0 views

Forum|alt.badge.img

We have a server/device that has expected high CPU utilisation overnight, is there a way in SL1 for us to suppress this CPU Utilisation event on this server/device for a few hours during the night when high CPU utilisation is expected ? We want it to have the standard threshold for all other times of the day.

Best answer by jchivers

Hello, 

There are a number of ways of achieving this, here are four:

  1. If CPU utilization follows a fairly consistent pattern across the day, then change the CPU collection object to enable Deviation Alerting. This will create a threshold for each hour of day and day of the week. After (usually) 2 weeks, it will learn that high CPU usage over night is normal and change the threshold to stop alerting. Introduction to Dynamic Application Development
  2. Create two Device Templates, one of the day and one for the night, each with different threshold values for the CPU collection object. The have RBA schedule a script in the evening and morning to apply the relevant template.
  3. Revise the RBA Automation Policy for the CPU events to use a schedule so that RBA only reacts to the CPUI event during the day.
  4. If this use case becomes common for you, consider modifying the PowerFlow event SyncPack to include a lookup table for event classes that should only become incidents based oon a set schedule.

2 replies

  • Community Manager
  • Answer
  • February 11, 2025

Hello, 

There are a number of ways of achieving this, here are four:

  1. If CPU utilization follows a fairly consistent pattern across the day, then change the CPU collection object to enable Deviation Alerting. This will create a threshold for each hour of day and day of the week. After (usually) 2 weeks, it will learn that high CPU usage over night is normal and change the threshold to stop alerting. Introduction to Dynamic Application Development
  2. Create two Device Templates, one of the day and one for the night, each with different threshold values for the CPU collection object. The have RBA schedule a script in the evening and morning to apply the relevant template.
  3. Revise the RBA Automation Policy for the CPU events to use a schedule so that RBA only reacts to the CPUI event during the day.
  4. If this use case becomes common for you, consider modifying the PowerFlow event SyncPack to include a lookup table for event classes that should only become incidents based oon a set schedule.

There is now a powerpack to help with this https://support.sciencelogic.com/s/release-version/aBuVL0000000qoD0AQ/scheduled-event-suppression