Whatâs with Orchestrations not having the granular âtriggering thresholdsâ I have in basic event rules?
I need to tell a particular noisy alert to chillax and only create an incident after X amount of noise over a certain period.
Whatâs with Orchestrations not having the granular âtriggering thresholdsâ I have in basic event rules?
I need to tell a particular noisy alert to chillax and only create an incident after X amount of noise over a certain period.
Hi @matt.newman, you should have an Action Rule called âDepends on event frequencyâ in Event Orchestration, this replaces the triggering thresholds.
Exactly as @constant.fischer says. The new Orchestration rules are a bit to adjust too from Event Rules but I, for one, am seeing some pretty neat potential with them. Where an Event Rule was all-in-one, you break the Event Orchestration down into steps.
So if you want a threshold on a specific alert based on content you would have content rule that would match against the alert and âLeave as isâ. From there you can build addition rules off the first.
So one of mine, for example, is three branches:
Biggest tradeoff I see to the additional overhead is that I can get very fancy with logic in PagerDuty instead of being restricted to the linear flow of Event Rules.
Yep! Thanks guys! I see it now. Not sure how I passed that one up. Iâd only nested once early on in my Orchestration testing and I wasnât using nesting correctly at that time.