Opsgenie
Atlassian is deprecating the Opsgenie product and encouraging their customers to migrate to Jira Service Management. Read more about moving from Opsgenie to Jira Service Management on Atlassian's web site.
Cortex is actively working on developing an integration with Jira Service Management.
Opsgenie is an alert and on-call management platform from Atlassian.
Integrating Opsgenie with Cortex allows you to:
Pull in on-call rotation data and escalation policies
The on-call user or team will appear in the Current On-call block on an entity's details page.
You can also view on-call information on an entity page in its side panel under Integrations > On-call.
View alerts from Opsgenie in an entity's event timeline
Create Scorecards that track progress and drive alignment on projects involving your on-call schedules and alerts
How to configure Opsgenie with Cortex
Prerequisite
Before getting started, create an Opsgenie API key with the following permissions:
Read
Configuration Access
Configure the integration in Cortex
In Cortex, navigate to the Opsgenie settings page:
In Cortex, click your avatar in the lower left corner, then click Settings.
Under "Integrations", click Opsgenie.
Configure the Opsgenie integration form:
Subdomain: Enter the subdomain assigned to your Opsgenie instance.
API key: Enter your Opsgenie API key.
Use European service region: Optionally, toggle this setting on to enable the EU region of Opsgenie.
Click Save.
How to connect Cortex entities to Opsgenie
Discovery
By default, Cortex will use the entity tag (e.g. my-entity
) as the "best guess" value for the backend
and service
tags on your alerts. For example, if your alert in Opsgenie has the tag backend:my-entity
, the alert will be automatically associated with the entity in Cortex with a unique identifier of my-entity
.
If your Opsgenie tags don’t cleanly match the Cortex entity tag, or you use different identifying tags, you can override this in the Cortex entity descriptor.
Entity descriptor
x-cortex-alerts:
- type: opsgenie
tag: different-tag
value: my-entity-override-tag
type
Type of alert (in this case, opsgenie
)
✓
tag
Type of tag in Opsgenie (e.g. backend
)
✓
value
Alert in Opsgenie (e.g. my-entity-override-tag
)
✓
For example, for the tag different-tag:my-entity-override-tag
, the entity descriptor would have different-tag
in the tag field and my-entity-override-tag
in the value field.
You can add a list of tags to use for lookup. Cortex will use an OR
operator when querying Opsgenie (e.g. backend:my-entity OR service:another-value
).
The value
field also supports wildcards (e.g. value: my-entity*
).
Adding a schedule
You can define the following block in an entity descriptor to add an Opsgenie schedule. Cortex supports adding a schedule by ID or UUID. You can add one schedule per entity.
The UUID for the schedule can be found in URL when viewing schedule details by clicking on the schedule name under who is on-call.
x-cortex-oncall:
opsgenie:
type: SCHEDULE
id: Cortex-Engineering
type
Opsgenie component being added (in this case, SCHEDULE
)
✓
id
Schedule ID or UUID
✓
Ownership
x-cortex-owners:
- type: group
name: My Opsgenie Team
provider: OPSGENIE
description: This is a description for this owner
type
Ownership type (in this case, group
)
✓
name
Name of the team defined in Opsgenie (**case-sensitive)
✓
provider
Identity provider (in this case, OPSGENIE
)
✓
description
Description for the team, to be displayed in Cortex
Identity mappings
Cortex maps email addresses in your Opsgenie instance to email addresses that belong to team members in Cortex. When identity mapping is set up, users will be able to see their personal on-call status from the developer homepage.
Using the Opsgenie integration
After setting up the integration, Opsgenie information will appear in several places across Cortex.
Viewing on-call information for an entity
On an entity details page, current on-call information from Opsgenie will display in the On-call block.
Escalation policy, the level associated with the policy, and other on-call information will also appear in the entity's sidebar in the "On-call & incidents" page. Owners assigned to each level will also be hyperlinked to the user or team page in Opsgenie.

Viewing recent Opsgenie events
Click Events in an entity's sidebar to view recent events pulled in from Opsgenie.
Viewing on-call information on the dev homepage
The Opsgenie integration enables Cortex to pull on-call information into the on-call block on the Dev homepage. On-call data from Opsgenie is refreshed every 1 minute.
Scorecards and CQL
With the Opsgenie integration, you can create Scorecard rules and write CQL queries based on Opsgenie on-call schedules and alerts.
See more examples in the CQL Explorer in Cortex.
Ownership CQL
Background sync
Cortex performs the following background jobs:
Ownership: A sync for Opsgenie teams every day at 9 a.m. UTC.
Identity mapping: A sync for Opsgenie identities every day at 10 a.m. UTC.
Still need help?
The following options are available to get assistance from the Cortex Customer Engineering team:
Email: [email protected], or open a support ticket in the in app Resource Center
Chat: Available in the Resource Center
Slack: Users with a connected Slack channel will have a workflow added to their account. From here, you can either @CortexTechnicalSupport or add a
:ticket:
reaction to a question in Slack, and the team will respond directly.
Don’t have a Slack channel? Talk with your Customer Success Manager.
Last updated
Was this helpful?