content-data-api: How to proceed with Sentry Errors
We aim to have an empty list of Errors in Sentry at all times, so with each occurrence in Sentry, we should take action to prevent it from showing again.
The main idea is to have only actionable errors in Sentry because otherwise, they are just noise that could hide important information; you can read more about errors and how to classify them in GOV.UK developers.
If you are a new developer to the team
- Subscribe to the Sentry team: #govuk-data-informed-team, which will enable notifications for Content Data Admin and Content Data API.
If you find an Error in Sentry (Production)
- Create a Trello card in the Team board (Backlog).
- Add the label
sentryto the Trello card
- Add a link to the Sentry Error
- Include any additional information that you find relevant.
- Share the link with the Team Lead / Senior Dev / Product Owner.
If you are resolving a Sentry Error
- Classify the error, and identify action to take.
- Fix the problem and write a detailed description of the issue/solution in the Trello card.
- Share with the team in the weekly Dev session.
- Mark the error as resolved.