Missing CPU Usage Alerts with Top Processes for Windows Team in DX Unified Infrastructure Management (Nimsoft / UIM)

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

You need to set up CPU usage alerts for your Windows team that include specific details about the top processes consuming CPU resources. This ensures that when a CPU threshold is breached, the resulting alarm provides immediate visibility into which applications or services are responsible for the high utilization.

Environment

• Product: DX Unified Infrastructure Management (Nimsoft / UIM)
• Probe: cdm (CPU, Disk, Memory)
• Platform: Windows/linux

Cause

By default, cdm probe alarms for CPU usage may not include process-specific data unless you explicitly configure the alarm messages to use the appropriate variables and verify that the message severity settings are correctly mapped in the probe configuration.

Resolution

You must configure the cdm probe to include top process variables in the alarm messages and ensure the correct message definitions are active in case the related message definitions were changed previously

Step 1: Configure Advanced Monitoring Properties

1. Open the cdm probe configuration in Infrastructure Manager (IM) or Admin Console (AC).
2. Navigate to the CPU > Advanced tab.
3. Enable the option to Include Top Processes in Alarm/Message.
4. Set the Number of Top Processes you wish to include (e.g., 5 or 10).

Step 2: Modify Alarm Messages

1. Go to the Message Pool in the cdm probe configuration.
2. Locate the messages used for CPU thresholds (typically CPUErrorProcesses and CPUWarningProcesses).
3. Ensure the message text includes the Top Processes $processesvariable.
   • Example: Average ($value_number samples) cpu usage is now $value$unit, which is above the error threshold ($value_limit$unit).Top Processes $processes.
4. If the messages are missing or modified incorrectly, you can drag and drop the default messages from the message pool or use Raw Configure to manually update the cpu > alarm > error and cpu > alarm > warning sections.
5. 

Step 3: Apply and Validate

1. Save the configuration to restart the probe and apply changes.
2. Trigger a test alarm by temporarily lowering the CPU threshold below the current usage level.
3. Verify that the generated alarm in the Alarm Console contains the list of top processes.