Ad Widget

Collapse

Zabbix actions disabled themselves

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • dmsmith32
    Junior Member
    • Feb 2019
    • 1

    #1

    Zabbix actions disabled themselves

    Hello

    We have various actions set up but for some reasons on Feb 1st 2019 two of these actions disabled themselves without warning.
    We have checked through the logs and audits and no user intervention was taken at this time to disable these.
    These two actions do have 48 conditions each which is a lot higher than other actions configured.

    Is anyone aware of any reason why actions would disable themselves or did anyone experience any issues with their own Zabbix on Feb 1st 2019
    Is their any other method to find out why these two actions disabled themselves other than looking at the audit and action logs.

    These actions alerted the on-call pager person so obviously this could have and still can have big impact on customer support.

    Best Regards

    Darren Smith
  • kloczek
    Senior Member
    • Jun 2006
    • 1771

    #2
    Originally posted by dmsmith32
    We have various actions set up but for some reasons on Feb 1st 2019 two of these actions disabled themselves without warning.
    Ask your colleagues why they did not gave you any warning :P

    http://uk.linkedin.com/pub/tomasz-k%...zko/6/940/430/
    https://kloczek.wordpress.com/
    zapish - Zabbix API SHell binding https://github.com/kloczek/zapish
    My zabbix templates https://github.com/kloczek/zabbix-templates

    Comment


    • dmsmith32
      dmsmith32 commented
      Editing a comment
      Hi, thanks for replying. No one disabled these actions and no one has an explanation for why this would have happened. Hence I am here.
  • Semiadmin
    Senior Member
    • Oct 2014
    • 1625

    #3
    Actions disabled due to deleted objects

    http://www.zabbix.com/documentation/...ion/conditions

    Comment


    • dmsmith32
      dmsmith32 commented
      Editing a comment
      Thank you very much this was exactly the issue. A trigger had been deleted causing the action to become disabled.
Working...