Per-node Execution Detail Step 2: Processing Logic

Logic: Decision Branch

This node provides the ability to specify conditions in which the runbookClosed 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. execution branches. See the Logic: Decision Branch page for more details.

The Example InterfaceClosed An entity type representing network interfaces on devices that are monitored for performance metrics and anomalies. Runbook employs Logic: Decision Branch to determine path of Runbook execution based on the type of Primary IndicatorClosed An observed change in a specific metric stream that is recognized as being outside of an expected model. Indicators are correlated into triggers, and one or more triggers are grouped into incidents. that triggeredClosed 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. the Runbook execution. For example, one path to investigate MetricClosed A measurement or data point that is monitored and analyzed to detect anomalies and generate incidents.: Interface StatusClosed The current state of an incident or runbook, indicating its progress through investigation and resolution workflows. related incidentsClosed 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. and another path to investigate Metric: In Packet Error Rate related incidents.

Example Interface Runbook configuration

The Example Interface Runbook configures Logic: Decision Branch with:

  1. Label: Default-value.

  2. OUTPUTS: The set of logic-checks that determine the Path of Runbook execution (the first successful logic-check is followed), e.g.:

    1. OUTPUTClosed A document containing data sets generated by the execution of a runbook, including output of queries and reports from point products, as well as output of analysis or other runbook nodes. 1: Checks to determine if the Interface Incident had a triggering Primary Indicator of Metric: Interface Status.

      1. If this is the case, then the path of Runbook execution will next process VisualizationsClosed A runbook node category that shows data in a chart, graph, table, or note, providing visual representation of analysis results in runbook output.: Cards.

      2. If this is not the case, then proceeds to the next logic-check/OUTPUT.

    2. OUTPUT 2: Checks to determine if the Interface Incident had a triggering Primary Indicator of Metric: In Packet Error Rate.

      1. If this is the case, then the path of Runbook execution will next process Visualizations: Timeseries Chart.

      2. If this is not the case, then proceeds to the next logic-check/OUTPUT.

This set of Logic: Decision Branch properties configures two potential paths of execution:

  1. Interface Incidents originating from Metric: Interface Status.

  2. Interface Incidents originating from Metric: In Packet Error Rate.

Previous Step | Next Step