-
-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: add Sentry support for reporting errors #244
Comments
I’ve read up a bit on Sentry – and it wasn’t quite what I expected. So, as a bit of clarification. Do I understand correctly that essentially Routinator would submit panics as events into Sentry and offer it as a logging backend? |
Correct @partim - with the distinction that I wouldn't call it logging but rather monitoring; and, yes, monitoring errors / panics as events that provide a detailed trace from where the error started which helps identifying the root cause easily. |
Sounds very interesting, indeed! I’ll do a bit more research into the best way to include support. |
I ❤️ Sentry and I'm using it in almost every project / app that runs in background that can silently fail, which many times turned out to be serious issues - that would be unnoticed otherwise.
The integration is relatively simple (see https://docs.sentry.io/platforms/rust/). I'd be happy to add it myself, however I'm yet to learn Rust. Anyway, I'm opening this for now mainly for hearing your thoughts.
Usually the Sentry DSN is read from an environment variable (e.g.,
SENTRY_DSN
) and / or CLI arg (e.g.,--sentry-dsn
).The text was updated successfully, but these errors were encountered: