The only part that you can't really do in Orion is the X minutes part, groups automatically build their status based on the status of all their direct members, you can wait 10 minutes to trigger your alert logic, but the group itself will change pretty much right away once a child status changes.
So the tree could possibly look something like this
MyApplication - Parent group folder, set to worst status so if any of these are down, mark the whole thing down
MyApplicationRedundantServerGroup - child group with status set to best (group stays green as long as any child is up)
MyApplicationAGroup - child group with status set to best (group stays green as long as any child is up)
Application A (I can't remember off the top of my head if you can do components directly. If you can then just use the component, if not make a template containing only the one component)
A major point I see people messing up is that groups only inherit up/down status, so something going critical will not impact the group statuses at all. Just to keep in mind as you build out your monitors.
Yes, I agree and that won't be an issue for this situation. We already have good monitoring on all of those individual components. Our goal was to use a Group is Down / Group is Up alert that would trigger a slack message to let people know that an entire critical application is down. Anything else regarding the details and components that may be in critical or warning are handled through my team. So this is actually purely for automated messaging that the application is either up or down.
Thank you, I'll work on this and see if we are able to obtain the results and behavior we are looking for.
I will let you know how it goes and mark the answer accordingly.