Discourse Sentry

AI-generated summary

  • Discourse Sentry integrates error tracking from Sentry.io into Discourse’s backend and frontend (eatcodetravel)
  • It allows configuring email/Slack notifications for errors and tracking error resolution (Artem_Vasiliev)
  • Sentry offers remote error tracking, alerts, assigning issues, and tracking resolution, which some find useful for large projects (neounix)
  • It provides an alternative to Discourse’s built-in Logster error aggregation (codinghorror)
  • Some users already use Sentry for other services, so integrating it with Discourse is convenient (eatcodetravel)
  • A video covers Sentry’s core features like setup and integration with Rails (neounix)
  • It may allow setting different DSNs for frontend and backend (Maxpain)

Repo: https://github.com/debtcollective/discourse-sentry

This plugin integrates https://sentry.io error tracking in the backend and the frontend. We are using at http://community.debtcollective.org

Admin Settings

  • discourse sentry dsn: sentry.io dsn for your project.

image

7 Likes

What does this offer over the existing, built in Logster error aggregation in Discourse at /logs?

I’m not sure but we use Sentry for the rest of our services, so is natural for us to use it in our community too.

5 Likes

What does this offer over the existing, built in Logster error aggregation in Discourse at /logs ?

E.g. configurable email/slack notifications in case of errors.

4 Likes

I use Sentry for a fairly large Rails development project and it’s nice for tracking issues, assigning people to tasks, tracking resolution, getting alerts and integrating (in our case) with a private GitHub repo.

Because Sentry works well for this current Rails development project, I think soon we will try out this Discourse Sentry plugin and see if there is any benefits but so far it’s nice to track errors remotely and get alerts, manage assignment and tracking issue resolution.

1 Like

This Drifting Ruby YT video is useful in describing the core features and setup for Sentry and Rails:

1 Like

Is it possible to set different DSNs for frontend and backend?