Monitoring
Monitor Sentry with MrCron
MrCron mirrors Sentry open error count, critical issues, and resolved-in-24h volume every 5 minutes so you can see error health on the same dashboard as your deploys and payments.
How MrCron monitors Sentry
- Open error count per project on the linked Sentry organization.
- Critical issue count with red badge on the project card.
- Errors resolved in the last 24 hours per project.
- OAuth token refresh handled automatically so integrations stay live.
- Alert rules that fire on new critical errors via any notification channel.
What you will see
Open errors, critical issues, resolved-in-24h on every project card.
Auth flow: OAuth. Credentials are stored encrypted at rest with AES-256-GCM and never returned to your browser.
Start monitoring Sentry
Sign in, create a project, and connect Sentry in under a minute. First check ships in the free tier.
Frequently asked questions
- How does MrCron connect to Sentry?
- OAuth. You grant project:read scope, pick which Sentry project to attach, and MrCron refreshes the token automatically on every sync.
- Does MrCron read error payloads?
- No. MrCron reads error counts and issue metadata only (title, level, status). Deep-link back to Sentry for stack traces and breadcrumbs.
- Does MrCron support self-hosted Sentry?
- Yes. When you connect the integration, point it at your self-hosted Sentry host URL and the same OAuth flow works.
- Can I alert on a new critical error?
- Yes. Create an alert rule on the sentry_critical_issues metric with a threshold above your baseline and route it to any notification channel.