[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:

  1. Open the alert "Load average is too high (per CPU load over {$LOAD_AVG_PER_CPU.MAX.WARN} for 5m)" from the template "Template Module Linux CPU by Zabbix agent" or "Template Module Linux CPU by Zabbix agent active
  2. See the item key inside: system.cpu.load[all,avg1]
  3. See the trigger description "... per cpu ..."
  4. ...

Result:
Confused colleagues 
Expected:
Either change item key to "percpu" according to the documentation or rename trigger's description 



 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
Item name: Load average (1m avg)
Item key: system.cpu.load[all,avg1] (and 5, 15)
Trigger description: Load average is too high (per CPU load over {$LOAD_AVG_PER_CPU.MAX.WARN} for 5m)
Trigger expression:

{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.

Generated at Sat May 10 07:50:32 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.