Skip to main content

Sentry Issues

Introduction​

We use Sentry tool to look for any unexpected behavior of our products. Whenever an error occurs on any instance of the product (including users' systems), the details about it are sent to Sentry enabling us to investigate it and fix before it affects more users. We have configured Sentry for WebApp and OneBox Chrome Extension.

There are 2 categories of events in Sentry:

  • Errors are the malfunctions that cause the software to work not as expected and they are reported back from the user's side to the Sentry.
  • Transactions are used for measuring the time needed to complete some action and they help with calculating the performance of our products.

Errors automatically become the issues and the transactions may also resolve to issues when a certain (configurable) threshold is exceeded. The issues are something we need to review and act on, to avoid similar problems in the future.

Note: There is a limit though for the number of the events from these categories called a quota, and if exceeded, all the latter events will be dropped. That's why we need to be mindful about it and track only what's important to us.

Review Process​

  1. Sentry issues are automatically assigned to teammates using CODEOWNERS file mapping.
  2. On Mondays, QA Team creates a summary of all the issues with names of the team members and the number of the issues assigned to them.
  3. The summary is posted on #sentry-process Slack channel.
  4. Following the summary message, all mentioned team members need to review their issues and take an action for each of them:
    1. Ignore - Mark it as "Ignore", if it's something not relevant or the severity is estimated to be very low,
    2. Reassign it to someone else and ping that person to take care about the issue,
    3. Fix it right away if it's really simple and mark it as "Resolved",
    4. Plan - Create a bug in GitHub (you can do it straight from the Sentry UI) and wait for it to be triaged,
    5. Escalate critical bugs by creating it in GitHub, notifying the others on Slack and acting on it quickly.
  5. QA Team is responsible for letting people know about the issues, but it's a responsibility of the assigned team members to take care and fix them.