Configure An Automation Rule

An automation Automated procedures that are executed as the result of a trigger. Automations consist of a single entry point and a sequence of connected nodes that define the processing logic. rule is a set of instructions that automatically triggers A set of one or more indicators that have been correlated based on certain relationships, such as time, metric type, application affected, location, or network device. specific actions in response to defined conditions or events. These rules are designed to streamline routine tasks, reduce manual intervention, and ensure consistent responses to common scenarios. By configuring automation rules, users can define what should happen when certain thresholds are met, incidents A collection of one or more related triggers. Relationships that cause triggers to be combined into incidents include application, location, operating system, or a trigger by itself. occur, or particular patterns are detected, such as sending notifications, updating records, or launching diagnostic workflows.

In the context of runbooks An automated workflow that executes a series of steps or tasks in response to a triggered event, such as the detection of anomalous behavior generating an incident, a lifecycle event, or a manually executed runbook., automation rules serve as the bridge between real-time events and the operational procedures documented in your runbooks. When an automation rule is triggered, it can automatically initiate a runbook, ensuring that the appropriate troubleshooting or remediation steps are executed without delay. This integration helps organizations respond faster to incidents, maintain system reliability, and free up technical staff to focus on more complex issues. Using automation rules in conjunction with runbooks creates a proactive, efficient, and scalable approach to managing IT operations.

Create a new automation rule

1. Navigate to the Automation Management page:

   1. Click the Launchpad button ⁝⁝⁝.
   2. Click AI Ops > Automations.
   3. In the Management page, click the Hamburger Icon, then click Automation Management.

2. Either:

   1. In the Automation Management homescreen, click Add Automation For Incident Triggers, Add Automation For Lifecycle Triggers, or Add Automation for External Triggers.

   2. Or, click into the specific issue that you want to create a new trigger for, i.e. Interface Performance Issue, then click Add Automation.

3. Proceed through the Add an Automation pop up.

   1. Select a trigger.

   Note: If you navigate to a specific issue, this step will automatically populate with the issue you began with. Otherwise, you must select a trigger from the drop down.

   2. (Optional) Define conditions on the trigger A set of one or more indicators that have been correlated based on certain relationships, such as time, metric type, application affected, location, or network device..

   3. Configure the automation to execute a runbook An automated workflow that executes a series of steps or tasks in response to a triggered event, such as the detection of anomalous behavior generating an incident, a lifecycle event, or a manually executed runbook. when trigger conditions are met.

      Note: You can choose to disable this step, however you cannot enable an automation that does not execute a runbook.

      1. Select the runbook you want to execute. You can also create a new runbook from this step.

   4. Finalize the automation.

      1. Give the Automation a name and description.

      2. Give the automation an order number. If multiple automations match the trigger, only the first automation in the specified order will be performed.

   5. Submit.

   6. The page should refresh and your automation rule appears.