Symptoms:
Slowness in the Operating System response due to high usage of the CPU by hardware interrupts.
Impact: Critical
An interrupt alerts the CPU to a high-priority condition requiring the interruption of the current code execution. The processor responds by suspending its current activities, saving its state, and executing a function called an “interrupt handler” to deal with the event.
Expected behavior :
The hardware interrupt level should be less than 2% of CPU usage, depending on the CPU frequency, running software, and attached hardware, and not impact OS response time.
Disk IO/ Network/ Memory utilization – Priority: Critical
There are one or more processes defined as critical that together with high CPU usage request high Disk IO and/ or Network and/ or Memory utilization.
Recommended action :
Verify in the time frame where this alert was triggered, the Disk IO/ Network/ Memory utilization. In the AimBetter platform, this verification can be done in the Performance tab -> Analyze subtab. Selecting the specific time frame, you can easily check in the 5 minutes logs, which had higher resource usage, and drill into these logs to understand the specific processes involved.
Background
Cpu hardware interrupts indicate that there are signals that the CPU receives by any kind of OS external device such as disk io, network, memory, or page file.
System interrupts appear as Windows processes, and they communicate with the CPU that their input must be processed with high priority.
When hardware interrupts are higher than expected, there may be a hardware issue that must be investigated.
