Set up custom episode actions in ITSI
Unique use cases can require custom alerting functionality and integration. In addition to the default actions you can take on an episode, ITSI also lets you define custom alert actions in notable_event_actions.conf.
Prerequisites
- Only users with file system access, such as system administrators, can set up custom episode actions.
- Review the steps in How to edit a configuration file in the Admin Manual.
Never change or copy the configuration files in the default directory. The files in the default directory must remain intact and in their original location. Make changes to the files in the local directory.
Steps
- Open or create a local version of
notable_event_actions.conf
atSPLUNK_HOME/etc/apps/SA-ITOA/local
. - Add a stanza for the action you want to perform. For example:
[itsi_sample_event_action_ping]
The stanza name should be same as the action name. For example, the stanza name in both alert_actions.conf and notable_event_actions.conf should be same.
- Set
disabled = 0
to enable the custom action.
For example:
[itsi_sample_event_action_ping] disabled = 0
For an example configuration, see notable_event_actions.conf.example.
Setting up custom alert actions via notable_event_actions.conf
only allows for a one-way integration. The episode will not contain a drilldown link to the action that was performed.
Integrate ITSI with Splunk SOAR (On-premises) | Overview of the ITSI Rules Engine |
This documentation applies to the following versions of Splunk® IT Service Intelligence: 4.11.0, 4.11.1, 4.11.2, 4.11.3, 4.11.4, 4.11.5, 4.11.6, 4.12.0 Cloud only, 4.12.1 Cloud only, 4.12.2 Cloud only, 4.13.0, 4.13.1, 4.13.2, 4.13.3, 4.14.0 Cloud only, 4.14.1 Cloud only, 4.14.2 Cloud only, 4.15.0, 4.15.1, 4.15.2, 4.15.3, 4.16.0 Cloud only, 4.17.0, 4.17.1, 4.18.0, 4.18.1, 4.19.0, 4.19.1
Feedback submitted, thanks!