Trigger name "Load average is too high (per CPU load)" confuses users (wrong item key)

XMLWordPrintable

    • Type: Problem report
    • Resolution: Won't fix
    • Priority: Trivial
    • None
    • Affects Version/s: 4.4.6
    • Component/s: None
    • None

      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 

            Assignee:
            Zabbix Support Team
            Reporter:
            Ilya Ableev
            Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: