Event notifications

StackState Self-hosted v5.0.x

This page describes StackState version 5.0.

Go to the documentation for the latest StackState release.

Overview

When something goes wrong within your IT environment, StackState can send event notifications to alert you or your team mates. 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.

Event handlers

Event handlers can be added to a StackState view to send event notifications or trigger actions in response to health state change events or problem events that are generated within the view. The event handler will listen to generated events and run a configured event handler function when the configured event type is generated.

You can add an event handler to a view from the StackState UI Manage Event Handlers panel.

Event types for notifications

Event handlers can be configured to respond to state change events and problem events.

Only events related to components are captured in event handlers, relation-related events will be ignored.

State change events

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. Use the Manage Event Handlers panel to add an event handler to the view and trigger an event notification or action whenever state changed events are generated.

The event types generated when an element state changes are described in the table below.

Problem events

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. Use the Manage Event Handlers panel to add an event handler to the view and trigger an event notification or action whenever problem events are generated.

Changes to a problem result in the following event types being generated. Note that there may be a slight delay between the generation of a health state change event for an element and the resulting Problem event:

➑️ Learn more about the problem lifecycle

See also

Last updated