Ad Widget

Collapse

Turn OFF The OFF Message

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • bcarpio
    Member
    • Jun 2008
    • 96

    #1

    Turn OFF The OFF Message

    Ok,

    So I am doing file monitoring on my Linux servers for instance:
    /etc/passwd

    when /etc/passwd changes I receive an alert stating /etc/passwd changed: ON then a minute or two later I receive an alert stating /ec/passwd changed: OFF, I would like to disable the OFF message there is no need for it in this case.

    However, I don't want to globally disable it because I still would like to receive OFF messages for things such as file systems, memory, CPU etc..

    Thanks.
  • tighep
    Senior Member
    • Dec 2007
    • 124

    #2
    When you create the action, you can specify trigger value="true", this will only provide the "on" alerts. This can be set individually for each action.

    Comment

    • Tenzer
      Senior Member
      • Nov 2007
      • 316

      #3
      The way Zabbix is made, it will always trigger the ON and OFF events. This is due to the way triggers are made. They check for when a criteria is meet, and then fires the ON event. When the criteria is no longer meet the OFF event is fired.

      In order to correct this, a new kind of trigger should be made, which simply fires an event for instance when the monitored item changes value.

      Comment

      • noxis
        Senior Member
        • Aug 2007
        • 145

        #4
        Originally posted by Tenzer
        The way Zabbix is made, it will always trigger the ON and OFF events. This is due to the way triggers are made. They check for when a criteria is meet, and then fires the ON event. When the criteria is no longer meet the OFF event is fired.

        In order to correct this, a new kind of trigger should be made, which simply fires an event for instance when the monitored item changes value.
        On top of that a timed trigger, as SNMP trap events dont work well with the current zabbix set. For example our storage system will send out 3 types of traps "Severe" "Warning" and "Information". If I capture and alert on anything that says severe I get my disaster trigger, thing is as soon as anything else comes from the storage platform it will clear that trigger and people may assume the problem is fixed. Or the opposite may occur, the problem fixed but it still stuck in disaster.

        Comment

        Working...