Steps to reproduce:

In official Juniper template, CPU utilization is being calculated with jnxOperating5MinLoadAvg (1.3.6.1.4.1.2636.3.1.13.1.21). High CPU trigger is avg(*5m)*}>{$CPU_UTIL_MAX}.

Result:

This load can be more than %100 as described here:

https://kb.juniper.net/InfoCenter/index?page=content&id=KB31764

Thus it is creating false alarms.

Expected:

Usage of jnxOperatingCPU (1.3.6.1.4.1.2636.3.1.13.1.8) instead of jnxOperating5MinLoadAvg (1.3.6.1.4.1.2636.3.1.13.1.21)