Currently there isn’t an easy way to do this. We call this “compound conditions.” Although I do like the ring to “super conditions” This is a topic we talk about internally now and again, but I don’t have a date or commitment I can share at this time.
That said, we are hard at work on a totally revamped incident & issue lifecycle that you’ll hear more about soon. Soon you’ll get access to a feature we call “Decisions” which allows you to group incidents based on time, context and connectivity. In addition you can raise and lower severity when this event correlation occurs.
This, in combination with a new Workflow capability will allow you to route your incidents using a flexible filtering approach, similar to a NRQL
So, putting the two together, you could:
- Create a handful of conditions with warning thresholds
- Create a Workflow that routes warning Issues to low priority destinations like Slack
- Create a Decision that both correlates (groups) Issues from those handful of conditions together when they occur close in time, and raise their severity to critical.
- Create a Workflow that routes critical issues to high priority destinations like PagerDuty.
I know this isn’t the same as compound conditions, but it is similar and might help you with the problem you’re trying to solve. You can do this today if you have access to our Incident Intelligence product. Otherwise you’ll need to wait a couple of months for an announcement that should open up access to this solution to you.