Page MenuHomeSoftware Heritage

Clean sentry reports
Closed, MigratedEdits Locked


We currently have a lot of open Sentry issues,
but this is very raw data that isn't very usable or visible.

We should either:

  • explicitly ignore them / stop raising them
  • assign them a task in the forge (manually! otherwise it would just be more noise)
  • fix them and/or close them


  • it is a process
  • better managing the elements that are in Sentry

Event Timeline

douardda triaged this task as Normal priority.Feb 18 2022, 12:14 PM
douardda created this task.

Sentry Sprint #1 report :


  • April 13th
    • 10:00 - 12:00
      • Kickoff
      • Definition of the sprint goals
      • Identification of the scoped sentry issues
      • Team organization
    • 14:00 - 17:00
      • First iteration
  • April 14th
    • 10:00 - 10:30
      • Synchronization
    • 10:30 - 12:00
      • Second iteration...
    • 14:00 - 16:30
      • ...second iteration
    • 16:30 - 17:00
      • Retrospective
  1. Sprint Goals
    • We currently have a lot of open Sentry issues, but this is very raw data that isn’t very usable or visible. They should be cleaned up so that under normal conditions, the number of reported issues stays “minimal”.
    • Clean-up options:
      • Refine issues data
      • Eliminate redundant/useless issues
      • Identify sources of issues >> potential easy hacks ?


turn off sentry error reporting logging integrationdouardda / bchauvetD7570
Use explicit sentry exception capture in RPC back-endanlambert / olasdD7566 D7567
RetryError Handlinganlambert / olasdD7568
UniqueViolation and HashCollision server-side onlyvsellier / vlorentz
Vaultardumont/jayeshD7566 D7564
Define statsd metrics for sentry-removed issuesanlambert/olasdD7569
Add missing sentry capturesteamT3957


vsellier - vlorentz
olasd - anlambert
ardumont - jayesh
douardda - bchauvet

Tasks details

Filtered list

  • Review the places in the code where we log exceptions to check there's an excplicit sentry capture
  • Define statsd metrics for sentry-removed issues
    • D7569 to add an error_type tag to already existing (backend function) error metrics
  • UniqueViolation and HashCollision: not to be reported in sentry if the error can be encoded and sent to the client >> create a task for it

seems we still have a lot of NotFound error from the swh-loader-git: