ServiceNow is a cloud-based workflow automation platform that provides a wide range of applications centered primarily around IT Service Management and IT Operations. This integration focuses on ServiceNow's Incident Management application, allowing Sleuth to source incident data from ServiceNow and evaluate how those incidents impact the overall health of your deploys (i.e. in terms of CFR and MTTR).
Note that the ServiceNow integration currently supports only ServiceNow's Incident object (an extension of ServiceNow's General Task object) and supports only the default state model for ServiceNow's Incident object, treating all states but Closed as an "open" failure with respect to CFR and MTTR.
To set up the the ServiceNow integration, you'll first need to enable it globally (i.e. for your Sleuth Organization).
To enable the ServiceNow integration for your Organization, perform the following steps:
- Click Integrations in Sleuth's left-hand sidebar.
- Select Incident from the drop-down to filter the list of available integrations (optional).
- Locate the ServiceNow card and click Enable
- Enter a fully qualified URL to your ServiceNow instance
- Enter the username and password for the service-level account that Sleuth will use to connect to ServiceNow. Note that the account used here must have read permissions for the following tables in ServiceNow:
- Click Save.
In order to leverage the ServiceNow integration within a given Sleuth Project, you'll need to add a ServiceNow Impact Source to that Project, where you can specify the unique filter criteria that will determine which specific ServiceNow incidents Sleuth will associate with that Project.
To add ServiceNow as an Impact Source for a specific Project, perform the following steps:
- From the left-hand-navigation panel, select the Project to which you'd like to add a new ServiceNow Impact Source
- Expand the More drawer, click + Add, and select Impact Source
- In the How do you track change failure drop-down, leave the default selection in place: Incident management (recommended)
- Under the Choose your service heading, select the ServiceNow tile.
- Click Enable and continue
- Provide a Name for your new Impact Source. Note that you might need to add multiple ServiceNow Impact Sources to cover all of the desired filter criteria combinations that you'd like to include the Project
- Configure the Impact Source by selecting the desired filters for the ServiceNow incident attributes that you would like to include in this Project.
- The Severity filter will include all ServiceNow Incidents with a Severity greater than or equal to the selected value.
- The Business service and Assignment Group filters are currently single-select, so if you'd like to include additional values for either attribute, you can do so by adding additional ServiceNow Impact Sources to the Project.
- The Custom filters text field allows you to filter incidents using custom attributes you've defined in ServiceNow by specifying any field-value pairings (e.g. u_business_service_subcat=somevalue). You can even add multiple custom fields by specifying each on a new line within this text field. You cannot, however, specify multiple values for this same field. Like Business service and Assignment group above, if you want to include multiple values for the same custom field, you can do so by adding additional ServiceNow Impact Sources to the Project.
- Under Advanced Settings, you can control historical data population. If checked, Sleuth will populate all incidents that happened in the last 30 days and recalculate the project's Failure Rate and MTTR metrics.
- Click Test Connection to validate that the new Impact Source is returning the expected incidents from ServiceNow.
- Click Save
Once you've configured a ServiceNow Impact Source, you should see that Impact Source and its health status listed on each new Deploy within that Project (as well as for the last 30 days of Deploys if you selected that option in the ServiceNow Impact Source):
You'll also find a chart listing all ServiceNow incidents from the last 14 days (and their health status) within the Impact Source record itself: