> ## Documentation Index
> Fetch the complete documentation index at: https://koreai.mintlify.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Opsgenie Connector

<Badge icon="arrow-left" color="gray">[Back to Search AI connectors list](/ai-for-service/searchai/content-sources#supported-connectors)</Badge>

Opsgenie is an incident management platform that receives alerts from monitoring tools, prioritizes them by urgency, and notifies the right people immediately. The Search AI Opsgenie Connector ingests **alerts** and **incidents** for tracking and analysis.

| 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

1. In Opsgenie, go to **Settings > App Settings > API Key Management**.
2. Click **Add New API Key**.
3. Enter a name for the key and select **Read Access** and **Configuration Access**. The key is generated automatically. Regenerate it before saving if needed.
4. 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. The `doc_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                            |

View the complete field set on the **Content** page of the connector.

## 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.

The `sys_racl` field includes:

* **Email IDs** of individual users who are direct responders.
* **Team IDs** of teams assigned as responders.

A permission entity is automatically created for each team ID. Use the **Permission Entity APIs** to associate individual users with team IDs, granting them access to the corresponding alerts and incidents.