<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Alerting and notifications on Step Documentation</title>
    <link>https://step.dev/knowledgebase/30/userdocs/alerting-notifications/</link>
    <description>Recent content in Alerting and notifications on Step Documentation</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Mon, 17 Mar 2025 14:08:01 +0100</lastBuildDate><atom:link href="https://step.dev/knowledgebase/30/userdocs/alerting-notifications/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Notifications</title>
      <link>https://step.dev/knowledgebase/30/userdocs/alerting-notifications/notifications/</link>
      <pubDate>Thu, 28 Feb 2019 14:08:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/30/userdocs/alerting-notifications/notifications/</guid>
      <description>Step includes a flexible mechanism for sending notifications using various methods. Such notifications are meant to work in tandem with the Alerting Rules, allowing to define exactly which events and conditions will result in which notification being sent, with what data.
In order to use Preset-based notifications, Step administrators must define at least one System Notification Preset. Introduction and Example Step currently supports two kinds of notifications: good old E-Mails, and Webhook calls.</description>
    </item>
    
    <item>
      <title>Alerting rules</title>
      <link>https://step.dev/knowledgebase/30/userdocs/alerting-notifications/alerting/</link>
      <pubDate>Thu, 28 Feb 2019 14:08:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/30/userdocs/alerting-notifications/alerting/</guid>
      <description>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.</description>
    </item>
    
    <item>
      <title>Execution Subscriptions</title>
      <link>https://step.dev/knowledgebase/30/userdocs/alerting-notifications/subscriptions/</link>
      <pubDate>Thu, 28 Feb 2019 14:08:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/30/userdocs/alerting-notifications/subscriptions/</guid>
      <description>From a user&amp;rsquo;s perspective, it is often useful to be notified about certain events, like the execution (or failure) of particular plans. This is possible by leveraging the functionality of the Alerting Rules and Notifications.
Expert users can create the corresponding rules themselves, however this is not necessarily a straightforward task, and figuring out the exact definitions may be cumbersome. Therefore, Step provides a simple Wizard which allows to set up notifications in an easy way.</description>
    </item>
    
  </channel>
</rss>
