https://step.dev/knowledgebase/30/categories/alerting/ Recent content in Alerting on Step Documentation Hugo -- gohugo.io en Mon, 17 Mar 2025 14:08:01 +0100 https://step.dev/knowledgebase/30/userdocs/alerting-notifications/alerting/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/30/userdocs/alerting-notifications/alerting/ Step includes a rule-based mechanism that allows users to define flexible reactions to various events. In a nutshell, rules allow you to define when to react to specific events (conditions), and how (actions). The following illustration presents the process in a simplified, informal form: Events Events are automatically generated by the Step environment and fed into the alerting rules evaluation component. Events contain further details about what happened, in the form of Bindings. https://step.dev/knowledgebase/30/userdocs/agent-provisioning/ Mon, 30 Sep 2024 00:00:00 +0000 https://step.dev/knowledgebase/30/userdocs/agent-provisioning/ When running in Kubernetes, Step supports automatic provisioning of Agents (i.e. automatic provisioning of the containers responsible for executing Keywords) across multiple Kubernetes clusters. This page explains how to utilize Agent provisioning in Plans. For information on enabling or configuring Agent provisioning, please refer to the Agent Provisioning configuration page. How it works In a nutshell, the automatic Agent provisioning works as follows: Upon execution, Plans are scanned to determine the required Agents for execution Based on the calculation and the available Agent pools, the optimal number of Agents per Agent pool is calculated The required Agents are provisioned across the clusters of the selected Agent pools Once the Agents have joined the grid, the execution starts After execution, the agents are de-provisioned Configure provisioning settings in Plans When Agent provisioning is enabled in Step, users can configure the Agent provisioning settings in each plan (in the UI and in the automation packages). https://step.dev/knowledgebase/30/userdocs/alerting-notifications/ Mon, 17 Mar 2025 14:08:01 +0100 https://step.dev/knowledgebase/30/userdocs/alerting-notifications/ Step includes a flexible mechanism for sending notifications in tandem with the definition of Alerting Rules, allowing to define exactly which events and conditions will result in which notification being sent. https://step.dev/knowledgebase/30/userdocs/incidents/ Thu, 28 Feb 2019 14:08:01 +0100 https://step.dev/knowledgebase/30/userdocs/incidents/ Incidents are used to be aware of problems in the infrastructure: for instance, Step can periodically run plans which test the behavior of a system. When these plans fail to execute correctly, or (user-defined) assertions concerning the performance do not hold, this constitutes an incident. Step allows incidents to be automatically created and managed according to user-defined alerting rules. These rules are evaluated in response to various events (most notably after every plan execution).