Engineering · Some setup
Turn app errors into issues the team will fix
Errors seen only in a monitoring tool are easy to ignore. Creating an issue from the error puts it into the normal planning flow, with the stack trace attached.
Software used
What happens
When
Sentry records a new error, or one starts happening more often.
Then
- A Linear issue is created and linked to the Sentry error.
- When the issue is resolved, both tools show it.
How the tools connect
With a built-in integration. Sentry lists Linear as an integration on its website.
Set it up
Connect Linear from Sentry's integrations.
Start by creating issues by hand from errors that matter. Add alert rules that create issues automatically once you trust the noise level.
Send new issues to a triage view rather than straight into a sprint.
Menus change, so these steps say what to do rather than where to click. Each company's help pages have the current screens.
Watch out for
- Automatic issues for every error will flood your backlog. Set thresholds first.
Track these tools in My stack
Add the software you pay for and see which automations you can set up with it.
Ideas for my stackRelated automations
Engineering · Easy · Built-in integration
Move issues along when code is merged
Updating issue status by hand after every pull request is easy to forget, so boards drift from reality. Linking them keeps status accurate.
Engineering · Easy · Built-in integration
Tell the team the moment your site goes down
Finding out about downtime from customers is the worst way. An alert in the channel the team already watches gets someone looking within minutes.
Engineering · Easy · Built-in integration
Follow code changes in a team channel
Pull requests waiting for review slow everyone down. Posting them where the team talks gets reviews done sooner and keeps others aware of what's shipping.