Skip action
Available for event, alert, and incident workflows |
The Skip action causes all workflow processing of an alert to stop immediately. Processing by the current workflow stops, and all subsequent workflows in the list are skipped.
Skip has no configuration. It is often used after a filter action or some other type of action that performs an evaluation step.
Event example
If some of your events are missing information which must be added from data catalogs using event workflows, you can use a filter to check your events for the presence of the data and, if no enrichment is required, use a Skip action avoid any processing events with already populated values.
Alert example
If you have an environment where extensive workflow processing is required to prepare particular alerts (from a certain country, a certain severity, a particular network or other factor) for correlation, you can use Skip to avoid all workflow processing for alerts which do not require such processing. You can include a filter and a Skip action to allow the simpler alerts to go directly to the correlation engine.
Incident example
Suppose you want to extensively process all of your incidents where severity = critical and send them to ServiceNow, except for incidents created from metrics dealing with memory availability issues. You can create a workflow with a filter that examines incidents for a metric containing the string "memory":
.*memory.*
Then, add a Skip action to the workflow after the filter.
All matching incidents are then directed to a Skip action, where they avoid any further processing. The rest of the incidents continue processing in additional workflows.