Problem

An event notification received in Slack from StackState reports that a view has a DEVIATING or CRITICAL health state, but: 

• No "possible root cause" information is included in the event notification.
• Clicking on the link provided to the affected view shows that the view actually has a CLEAR health state in the StackState UI.

Cause

The event handler in StackState has been configured to send Slack notifications in response to view health state changes, however, the notification was generated in response to changes in the health state of components and relations that were resolved before the actual view health state changed to DEVIATING or CRITICAL.

Solution

Event notifications in Slack should always contain "possible root cause" information. If no "possible root cause" information is included, the notification can be ignored as the issue has already been resolved.