Greetings,
There are many situations where one may want a notification channel to run for both the warning and critical state for the same alarm. A critical piece to this is the transition of an existing alarm from warning state to critical state, which SCOM notifications currently ignore.
Am I missing the boat, or is SCOM missing what seems like a fundamental option? If I can configure a rule or monitor to trigger on warning and critical health states, and I can configure a notification subscription to include warning and/or critical health states, the notification channel should run when an alarm state get worse, and a subscription is configured for that state.
Is this something Microsoft will be addressing? Are we 'doing it wrong,' and should we change the way we monitor? Should I stand up Orchestrator to handle these transitions? Do I need to set up a completely separate monitor because SCOM can't handle the fundamentals?
Hoping this is addressed. SCOM seems like a fantastic product with great flexibility and functionality. On the otherhand, there are times when I feel like I'm receiving a million paper cuts...
Your insight would be greatly appreciated!