Set Service action
Available for event and incident workflows |
This action adds to or replaces the service list of an event or incident with user-specified services.
The standard practice is to place this action after a filter in the Workflow trigger or an action such as Time Filter Action.
This action takes the following inputs:
Action
Select one of the following options:
Replace all service names
Add to any service names that already exist
Note
New service names are always appended to the end of the existing list of services.
Service
The new service names that should go into the service field list of the event or incident. You can provide the service names one of two ways:
Data from another field
Pass data from another selected field in the event or incident.
Text
Provide the new service names as text. Enter the name of the new service without using any quotes.
Event example
Set Service works the same way for both incidents and events. In both cases, it supplements or substitutes the list of services associated with an event or incident with services chosen by the user.
Suppose you want to change the value of the service field for all events coming from a particular source. You can accomplish this by creating an event workflow using a Set Service action.
After setting up the Trigger to activate the workflow only for relevant source events, you can configure the Set Service action as follows:
Action
Replace all service names
Service
Text:
payment
Here is an example event that was processed by this workflow:
Event fields before | Event fields after |
---|---|
{ "description": "CPU spike to 80%", "severity": 5, "source": "ussf-sw99", "check": "cpu", "service": [ "retail", "support" ], "tags": { "devicename": "sw99" } } | { "description": "CPU spike to 80%", "severity": 5, "source": "ussf-sw99", "check": "cpu", "service": [ "payment" ], "tags": { "devicename": "sw99" } } |
Incident example
Suppose you want to add a new service name to all new incidents. You can accomplish this by creating an incident workflow with a Set Service action.
After setting up the Trigger, you can configure the Set Service action as follows:
Action
Add to any service names that already exist
Service
Text:
payment
Here is an example incident that was processed by this workflow:
Incident fields before | Incident fields after |
---|---|
{ .... "services": [ "support", "retail" ], } | { .... "services": [ "support", "retail", "payment" ], } |