Some explanation: while native monitoring graph shows ~5% CPU usage, Zabbix shows 100%.

Looks like the subject is about item

Name: Ubiquiti AirOS: CPU utilization
key: system.cpu.util[loadValue.2]
OID: 1.3.6.1.4.1.10002.1.1.1.4.2.1.3.2
Description: MIB: FROGFOOT-RESOURCES-MIB 5 minute load average of processor load.

from template

Name: "Ubiquiti AirOS by SNMP"

Looks like we mistook CPU "load" for "utilization".

The problem arises due to the specific OID (1.3.6.1.4.1.10002.1.1.1.4.2.1.3.2) used in Ubiquiti AirOS by SNMP template, which triggers incorrect alerts when CPU usage is below 5%. Let’s address this issue step by step:

1.Locate the Host and Trigger:
In the Zabbix configuration, find the host associated with your Unifi device.
Click on the trigger that corresponds to the incorrect report: “Ubiquiti AirOS by SNMP: Ubiquiti AirOS: High CPU utilization.”

2.Clone the Trigger:
Clone the trigger that is causing the false alert.
This will allow you to modify the cloned trigger without affecting the original one.

3.Disable the Original Trigger:
Disable the original trigger that sends the incorrect report.
This ensures that it no longer generates false alerts.

4.Activate the Cloned Trigger:
Enable the cloned trigger that you created.
This new trigger will replace the original one for monitoring CPU utilization.

5.Update the Expression:
In the cloned trigger, modify the expression manually.
Replace the existing expression with the following:

min(/YOURUNIFIHOSTIPADDRESSS/system.cpu.util[loadValue.2],5m) > 2 * {$CPU.UTIL.CRIT}

like: min(/[192.168.1.10/system.cpu.util[loadValue.2],5m|https://web.telegram.org/a/192.168.1.10/system.cpu.util[loadValue.2],5m]) > 2 * {$CPU.UTIL.CRIT}

This expression ensures that the alert is triggered only when the CPU usage exceeds the critical threshold (as defined by {$CPU.UTIL.CRIT}).

Hi, I'm not agree to point the trigger as the issue. The problem is about the misconception about load and utilization.

The values of the monitor "CPU Utilization" gets CPU Load values and they are no the same concept. This is generating confusion about the issue.

I've created a bug for this. https://support.zabbix.com/browse/ZBX-25855

Issue is in the item "CPU Utilization".

We mistook CPU "load" for "utilization".

Will be fixed in scope of https://support.zabbix.com/browse/ZBX-25855