OpsGenie Integration
Synchronize on-call schedules, escalation policies, and user information.
Synchronize on-call schedules, escalation policies, and user information from OpsGenie to Harness AI SRE.
Overview
The OpsGenie integration enables you to:
Import schedules: Synchronize rotation schedules with shifts and time zones
Import escalation policies: Bring existing escalation chains into AI SRE
Import teams: Synchronize user groups and team structures
Import user details: Sync contact information including email, SMS, and phone numbers
Maintain consistency: Keep on-call configurations aligned between systems
Prerequisites
OpsGenie account with administrator access
OpsGenie API key with read permissions
OpsGenie region (US or EU)
Harness project with On-Call Management enabled
Configure OpsGenie sync
Step 1: Generate API key
Create a read-only API key in OpsGenie for the integration:
Log in to OpsGenie
Navigate to Settings → API Key Management
Click Add New API Key
Configure the API key:
Name: Enter "Harness AI SRE Integration"
Access Rights: Select Read permissions for schedules, teams, and users
Click Create
Copy the generated API key
Step 2: Connect OpsGenie to AI SRE
Add OpsGenie as a sync source and verify the connection:
In Harness AI SRE, navigate to On-Call → Sync from 3rd Party tab
Click Connect Source
Select OpsGenie as the source system
Configure the connector:
API Key: Paste the API key from Step 1
Region: Select US or EU based on your OpsGenie instance location
Click Test Connection to verify credentials
Click Next: Select Entities
Step 3: Select entities to sync
Choose which OpsGenie entities to import and preview the results:
Choose which services to synchronize:
All Services: Import all OpsGenie services
Specific Services: Select individual services to import
Review the preview showing what will be imported:
Schedules with rotation patterns
Escalation policies with levels and timeouts
Groups mapped to Harness User Groups
People with contact information
Click Next: Invite Users
Step 4: Invite users to Harness
Invite the discovered users so they can receive pages in Harness:
Review the list of discovered users from OpsGenie
Select users who need Harness accounts to receive pages
Selected users will receive email invitations to join Harness
Users already in Harness will be automatically mapped by email
Click Next: Configure Sync Rules
Step 5: Configure sync rules
Set the sync behavior and conflict resolution strategy, then start the sync:
Configure sync behavior:
Sync Contact Details: Enable to import email, SMS, and phone numbers
Sync Strategy: Choose conflict resolution strategy:
Preserve Local Changes: Keep existing Harness data when conflicts occur
Overwrite with Source: Use OpsGenie data for all conflicts
Review the sync summary showing selected options
Click Start Sync
Step 6: Monitor sync progress
Track the import status and review the imported entities:
View the sync status dashboard showing:
Import progress by entity type
Successfully imported items
Skipped items with reasons
Failed items with error details
Review imported entities:
Users: Number imported and invitation status
Schedules: Rotation patterns and shift assignments
Escalation Policies: Levels and responder assignments
Teams: User Group mappings
Post-sync steps
After completing the initial sync:
Verify user mapping: Ensure external users are correctly mapped to Harness users by email
Review schedules: Check that rotation patterns and time zones imported correctly
Test escalation policies: Verify escalation rules work as expected
Update service ownership: Assign imported teams to services in the Service Directory
Configure notifications: Set up notification preferences for imported users
Sync conflicts
Common conflicts and how to resolve them:
User not found
External user email does not match a Harness user
Invite the user to Harness or map to an existing user
Duplicate schedule
Schedule with same name already exists
Rename one of the schedules or merge them
Team name collision
User Group with same name exists
Rename the User Group or choose to merge
Timezone mismatch
External tool uses different timezone format
Review and confirm timezone conversions
Ongoing sync
After the initial import:
Re-sync periodically: Pull updates from OpsGenie to keep schedules current
One-way sync: Changes in OpsGenie can be synced to AI SRE
Manual management: After import, manage schedules independently in AI SRE
Selective updates: Re-run sync for specific services when needed
Next steps
Go to Create On-Call Schedules to manage imported schedules.
Go to Define Escalation Policies to configure escalation chains.
Go to Configure Notification Fallback to set up multi-channel notifications.
Last updated
Was this helpful?