Trigger Inputs For Testing Runbooks

When you test 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. (using Execute a Test Run in the Runbook Editor), the Inputs dialog appears, prompting you to provide inputs interactively that 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. and other preceding nodes Individual components that make up a runbook automation, each performing a specific function such as data queries, transformations, logic, integrations, or visualizations. will supply when the runbook executes in automated use. The test inputs are:

• Application An entity type representing software applications deployed in the customer environment that are monitored for performance and anomalies./Device An entity type representing network devices or hardware components deployed in the customer environment that are monitored for performance and anomalies./Interface An entity type representing network interfaces on devices that are monitored for performance metrics and anomalies./Location An entity type representing physical or logical locations in the customer environment where entities are deployed and monitored.: Type the name of the object (application or device or interface or location, as appropriate for the runbook trigger) that you are testing this runbook for.

• Client Location: Choose the location that you are testing this runbook for.

• Mimic the multi-device automation trigger:Simulate the existence of multiple device triggers.

  Note: For Device trigger only

• Time: The default is Now.

• Trigger Metric: Choose the metric A measurement or data point that is monitored and analyzed to detect anomalies and generate incidents. passed from the trigger that you are testing this runbook for.

• Actual Value: Type the value to use for that metric.

• Acceptable Low Value: Type the value at the low end of the metric's acceptable range.

• Acceptable High Value: Type the value at the high end of the metric's acceptable range.

• Advanced:

  • Incident Variables: Type the incident 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. variables to be used in the test, along with their values. For example:
    {    
"incident.builtin.status": "New"
}

  • Timeout: The default is five minutes.