• 使用を開始する
  • 関連ドキュメント

End of sales and support for Opsgenie

Atlassian will discontinue new sales of Opsgenie on June 4, 2025 and end support for Opsgenie on April 5, 2027. Read the full announcement and learn about next-generation incident response options via Jira Service Management and Compass.

Advanced alert configurations after migration

Advanced alert configurations in Opsgenie include heartbeat monitoring, audit logs, global custom roles, and role-based notifications (previously called central notification templates). These features remain available in Jira Service Management and Compass but have new limits and configuration changes.

Migration summary

Is this feature fully available in all Jira Service Management and Compass plans?

No, some advanced alert configurations are only available in higher-tier plans:

  • Heartbeat monitoring isn't available in Jira Service Management Free and Standard or Compass Free and Standard.

  • Global custom roles and role-based notifications aren't available in Jira Service Management Free and Standard or Compass Free and Standard.

Is this feature auto-synced after data migration?

  • Heartbeats, audit logs, and role-based notifications will be moved automatically.

  • Heartbeats exceeding the 2,000 limit per site will still be moved, but you must remove excess heartbeats in your new product before adding more.

  • The Owner role template in central notification templates (now called Role-based notifications) won’t be migrated as this role no longer exists in Jira Service Management or Compass.

Are there required actions for full workflow parity?

Yes. You’ll need to:

  • Update heartbeat email references in scripts to match new Jira Service Management and Compass domains. Heartbeat names are updated to the new atlassian.net servers and will continue to function as usual. However, if there are scripts you’re using the heartbeat names with the opsgenie.net servers, we recommend updating your scripts.

  • Manually recreate deprecated heartbeats if they were using the older version of Heartbeats (Heratbeats v1).

  • Remove excess heartbeats if their migrated total exceeds the 2000 cap.

  • Reassign role-based notifications previously assigned to the Owner role.

Advanced alert configuration in Jira Service Management

Heartbeat

Currently, heartbeats are only available for your teams. You can access your hearbeat from your team’s operations. To find your updates and review them;

  1. Go to Teams > Operations > Heartbeats to view your migrated heartbeats.

  2. If your site has more than 2000 heartbeats ask your Jira admin to remove excess heartbeats from other teams' operations.

  3. Since heartbeat emails are changed we recommend updating email references in scripts to reflect Jira Service Management domains. Select Copy heartbeat name from the Actions menu to copy the new email for your heartbeat.

  4. If any heartbeats weren’t migrated due to outdated formats, manually create a new heartbeat using Jira Service Management’s API.

Read more about heartbeats in Jira Service Management

Central notification templates

Templates assigned to the Owners in Opsgenie are now disabled, as your Opsgenie owners have been mapped to a different role in Jira Service Management. You can either reassign these templates to an Admin, or remove them if an existing admin role template is already in place.

  1. Go to Operations > General configuration > Role-based notifications.

  2. Locate templates that were previously assigned to the Owners role.

  3. Reassign the template to an Admin role, or remove it if an existing admin role template is already in place.

Read about setting up role-based notifications in Jira Service Management.

監査ログ

Audit logs related to Operations, such as alert logs, notification logs are located seperate from Jira logs. You can find them under Operations > General configuration > Audit logsRead more about audit logs.

Advanced alert configuration in Compass

Heartbeat

In Compass, heartbeats continue to function at the team level and can be accessed through Operations. 

To find and manage your heartbeats:

  1. Go to Operations > Heartbeats.

  2. Remove any excess heartbeats if your total exceeds 2,000.

  3. Select Copy heartbeat name from the Actions menu and update email references in scripts to reflect Compass domains.

  4. If any heartbeats weren’t migrated due to outdated formats, manually create a new heartbeat using Compass’s API.

Read more about heartbeats in Compass.

Central notification templates

Opsgenie’s central notification templates have been renamed to role-based notifications in Compass. Templates assigned to Owners in Opsgenie are now disabled, as the Owner role doesn't exist in Compass. Users must reassign or remove these templates to ensure notifications continue working as expected.

To update role-based notifications:

  1. Go to Operations > General configuration > Role-based notifications.

  2. Locate templates that were previously assigned to the Owners role.

  3. Reassign the template to an Admin role or remove it if an existing admin role template is already in place.

監査ログ

Operations-related audit logs, including alert logs and notification logs, are separate from Compass logs. You can find them under Operations > General configuration > Audit logs. These logs provide a history of changes and notifications related to alerts, on-call schedules, and escalation policies.

さらにヘルプが必要ですか?

アトラシアン コミュニティをご利用ください。