Features

Working with Sentry

Sign in, understand errors, and map releases – day-to-day work with error tracking.

On this page

Opening Sentry and signing in

  1. Open the project overview in the platform and click the Sentry tile – it leads directly to your Sentry project on sentry.doppelt-digital.com.
  2. Sign in with the same account you use for the platform and GitLab.

Reading errors

Each entry (issue) in Sentry groups similar errors and shows you:

  • Stack trace – where in the code the error occurs.
  • Frequency and affected users – how urgent the problem is.
  • Release version – from which release the error appears. The versions match the automatically assigned versions of your pipeline (see Operations).
  • Context – device, operating system, browser, and the last actions before the error.

Typical flow after a release

  1. After the prod release, briefly open the Sentry project.
  2. Check new issues since the release – Sentry groups them by release version.
  3. Fix the error, commit, merge – the next release resolves the issue.
  4. For critical errors: roll out the previous version again, see Operations.
Tip
Apps and backend report into the same Sentry project of your platform project – no jumping between multiple places.

See also