Ad Widget

Collapse

defining multiple severity levels in one trigger

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • td3201
    Junior Member
    • Nov 2008
    • 25

    #1

    defining multiple severity levels in one trigger

    Hello,

    I have a trigger for low disk space on an agent. It is set to Average. Is it possible to create an expression that sets severity to a LOW for let's say free disk space < 5G and HIGH for < 1G?

    Thanks!
  • ataylo13
    Senior Member
    • Feb 2007
    • 122

    #2
    I have only been able to accomplish this using 2 triggers.
    Version : 1.8.8
    Current Configuration 1 Master and 3 Child Nodes

    Comment

    • td3201
      Junior Member
      • Nov 2008
      • 25

      #3
      That's cumbersome. I wish there was a way in the expression logic to force a new severity.

      Comment

      • gospodin.horoshiy
        Senior Member
        • Sep 2008
        • 272

        #4
        Easiest way I know is to create two triggers and make one dependent on another, with higher severity
        Zbx 2.0.4 on Debian and MYSQL5 on Ubuntu Server 64bit 8.04,
        200+ Win Agents, 50+ Linux Agents, 150+ Network Devices

        Comment

        • td3201
          Junior Member
          • Nov 2008
          • 25

          #5
          Oh good tip. Wouldn't have thought to do a dependency at first. Should be able to template that logic of course so that is OK.

          Comment

          • zabbix_zen
            Senior Member
            • Jul 2009
            • 426

            #6
            I still see a need for this..

            I've opened a Request

            Comment

            • Sergeylo
              Member
              • Feb 2011
              • 40

              #7
              Same situation (lot of similar triggers). If it's clear to me, such feature will be realised in 1.8.5

              Comment

              • zabbix_zen
                Senior Member
                • Jul 2009
                • 426

                #8
                Unfortunately developers see this code/DB model change as a nuisance that doesn't justify the improvement.

                Comment

                • zabbix_zen
                  Senior Member
                  • Jul 2009
                  • 426

                  #9
                  I've tried to reopen the issue,
                  as I see it important not only for our monitoring scenarios but for other large installations.

                  Comment

                  Working...