-
Problem report
-
Resolution: Fixed
-
Trivial
-
4.4.1
-
Zabbix 4.4.1
Template version 0.32
-
Sprint 65 (Jun 2020)
-
0.125
Steps to reproduce:
- Open template Template Module Windows CPU by Zabbix agent (active or not)
- Check CPU queue length is too high (over {$CPU.QUEUE.CRIT.MAX}% for 5m) trigger
Result:
- Trigger name contains %
- Should think abount threshold eq 3
Expected:
- CPU Queue length return non-percent values, so name must be just "over {$CPU.QUEUE.CRIT.MAX}"
- Threshold in 3 is not optimal for most of systems and should be like "length > number-of-cores * 2"