Menu
Documentationbreadcrumb arrow Grafana Cloudbreadcrumb arrow Alerts and IRMbreadcrumb arrow IRMbreadcrumb arrow IRM Slack integrationbreadcrumb arrow Migrate from existing Slack integrations
Grafana Cloud

Migrate to the Grafana IRM Slack app

Warning

Do not uninstall your current Slack apps before migrating to the Grafana IRM Slack app. Uninstalling could result in configuration loss.

The Grafana IRM Slack integration combines the features of the OnCall and Incident Slack apps into a single, unified Grafana IRM Slack app. This simplifies your workflow and makes for a more cohesive and streamlined experience, eliminating the need for separate integrations.

If you have the OnCall or Incident Slack apps installed, follow the steps in this guide to migrate your existing Slack configurations without losing any settings.

Key changes

Shared integration: This integration is IRM-wide, meaning that when it is installed in OnCall, it is automatically be available for use in Incident, and vice versa. The same applies to the uninstall process—uninstalling the IRM app from OnCall also removes it from Incident.

Slash Commands: Commands are changing from /escalate and /incident to /grafana. Update your internal workflows accordingly.

  • Example commands:
    • /grafana: List all available commands
    • /grafana incident new: Create a new incident
    • /grafana escalate: Page a user or team

Migrate from the OnCall and Incident Slack apps

To preserve your existing Slack configuration, do not uninstall your current Slack apps before migrating to the Grafana IRM Slack app.

There are two ways to migrate to the new integration, depending on your current installation.

Migrate from the OnCall Slack app

To migrate from the OnCall Slack app to the Grafana IRM Slack app, you need to approve additional permissions for incident management functionality. Your existing Slack-related OnCall configuration, including channels, users, and schedules, are preserved in the migration process.

Follow these steps to migrate from Grafana OnCall:

  1. In Grafana OnCall, navigate to the Settings tab, then the ChatOps tab.
  2. Click Slack and click the Migrate button to upgrade.
  3. After being redirected to the Slack connection page, verify your Slack workspace, review the permissions, and specify a default channel.
  4. Follow the Slack prompts to authorize the new permissions.
  5. Verify that all existing configurations have been transferred successfully.

Migrating requires the following additional permissions:

  • Bookmarks:read
  • Bookmarks:write
  • Channels:manage
  • Groups:write
  • Pins:read
  • Reactions:read
  • Incoming-webhook

Refer to the Permissions section for detailed information.

Migrate from the Incident Slack app

The Grafana Incident Slack integration is now considered legacy, and you need to migrate to the new Grafana IRM Slack integration by installing the updated Grafana IRM Slack app.

During this migration, your existing Incident Slack settings, including incident announcements and automatic channel creation, are all preserved.

You can still manage incidents that started before the migration using the legacy app and the /incident command.

Follow these steps to migrate from Grafana Incident:

  1. Navigate to the Integrations tab then click the Slack IRM tile.
  2. Click Install Integration to set up the Grafana IRM Slack app.
  3. After being redirected to the Slack connection page, verify your Slack workspace, review the permissions, and specify a default channel.
  4. Follow the Slack prompts to authorize the new permissions.
  5. Verify that all existing configurations have been transferred successfully.

Refer to the Permissions section for more information.

Known issues

  • Uninstalling and reinstalling instead of migrating may result in configuration loss.
  • The hero image might not update immediately after migration.
  • Changes to channel titles from the UI or web might not update automatically.

For more detailed instructions and information on available commands, refer to the IRM Slack integration documentation.