Opsgenie

Overview

Opsgenie, developed by Atlassian, is an incident and alert management platform for operations teams. When you configure Opsgenie as a notification channel in Turbo360, alerts from Turbo360 are automatically forwarded to Opsgenie as incidents or alerts, ensuring critical issues are routed to the right people and acted on promptly.

Business value

Integrating Opsgenie with Turbo360 connects your monitoring alerts to on-call schedules and escalation policies in Opsgenie. This reduces mean time to acknowledge (MTTA) and ensures the right engineer is notified based on your Opsgenie routing rules.

Prerequisites

• An active Opsgenie account.
• An API access key or API integration key generated from your Opsgenie account. See the following guides for instructions:
  • Add an API Access Key
  • Add an API Integration key

Required permissions

You must have sufficient permissions in Opsgenie to create or manage API keys and integrations for the target team or account.

Dependencies

• Turbo360 must have outbound connectivity to the Opsgenie API endpoint for your selected service region.
• The destination type (alerts or incidents) must be supported by the type of integration key you use.

How it works

Turbo360 uses an Opsgenie integration key to authenticate and send alert payloads to the Opsgenie API. When an alert condition is met, Turbo360 posts a notification to Opsgenie, which creates an alert or incident depending on your integration key type and destination configuration. You can validate the connection during setup to confirm credentials before saving.

Steps

To configure the Opsgenie notification channel, navigate to the notification channel configuration in Turbo360.

1. In Turbo360, navigate to the notification channel configuration and select Opsgenie.
2. Enter a Friendly name to identify this channel in the Turbo360 application.
3. Enter the API access key or API integration key from your Opsgenie account in the Integration key field.
4. Select the service region that matches the region in which your Opsgenie account was created.
5. Select the destination based on the type of key you provided. The destination determines whether Turbo360 notifications are transmitted as alerts or incidents in Opsgenie.
6. Click Validate. Turbo360 sends a sample notification to verify that the credentials are valid.
7. After successful validation, click Save to complete the setup.

Configuration

Permission behavior

With access: Turbo360 can authenticate to Opsgenie and forward alerts or incidents to the configured destination. Test notifications can be sent using the Validate action.

Without access: If the integration key is invalid or lacks sufficient permissions, validation will fail and Turbo360 will not be able to send notifications to Opsgenie until a valid key is provided.

Example scenario

Your team runs on-call rotations managed in Opsgenie. You configure an Opsgenie notification channel in Turbo360 using an API integration key with Alerts as the destination. When a Cost Analyzer anomaly detection rule fires, Turbo360 sends an alert to Opsgenie, which routes it to the on-call engineer based on your existing Opsgenie escalation policies.

Limitations

• API integration keys created via API management only support Incidents as the destination; they cannot send to Alerts.
• Only one Opsgenie destination (alerts or incidents) can be configured per channel. Create separate channels if you need to route to both destinations.
• Turbo360 does not automatically resolve or close Opsgenie alerts when the underlying condition clears.

Troubleshooting

1. Validation fails after entering the integration key
   Cause: The integration key is incorrect, has been revoked, or does not have the required permissions.
   Fix: Verify the key in your Opsgenie account under Integrations or API management. Regenerate the key if it has been revoked, and confirm the key type matches your selected destination.

2. Alerts are not appearing in Opsgenie after successful validation
   Cause: The notification channel is not linked to an alert rule or escalation policy in Turbo360.
   Fix: Verify that the relevant alert rule or escalation policy in Turbo360 references this Opsgenie channel.

3. Destination mismatch error during setup
   Cause: An API management key was selected with Alerts as the destination, which is not supported.
   Fix: Change the destination to Incidents, or switch to an API integration key created via Integrations to enable alert routing.

4. Notifications are sent but appear in the wrong Opsgenie team or queue
   Cause: The integration key is associated with the wrong team or routing configuration in Opsgenie.
   Fix: Review the integration key settings in Opsgenie and confirm the routing rules direct alerts to the intended team.

5. Connection to Opsgenie API times out
   Cause: The selected service region does not match the region of your Opsgenie account, or network rules are blocking outbound requests.
   Fix: Confirm your Opsgenie account region and select the correct region in the channel configuration. Contact your network administrator if outbound HTTPS traffic to Opsgenie is blocked.

FAQs

1. What is the difference between an API access key and an API integration key?
   An API access key is generated from API management in Opsgenie and can only route to Incidents. An API integration key is created under Integrations and supports routing to both Alerts and Incidents.

2. Can I configure multiple Opsgenie channels in Turbo360?
   Yes. You can create multiple Opsgenie notification channels, each with a different integration key or destination, and assign them to different alert rules.

Related articles

• Add an API Access Key
• Add an API Integration key