Sentry integration. Investigate Sentry errors from the stack trace to the line that broke.
Praxen Inc. picks up Sentry alerts with the exception attached, searches errors and events to find the cause, and fixes the code behind the stack trace.
Get started for freeWhat Praxen Inc. does with Sentry.
Errors arrive with the exception attached
Sentry issues land in Praxen Inc. with the actual exception before triage starts: type, message, top stack frames, and tags.
Alerts triaged on arrival
Every Sentry alert lands as an issue and an agent triages it the moment it fires: real signal or noise, and what changed right before.
Error data mid-investigation
Agents search issues and events while they work an issue, correlating error patterns with deploys and the resources in the blast radius.
From stack trace to fix
When the investigation reaches a line of code, the fix arrives as a pull request on the repo behind the service, with the evidence trail attached.
How to set up Sentry
- Select Sentry in Praxen Inc. to start the OAuth integration installation.
- Choose the Sentry organization, review requested access and accept installation.
- Return to Praxen Inc. and check alert delivery. Connecting adds a Send a notification via Praxen Inc. action to issue alert rules.
Permissions and access
Sentry uses an organization OAuth integration rather than a manually entered token. The checked connection guide does not enumerate the provider-side scope manifest; review Sentry’s installation consent screen for the exact grants. Provisioning the Praxen Inc. notification action changes issue alert rules.
Discovery, refresh and the connected view
Agents read issues, search error events, inspect recent event details and investigate alert context. Recurring reconciliation adds the Praxen Inc. action to issue alert rules. For Terraform-managed rules, include the installation UUID in the notification action configuration to avoid drift; the Sentry installations API lists that UUID.
Disconnect and revoke access
Disconnect Sentry in Praxen Inc. or remove the installation in Sentry Settings → Integrations. Disconnecting removes its action from alert rules, so remove it from Terraform configuration at the same time.
Sentry tools.
The calls Praxen Inc. can make to Sentry when it looks into an issue.
Sentry -
sentryApiCall any Sentry REST endpoint that lacks a dedicated tool -
sentryProjectsRead Sentry projects (list, get, stats) -
sentryIssuesRead or update Sentry issues, events, tags, and hashes -
sentryAlertRulesRead or create Sentry alerts (issue alert rules) -
sentryMetricAlertsRead or create Sentry metric monitors (metric alert rules) -
sentryIncidentsRead Sentry metric alert firings -
sentryReplaysRead Sentry session replays -
sentryDashboardsRead, create, or edit Sentry dashboards -
sentryQueryDiscoverRun a Discover query in Sentry -
sentryQueryTimeseriesRun a Sentry events timeseries query
Sentry setup and troubleshooting
Common questions.
How do I connect Sentry to Praxen Inc.?
Select Sentry in Praxen Inc. to start the OAuth integration installation. Choose the Sentry organization, review requested access and accept installation. Return to Praxen Inc. and check alert delivery. Connecting adds a Send a notification via Praxen Inc. action to issue alert rules.
What can Praxen Inc. read from Sentry?
Agents read issues, search error events, inspect recent event details and investigate alert context. Recurring reconciliation adds the Praxen Inc. action to issue alert rules. For Terraform-managed rules, include the installation UUID in the notification action configuration to avoid drift; the Sentry installations API lists that UUID.