When something goes wrong within your IT environment, StackState can use event handlers to send event notifications to alert you or your teammates. A message can be sent in the form of an email, Slack message, mobile ping or an HTTP POST request to any URL. Event notifications can contain detailed content on the trigger event and possible root cause.
StackState event notification in Slack with possible root cause information
Event handlers added to a StackState view can send event notifications or trigger actions in response to health state change events or problem events. The event handler will listen to events generated within the view and run a configured event handler function when the configured event type is generated.
Metrics and events data flow through StackState topology elements in telemetry streams. These telemetry streams are used by health checks to determine the health state of an element. For every change in health state, at least one state change event is generated. Event notifications or actions can be triggered whenever state changed events are generated for a component in the view.
The event types generated when an element state changes are described below.
- Propagated state change of an element - a
PropagatedStateChangedEventevent is generated whenever the health state of one of an element’s dependencies changes. These events are not visible in the StackState UI, but can be used to trigger an event notification.
- State change of entire view - a
ViewStateChangedEventevent is generated only when the health state of a significant number of elements in a view changes. These events are not visible in the StackState UI, but can be used to trigger event notifications.
StackState groups unhealthy components in a view into problems, each with a common root cause. For every change to a problem, at least one problem event is generated.
Changes to a problem result in the following Problem changed events event types being generated:
ProblemCreatedEventevent is generated when a new problem has been created.
ProblemUpdatedEventevent is generated when new information is available for a problem. For example, a new root cause or contributing cause being added to the problem, or an update to a check on an existing unhealthy component.
ProblemSubsumedEventevent is generated when a change in root cause or the topology as a whole has caused an existing problem to be joined with another problem. For example, a new relation has been created.
ProblemResolvedEventevent is generated when the root cause component and all contributing cause components have reported a CLEAR (green) health state. No unhealthy components remain in the problem.