[ZBX-17436] Trigger name "Load average is too high (per CPU load)" confuses users (wrong item key) Created: 2020 Mar 10 Updated: 2020 Mar 11 Resolved: 2020 Mar 10 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | None |
Affects Version/s: | 4.4.6 |
Fix Version/s: | None |
Type: | Problem report | Priority: | Trivial |
Reporter: | Ilya Ableev | Assignee: | Zabbix Support Team |
Resolution: | Won't fix | Votes: | 3 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Description |
Steps to reproduce:
Result: |
Comments |
Comment by Ilya Ableev [ 2020 Mar 10 ] |
And don't forget about default macro limit |
Comment by Ilya Ableev [ 2020 Mar 10 ] |
But macro seems ok: {$LOAD_AVG_PER_CPU.MAX.WARN} 1.5 |
Comment by Vladislavs Sokurenko [ 2020 Mar 10 ] |
Could you please be so kind and provide whole trigger expression, thanks ! |
Comment by Ilya Ableev [ 2020 Mar 10 ] |
Template: Template Module Linux CPU by Zabbix agent {Template Module Linux CPU by Zabbix agent:system.cpu.load[all,avg1].min(5m)}/{Template Module Linux CPU by Zabbix agent:system.cpu.num.last()}>$LOAD_AVG_PER_CPU.MAX.WARN} and {Template Module Linux CPU by Zabbix agent:system.cpu.load[all,avg5].last()}>0 and {Template Module Linux CPU by Zabbix agent:system.cpu.load[all,avg15].last()}>0} My bad, sorry, didn't see division by system.cpu.num |
Comment by Vladislavs Sokurenko [ 2020 Mar 10 ] |
That's OK, thank you for your report, closing as Won't fix, it could be good to change from "all" to "percpu" and remove division but then it would not work on Zabbix agents prior to 2.0 if such would be used. |