Zenning for Sentry
Zenning can flag new error spikes, summarise an issue and explain a stack trace.
Spot errors and crash spikes
What Zenning can do
- Spot a bad release
- Digest overnight errors
- Track crash-free rates
Try asking
Each morning triage new Sentry issues, group duplicates in Linear, and auto-ignore noise via Mezmo filters.
What it does in Sentry
- When a critical alert fires in SentryCheck related logs in New Relic, create a Linear ticket and notify the security Slack channel with suggested remediation
- When Sentry error volume spikesFind the release in GitHub, assign in Linear, and deploy a Heroku hotfix
- When Sentry shows a mobile crash spikeCheck the Bitrise build, file in Shortcut, and update App Store Connect notes
Actions
Every action Zenning can take in Sentry.
36 actions
- Bulk update issues
- Create alert rule
- Create monitor
- Create project
- Create release
- Create team
- Delete alert rule
- Delete issue
- Delete monitor
- Delete project
- Delete release
- Delete team
- Get alert rule
- Get event
- Get issue
- Get monitor
- Get organization
- Get project
- Get release
- Get team
- List alert rules
- List environments
- List issue events
- List issues
- List monitors
- List organization members
- List organization projects
- List project events
- List projects
- List releases
- List teams
- Update issue
- Update monitor
- Update project
- Update release
- Update team
Connect Sentry in a few minutes
Connect it in a few clicks and choose who in your team can use it. Change that any time.