<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Incidents on Step Documentation</title>
    <link>https://step.dev/knowledgebase/30/categories/incidents/</link>
    <description>Recent content in Incidents on Step Documentation</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Thu, 28 Feb 2019 14:08:01 +0100</lastBuildDate><atom:link href="https://step.dev/knowledgebase/30/categories/incidents/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Incidents</title>
      <link>https://step.dev/knowledgebase/30/userdocs/incidents/</link>
      <pubDate>Thu, 28 Feb 2019 14:08:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/30/userdocs/incidents/</guid>
      <description>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).</description>
    </item>
    
  </channel>
</rss>
