| Specification | Details |
|---|---|
| Repository type | Cloud |
| Supported content | Alerts and Incidents |
| RACL support | Yes |
| Content filtering | No |
Prerequisites
- An Opsgenie account with API Key Management access.
Generate an API Key
- In Opsgenie, go to Settings > App Settings > API Key Management.
- Click Add New API Key.
- Enter a name for the key and select Read Access and Configuration Access. The key is generated automatically. Regenerate it before saving if needed.
- Click Add API Key to save.
Configure the Connector in Search AI
On the Authentication page of the Opsgenie Connector, enter the following details and click Connect.| Field | Description |
|---|---|
| Name | Unique name for the connector |
| Customer Name | Customer name as shown on the Profile Settings page in Opsgenie |
| API Key | API key generated in Opsgenie |
Content Ingestion
Search AI ingests Alerts and Incidents from Opsgenie in JSON format. Thedoc_source_type field indicates whether the record is an alert or an incident.
Key fields for both content types:
| Field | Description |
|---|---|
| Title | Alert or incident message |
| Content | Description, acknowledgement status, responders, and other details |
| Doc_created_on / Doc_updated_on | Creation and last update timestamps |
| Status | Status at the time of sync |
| Priority | Priority assigned to the alert or incident |
| Labels | Set of labels for the alert or incident |
RACL Support
The Opsgenie Connector restricts access to ingested content based on the responders field. Each alert or incident is visible only to users listed as responders on that record. Thesys_racl field includes:
- Email IDs of individual users who are direct responders.
- Team IDs of teams assigned as responders.