zabbix-cachet icon indicating copy to clipboard operation
zabbix-cachet copied to clipboard

Published 20 hours ago • verified publisher icon qk4l

Ability to nest trigers

Open dbnewman opened this issue 8 years ago • 5 comments

Hi Artem,

Would it be possible to add the ability to trigger a service based on its subordinate triggers?

Currently only one level of nesting is allowed, we would like to have high-level categories that can be triggered by a number of subordinates.

ie.

Service Status (root level) -- Core Services ---- Internet Service (shown on cachet, triggers based on subordinates) ------ Proxy Service (trigger, hidden on cachet) ------ DNS Service (trigger, hidden on cachet)

capture

dbnewman avatar Feb 07 '17 23:02 dbnewman

Hi, I was in my todo list since beginning.

What do you think about Cachet incidents name/message in this scenario?

qk4l avatar Feb 28 '17 22:02 qk4l

This is how I went about it, Zabbix calls this script each time a trigger is updated which in turn updates the component/incident. We are still using your script to sync the groups/components, I guess it would be nice to have it "all in one", are also only trigger one level deep below the component at this point.

capture zabbix-cachet.zip

dbnewman avatar Mar 01 '17 00:03 dbnewman

Just wondering if there was any update to this enhancement? I am trying to setup IT Services lower down, and even though the status is reported all the way up to the root, my cachet doesn't get updated.

networkdawg avatar Feb 08 '18 19:02 networkdawg

@networkdawg, @dbnewman

Hi, I implemented this feature. You can try and test by clone 12_nest_triggers branch or use nest_services tag.

There are some uncertain things here:

  • What should we write to description/link field during component creation? In simple case we took this data from linked trigger, but here we can have more than one trigger.
  • Acknowledgements not implemented yet

qk4l avatar Jun 20 '18 11:06 qk4l

@qk4l just tried the brqnch. It does indeed seem to work!

i created a tree like this: Root -Test —Test Child —-Leaf ——Trigger X

And when the trigger activated the fault would propagate all the way up to Test.

Now I might have found a regression or a completely different fault. I later exchanged Trigger X with another Trigger Y and cachet does not see the change. test Leaf had this (?) symbol and holding over it still shows Trigger X even if I replaced it hours ago.

Any plan on when this branch will make it into master?

kind regards Jens

jensolsson avatar Jun 27 '22 19:06 jensolsson