Skip to content

Sentry

Valentyne Stigloher requested to merge 380-sentry into main

I was experimenting with sentry, then found that there is already a Nuxt module which already configures some hooks correctly. Only for express another call is needed. For the server scripts another init is required (they have a slimmer configuration, e.g. release and environment is not set there).

GitLab also provides a small Sentry backend via Error tracking, but it is very limited (no notifications, no source mapping, no performance, no user agent information, just time, count, stack trace and maybe a source preview). So I setup a Sentry user account, which also has more granular options. The GitLab page just displays things from Sentry.

Express might not be configured correctly, as the route name is logged, not the actual url (which we use in console.error)

Currently, no sensitive information like localStorage or cookies get transferred. But IP and sometimes email address is stored.

When deploying to test, I noticed that the deployment time went up to 150s (maybe because of the source map uploading).

Closes #380 (closed)

TODO

  • Check privacy notice

Future Work

  • Clear Sentry project so that production begins with a clean one
  • Setup Discord bot
  • Check whether we need to erase user information – for now, scrub all user information because Sentry somehow detects it even without setting them explicitly via Sentry.setUser
  • Enable query performance monitoring
Edited by Valentyne Stigloher

Merge request reports