| Specification | Details |
|---|---|
| Repository type | Cloud |
| Supported content | Incidents, Events, On-Calls |
| RACL support | Yes |
| Content filtering | No |
Prerequisites
Search AI uses OAuth 2.0 Password Grant Type to authenticate with xMatters. The authorization token grants the same permissions in xMatters as the user account used to create it. Retrieve the OAuth Client ID from xMatters before configuring the connector:- In xMatters, navigate to Workflows > OAuth.
- Copy the Client ID. This is unique to your xMatters company and is required during connector configuration.
Configuring the xMatters Connector in Search AI
Navigate to the xMatters Connector and enter the following details on the Authentication page.| Field | Description |
|---|---|
| Name | Unique identifier for the connector |
| Domain | Your xMatters company subdomain (for example, if your domain is test.xmatters.com, enter only test) |
| Client ID | OAuth Client ID from your xMatters instance |
| Username | Username of the account used to authenticate requests |
| User Password | Password of the account used to authenticate requests |
Content Ingestion
Search AI ingests the following content types from xMatters:- Incidents
- Alerts (also referred to as Events)
- On Calls
doc_source_type field identifies the content type of each ingested document. Additional metadata is available in the respective fields of each document.
Access Control
For incidents and alerts, thesys_racl field contains the following permission entities:
- User ID of the commander (if available)
- User ID of the resolvers (if available)
- User ID of the creator
- Group ID of one or more involved groups (if applicable)
sys_racl field contains:
- Group ID