To prevent alert fatigue when a batch job overnight increases CPU usage, which adjustment is BEST?

To prevent alert fatigue when a batch job overnight increases CPU usage, which adjustment is BEST?

• A. Set a different threshold during the batch peak time.
• B. Increase the alert time threshold to 65 minutes.
• C. Increase the alert utilization threshold to 80%.
• D. Manually disable monitoring during the batch job.

Answer: (A)

Alert fatigue is minimized by tailoring monitoring to predictable workload changes rather than applying a one-size-fits-all threshold. When a batch job runs overnight and drives CPU usage up, the best move is to set a different alert threshold for the batch peak window. This lets the system recognize the normal, expected spike during that time and avoid generating noise, while still raising alerts if CPU usage remains high outside that window or if a real problem arises. Delaying alerts by increasing the time threshold helps with noise but can hide real issues and slow detection, which isn’t ideal. Raising the utilization threshold to a higher value might prevent some alerts during the spike, but it risks missing genuine problems that occur within the batch window. Disabling monitoring during the batch eliminates visibility entirely and is risky for catching new issues.

Alert fatigue is minimized by tailoring monitoring to predictable workload changes rather than applying a one-size-fits-all threshold. When a batch job runs overnight and drives CPU usage up, the best move is to set a different alert threshold for the batch peak window. This lets the system recognize the normal, expected spike during that time and avoid generating noise, while still raising alerts if CPU usage remains high outside that window or if a real problem arises.

Delaying alerts by increasing the time threshold helps with noise but can hide real issues and slow detection, which isn’t ideal. Raising the utilization threshold to a higher value might prevent some alerts during the spike, but it risks missing genuine problems that occur within the batch window. Disabling monitoring during the batch eliminates visibility entirely and is risky for catching new issues.