This is an updated and improved version of the Opsgenie integration! If you’re setting up an Opsgenie integration with ConductorOne for the first time, you’re in the right place.

Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather Opsgenie credentials

Each setup method requires you to pass in credentials generated in Opsgenie. Gather these credentials before you move on.

A user with the Owner or Admin role (or a custom user role with the Edit Configuration user right) in Opsgenie must perform this task.

Generate a new API key

1. Log into Opsgenie and navigate to Profile settings > API key management.

2. Click Add new API key.

3. Give the API key a name, such as ConductorOne.

4. Give the API key Read and Configuration access access rights.

5. Click Add API key.

6. The new API key is generated for you. Carefully copy and save the API key.

That’s it! Next, move on to the instructions for your chosen setup method.

Set up an Opsgenie cloud-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of Opsgenie credentials generated by following the instructions above

1. In ConductorOne, click Connectors > Add connector.

2. Search for Opsgenie and click Add.

3. Choose how to set up the new Opsgenie connector:

   • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)

   • Add the connector to a managed app (select from the list of existing managed apps)

   • Create a new managed app

4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.

   If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.

5. Click Next.

6. Find the Settings area of the page and click Edit.

7. Paste the API key into the API key field.

8. Click Save.

9. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

That’s it! Your Opsgenie connector is now pulling access data into ConductorOne.

Set up an Opsgenie cloud-hosted connector using Terraform

As an alternative to the cloud-hosted setup process described above, you can use Terraform to configure the integration between Opsgenie and ConductorOne.

See the ConductorOne Opsgenie v2 integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.

Set up an Opsgenie self-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of Opsgenie credentials generated by following the instructions above

When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.

Why use Kubernetes? Kubernetes provides automated deployment, scaling, and management of your connectors. It ensures high availability and reliable operation of your connector services.

Step 1: Configure the Opsgenie connector

1. In ConductorOne, navigate to Connectors > Add connector.

2. Search for Baton and click Add.

3. Choose how to set up the new Opsgenie connector:

   • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with ConductorOne)

   • Add the connector to a managed app (select from the list of existing managed apps)

   • Create a new managed app

4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of ConductorOne users. Setting multiple owners is allowed.

   If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.

5. Click Next.

6. In the Settings area of the page, click Edit.

7. Click Rotate to generate a new Client ID and Secret.

   Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Opsgenie connector deployment:

Secrets configuration

# baton-opsgenie-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-opsgenie-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Opsgenie credentials
  BATON_API_KEY: <Opsgenie API key>

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-opsgenie.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-opsgenie
  labels:
    app: baton-opsgenie
spec:
  selector:
    matchLabels:
      app: baton-opsgenie
  template:
    metadata:
      labels:
        app: baton-opsgenie
        baton: true
        baton-app: opsgenie
    spec:
      containers:
      - name: baton-opsgenie
        image: ghcr.io/conductorone/baton-opsgenie:latest
        args: ["service"]
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-opsgenie-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run ConductorOne connectors (if desired):

   kubectl create namespace baton-opsgenie
   

2. Apply the secret configuration:

   kubectl -n baton-opsgenie apply -f baton-opsgenie-secrets.yaml
   

3. Apply the deployment:

   kubectl -n baton-opsgenie apply -f baton-opsgenie.yaml
   

Step 4: Verify the deployment

1. Check that the deployment is running:

   kubectl -n c1 get pods
   

2. View the connector logs:

   kubectl -n c1 logs -l app=baton-${baton-opsgenie}
   

3. Check that the connector data uploaded correctly. In ConductorOne, click Applications. On the Managed apps tab, locate and click the name of the application you added the Opsgenie connector to. Opsgenie data should be found on the Entitlements and Accounts tabs.

That’s it! Your Opsgenie connector is now pulling access data into ConductorOne.