Sentry

The Sentry integration connects your Sentry organization to scaling.cloud in two directions from a single install:

• Send alerts → page on-call. A Sentry issue-alert rule fires, scaling.cloud opens an incident and pages whoever is on-call through your escalation policy.
• Read for investigations. AI investigations read your Sentry issues, releases, and stack traces and surface them as root-cause findings.

You install once. Both directions are authorized by the same connection — there are no per-project tokens or webhook URLs to copy.

​

Send Sentry alerts as incidents

Add “Send a notification via scaling.cloud” as an action on any Sentry issue-alert rule. When the rule fires:

• scaling.cloud opens an incident and routes it through your org’s routing and escalation policy, paging the engineer who is on-call right now.
• The Sentry event level maps to incident severity — fatal → critical, error → high, warning → medium, info/debug → low.
• Alerts are deduplicated by Sentry issue, so a noisy rule raises one incident, not hundreds.
• When the Sentry issue is resolved, the matching incident resolves automatically.
• The incident maps to the component whose name matches the Sentry project slug; if none matches, a component-less incident is opened so the page still happens.

​

Enrich investigations (read)

The same connection is a signal source for AI investigations. Once connected, an investigation can read your Sentry data and surface findings:

• root_cause — derived from a grouped error’s stack trace.
• commit_correlation — from a release’s linked commits, corroborating a GitHub suspect change at commit precision.

This direction is read-only and enriches investigations on existing incidents — it does not open them.

​

Watched projects

After connecting, you choose which Sentry projects investigations may read from, under Watched projects. Only the projects you select are read — connect once, then scope the integration to the projects that matter for your incidents.

​

Connect

Connecting authorizes scaling.cloud against your Sentry organization through Sentry’s integration platform. You need the Admin role in both scaling.cloud and Sentry.

​

Remove the integration

Open Settings → Integrations → Sentry and click Disconnect Sentry. scaling.cloud stops reading from your Sentry organization and stops accepting its alerts immediately.