<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Automations</title><link>https://docs.sysdig.com/en/sysdig-monitor/alerts/automations/</link><description>Recent content on Automations</description><language>en</language><lastBuildDate>Mon, 04 May 2026 10:16:23 +0200</lastBuildDate><image><url> https://docs.sysdig.com/icons/sysdig-horizontal.png</url><title>Automations</title><link>https://docs.sysdig.com/en/sysdig-monitor/alerts/automations/</link><description>Sysdig logo</description></image><item><title>Automations - Create an Automation</title><link>https://docs.sysdig.com/en/sysdig-monitor/alerts/automations/#create-an-automation</link><description>To create a new automation:</description><content:encoded><![CDATA[<p>To create a new automation:</p>

<ol>

<li>

<p>Log in to Sysdig Monitor.</p>
</li>

<li>

<p>Select <strong>Alerts</strong> from the left navigation bar.</p>
</li>

<li>

<p>Select <strong>Automations</strong> from the sub-menu.</p>

<p>The <strong>Automations</strong> page appears, showing all existing automations with their name, status, last execution time, and last modified date.</p>
</li>

<li>

<p>Select <strong>New Automation</strong> in the top-right corner.</p>

<p>The automation editor opens. The <strong>Alert Occurrence</strong> node at the top of the flow represents the entry point — it is activated when an alert that is linked to this automation fires. Proceed to <a href="/en/sysdig-monitor/alerts/automations/#configure-an-automation">Configure an Automation</a>.</p>
</li>
</ol>]]></content:encoded><guid isPermaLink="false">Create an Automation</guid></item><item><title>Automations - Integrate Automations with Alerts</title><link>https://docs.sysdig.com/en/sysdig-monitor/alerts/automations/#integrate-automations-with-alerts</link><description>Automations are activated by alerts that are explicitly linked to them. To link an alert to an automation, open the alert in the Alert Editor and select the automation from the Automations field in the Notifications section. An alert can be linked to multiple automations, and a single automation can be linked to multiple alerts.</description><content:encoded><![CDATA[<p>Automations are activated by alerts that are explicitly linked to them. To link an alert to an automation, open the alert in the <a href="/en/sysdig-monitor/configure-alerts/">Alert Editor</a> and select the automation from the <strong>Automations</strong> field in the <strong>Notifications</strong> section. An alert can be linked to multiple automations, and a single automation can be linked to multiple alerts.</p>]]></content:encoded><guid isPermaLink="false">Integrate Automations with Alerts</guid></item><item><title>Automations - Configure an Automation</title><link>https://docs.sysdig.com/en/sysdig-monitor/alerts/automations/#configure-an-automation</link><description>You can build automations visually through logic chains of conditions and actions.</description><content:encoded><![CDATA[<p>You can build automations visually through logic chains of conditions and actions.</p>

<h3 id="filters">Filters</h3>
<p>Filters let you limit a condition node to a specific subset of alert events.</p>

<p>The following suggested filters are available:</p>

<ul>

<li><strong>Alert Type</strong>: The type of alert, such as <code>threshold</code>, <code>prometheus</code>, <code>event</code>, <code>group_outlier</code>, <code>change</code>, or <code>downtime</code>.</li>

<li><strong>Severity</strong>: The alert severity level: <code>high</code>, <code>medium</code>, <code>low</code>, or <code>info</code>.</li>

<li><strong>Threshold</strong>: The name of the alert rule.</li>

<li><strong>Group</strong>: The group the alert belongs to.</li>
</ul>


<p>In addition to these, you can filter on any of the <strong>Labels</strong> (50+) available in your environment, including agent tags and Kubernetes labels such as <code>agent.tag.region</code>, <code>kubernetes.namespace.name</code>, and others.</p>

<p>You can combine multiple filters within a single node using <strong>AND</strong> logic.</p>

<h3 id="actions">Actions</h3>
<p>Select the <strong>+</strong> icon below any node to add an action. The <strong>Select an Action</strong> modal provides the following options:</p>

<h4 id="condition">Condition</h4>
<p>Add a <strong>Condition</strong> node to branch the automation flow based on alert properties. A condition evaluates to either <strong>TRUE</strong> or <strong>FALSE</strong>, and you can attach different subsequent actions to each outcome.</p>

<p>Configure a condition using the same filter options available on the trigger. For example:</p>

<ul>

<li><code>Alert Type</code> <code>in</code> <code>threshold</code> AND <code>Severity</code> <code>in</code> <code>high</code></li>
</ul>


<h4 id="notifications">Notifications</h4>
<p>Send notifications to any of the following channels when the automation runs:</p>

<ul>

<li><strong>Slack</strong>: Send a message to a configured Slack channel.</li>

<li><strong>MS Teams</strong>: Send a message to a Microsoft Teams channel.</li>

<li><strong>Email</strong>: Send an email to a configured email notification channel.</li>

<li><strong>Webhook</strong>: Send a payload to a configured webhook URL.</li>

<li><strong>PagerDuty</strong>: Trigger or resolve an incident in PagerDuty.</li>

<li><strong>SNS</strong>: Publish a message to an Amazon SNS topic.</li>

