Configure episode action rules in ITSI
Set up action rules within an aggregation policy in IT Service Intelligence (ITSI) to take automated actions when an episode's activation criteria are met. Action rules are optional. You can define more than one action rule per aggregation policy. For more information about aggregation policies, see Overview of aggregation policies in ITSI.
For example, if you want to close the episode and change the episode severity level to
Info when a notable event comes in, you could specify the following rule:
If the following event occurs:
Normal, change severity to
Info for the episode, add a comment
Don't worry for the episode, and change status to
Closed for the episode.
Action rules consist of the following distinct parts:
|Activation Criteria||A set of WHERE clauses that determine when the trigger conditions for a specific action are met.|
|Action||A set of THEN clauses that represent the things being done to an episode when the activation criteria are met. Examples of actions taken on episodes include changing the status, severity, or owner of an episode. Actions can also be taken on things other than the specific episode that triggered the action. Examples of external actions include pinging a host, sending an email, or creating a ticket in an external ticketing system.|
Choose from the following conditions that trigger an action:
|The following event occurs||Trigger an action when an event containing specific field values is added to the episode. For example, when |
|The episode existed for||Trigger an action if the episode has existed for a given amount of time, in seconds. You might close an episode if it's existed for 86400 seconds (one day).|
|The number of events in the episode is||Trigger an action if the number of events in the episode exceeds or does not reach a certain limit. By default, an episode breaks when it reaches 10,000 events, and a new episode is created.|
|The flow of events into the episode paused for||Trigger an action if the episode hasn't received any events for a given amount of time, in seconds.
The maximum value for this field is
Choose from the following actions to take on an episode:
|Change severity||For example, change the severity to |
|Change status||For descriptions of each status, see Update the status of an episode.
Changing an episode's status to
|Change owner||Episodes are unassigned by default.|
|Add a comment||Does not accept token replacement.|
|Ping a host||Determine whether a host is still active on the network by pinging the host. Provide the event field that contains the host that you want to ping in the Host field. For example, |
|Send an email||Send an email to the appropriate team as a result of an event. Make sure the mail server is configured in the Splunk platform before configuring this action.
You can use tokens in the email subject or message. The tokens are replaced with field values in the email message. The following episode fields are available:
You can also use fields contained in the last event in the episode. If a field isn't present in the last event, although it may exist in other events in the episode, ITSI does not replace the token with the field value in the email message.
Optionally, select a message template which populates the message field with a preconfigured email body. Tokens are supported in templates. Click Manage templates to configure additional templates or remove existing ones. Anyone with the admin, itoa_admin, or itoa_analyst role can create and edit email templates. Once you create a template it's available for selection in all aggregation policies and is not policy-specific.
|Run a script||Provide the file name of the script stored in |
External episode actions
In addition to the default episode actions included with ITSI, you can also integrate with certain third-party alerting systems. Once you configure an integration, you can set up action rules that create tickets in those third-party systems when certain activation criteria are met.
ITSI offers the following external actions you can take within integrated systems:
|Create an incident in ServiceNow||Requires the Splunk Add-on for ServiceNow. For configuration information, see Integrate ITSI with ServiceNow.|
|Create an incident in Remedy||Requires the Splunk Add-on for Remedy. For configuration information, see Integrate ITSI with BMC Remedy.|
|Create an incident in VictorOps||Requires VictorOps For Splunk. For configuration information, see Integrate ITSI with VictorOps.|
For more information about the integrations shipped with ITSI, see Overview of episode ticketing integrations in ITSI.
Configure episode information and episode dashboards in ITSI
Dispatch episode actions to a remote ITSI instance
This documentation applies to the following versions of Splunk® IT Service Intelligence: 4.8.0 Cloud only, 4.8.1 Cloud only, 4.9.0, 4.9.1, 4.9.2, 4.9.3, 4.9.4, 4.9.5, 4.9.6, 4.10.0 Cloud only, 4.10.1 Cloud only, 4.10.2 Cloud only, 4.10.3 Cloud only, 4.10.4 Cloud only, 4.11.0, 4.11.1, 4.11.2, 4.11.3, 4.11.4, 4.11.5, 4.12.0 Cloud only, 4.12.1 Cloud only, 4.13.0