Skip to main content

R6. Error tracking

What this page helps you do​

Set up a simple way to collect and review app errors.

Why it matters​

Logs are useful, but error tracking helps surface the failures that matter most.

You should already have​

  • a deployed app

Skip this page if​

  • you are not online yet

What to do​

  • pick one error tracking tool or system
  • make sure key failures are captured
  • avoid sending sensitive values

Start with one tool that shows recent production errors clearly.

Common mistakes​

  • capturing nothing
  • capturing too much sensitive data
  • not testing whether the tool actually receives events

Next step​

Go to R7. Logs.

Advanced notes​

TODO for contributors: add a plain-English guide to separating “expected user mistakes” from real production errors.