<li><strong>Google Chat</strong>: Send a message to a Google Chat space.</li>

<li><strong>OpsGenie</strong>: Create or close an alert in OpsGenie.</li>

<li><strong>Prometheus Alert Manager</strong>: Forward the alert to a Prometheus Alertmanager instance.</li>

<li><strong>Team Email</strong>: Send an email to a Sysdig team&rsquo;s email address.</li>

<li><strong>Victor Ops</strong>: Send an alert to a VictorOps (Splunk On-Call) channel.</li>
</ul>


<p>To use any notification action, you must first set up the corresponding notification channel. See <a href="/en/docs/administration/administration-settings/notifications-management/set-up-notification-channels/">Set Up Notification Channels</a>.</p>

<h4 id="other">Other</h4>
<ul>

<li><strong>Custom Webhook</strong>: Send a customized HTTP request to any endpoint, independent of a pre-configured notification channel.</li>
</ul>


<h3 id="enable-or-disable-an-automation">Enable or Disable an Automation</h3>
<p>Use the <strong>Enabled</strong> toggle in the top-right corner of the editor to activate or deactivate an automation. Disabled automations will not run even when a linked alert fires.</p>

<h3 id="save-an-automation">Save an Automation</h3>
<p>Select <strong>Save</strong> in the top-right corner to save your automation. You cannot save an automation with an incomplete configuration, for example, if a notification action has not been linked to a notification channel.</p>]]></content:encoded><guid isPermaLink="false">Configure an Automation</guid></item><item><title>Automations - Review Executions</title><link>https://docs.sysdig.com/en/sysdig-monitor/alerts/automations/#review-executions</link><description>Each time an automation is triggered, Sysdig logs the execution so you can monitor and debug your automation flows.</description><content:encoded><![CDATA[<p>Each time an automation is triggered, Sysdig logs the execution so you can monitor and debug your automation flows.</p>

<p>To review executions:</p>

<ol>

<li>

<p>Log in to Sysdig Monitor.</p>
</li>

<li>

<p>Select <strong>Alerts</strong> &gt; <strong>Automations</strong>.</p>
</li>

<li>

<p>Select an existing automation.</p>
</li>

<li>

<p>Select the <strong>Executions</strong> tab.</p>

<p>The executions log shows the history of all times the automation was triggered, including:</p>

<ul>

<li><strong>Time</strong>: The timestamp of the execution.</li>

<li><strong>Status</strong>: Whether the execution <strong>Succeeded</strong> or <strong>Failed</strong>.</li>

<li><strong>Failing Nodes</strong>: The nodes that failed, if any.</li>
</ul>


<p>You can filter the list by <strong>All</strong>, <strong>Succeeded</strong>, or <strong>Failed</strong>.</p>
</li>

<li>

<p>Select an execution to inspect its details.</p>

<p>The execution detail view shows:</p>

<ul>

<li><strong>Execution Context</strong>: The status and result (<code>True</code> or <code>False</code>) of each node, along with the variable values that were evaluated at the time of execution.</li>

<li><strong>Configuration</strong>: The automation configuration as it was at the time of execution.</li>
</ul>


<p>You can also select <strong>Download JSON</strong> to export the full execution context for further analysis.</p>

<p>Nodes that executed successfully are highlighted in green in the flow diagram. Failed nodes are highlighted in red.</p>
</li>
</ol>

<div class='row alert d-flex infobox infobox--note'>
  <div class="ps-0 col-md-auto">
  <i class='fas fa-info-circle fa-lg'></i>
  </div>
  <div class="ps-0 col infobox__contents">

<p>Each execution record is a snapshot. If you later modify the automation, previous executions continue to display the automation flow as it was when they ran, so you can debug them against the configuration that was actually in effect at the time.</p>
  </div>
</div>]]></content:encoded><guid isPermaLink="false">Review Executions</guid></item><item><title>Automations - Delete an Automation</title><link>https://docs.sysdig.com/en/sysdig-monitor/alerts/automations/#delete-an-automation</link><description>To delete an automation:</description><content:encoded><![CDATA[<p>To delete an automation:</p>

<ol>

<li>

<p>Log in to Sysdig Monitor.</p>
</li>

<li>

<p>Select <strong>Alerts</strong> &gt; <strong>Automations</strong>.</p>

<p>The <strong>Automations</strong> page appears.</p>
</li>

<li>

<p>On the right side of an automation listing, select the three-dot menu icon.</p>
</li>

<li>

<p>Select <strong>Delete</strong>, and confirm the deletion.</p>
</li>
</ol>

<div class='row alert d-flex infobox infobox--note'>
  <div class="ps-0 col-md-auto">
  <i class='fas fa-info-circle fa-lg'></i>
  </div>
  <div class="ps-0 col infobox__contents">

<p>Deleting an automation does not remove it from any alerts it was linked to. You must manually remove the automation from each linked alert in the <a href="/en/sysdig-monitor/configure-alerts/">Alert Editor</a> before you can save further changes to those alerts.</p>
  </div>
</div>]]></content:encoded><guid isPermaLink="false">Delete an Automation</guid></item></channel></rss>