When something goes wrong within your IT environment StackState can alert you or your team mates with a message in the form of an email, Slack message, mobile ping or an HTTP POST request to any URL. Alerts can contain detailed content on the trigger event and possible root cause. This guide will help you set this up.
Alerts are triggered in response to health state changes on an element or view. The health state of an element is derived from metrics and events data in the telemetry streams assigned to it, whereas the health state of a view is calculated based on the combined health state of elements within it. Propagated state changes can also be used to trigger alerts, however, this can result in a lot of noise.
The process to trigger an event is as follows:
Telemetry streams attached to an element provide metrics and events data.
A health check attached to the element listens to the available telemetry streams and reports a health state based on its configured parameters.
When the reported health state of an element changes, a chain of state change events are generated:
HealthStateChangedEvent for the element itself.
PropagatedStateChangedEvent for all other elements that have been impacted by the element's state change.
ViewStateChangedEvent for each view containing the element. Note that this event type is only generated when a view's view state configuration criteria are met.
Event handlers associated with each view listen to the generated state change events and trigger the configured alerts and actions.
Event handlers respond to health state change events and run event handler functions to generate alerts and trigger automated actions. You can add an event handler to a view from the StackState UI.
Select Events Settings on the left.
Click ADD NEW EVENT HANDLER.
Select the trigger event and event handler to run:
On event - the type of state change events that should trigger the alert or automated action.
Run event handler - the event handler function that will run whenever the selected state change event type is generated. StackState ships with event handler functions that can send an alert via email, Slack or SMS, or POST to an HTTP webhook. You can also create your own custom functions. Read more about event handler functions.
Enter the required details, these will vary according to the event handler function you have selected.
In StackState, metrics and events data flow through topology elements in telemetry streams. These telemetry streams are used by health checks to determine the health state of the element. For every change in health state, at least one state change event is generated. Event handlers can be added to a view to listen to state change events generated within the view and trigger an alert or action when a configured threshold is passed.
The event types generated when an element state changes are described in the table below.
State change of an element Generated when the health state of an element changes. These events will be listed in the StackState UI Events Perspective.
Propagated state change of an element 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 for alerting.
State change of entire view 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 for alerting.
You can add an event handler to a view to trigger alerts or automated actions on specific state change events.