-
Notifications
You must be signed in to change notification settings - Fork 711
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
Sentry integration #509
Comments
Hi @fratambot, thanks for sharing a this code snippet! I'm not familiar with Sentry so it's hard for me to produce appropriate documentation. Your solution looks somehow similar to this one shared in another ticket: getsentry/sentry-python#653 (comment) It seems combining |
Hello @Delgan Would it be useful for the Loguru docs to reference the sentry integration in the "Code snippets and recipes"? |
Hi @hillairet. I noticed that Sentry has incorporated support for Loguru, although I hadn't delved into the details yet. The implementation appears very clean. Thanks a lot to @PerchunPak for the hard work! Following your suggestion, I'm closing this ticket since an official solution is now available. In my opinion, the Sentry documentation effectively outlines the integration process between Loguru and Sentry. It doesn't seem necessary to duplication this information in the Loguru documentation. After all, it's a Sentry feature built upon on top of Loguru, rather than the other way around. I assume individuals searching for "Sentry integration with Loguru" on their preferred search engine will easily figure out the relevant documentation. |
I recently started to use loguru and it's amazing !
But sentry too is amazing !
It would be nice to have some integration, at least at the documentation level.
After crawling the web for hours I ended up with this setup which seems to work:
In my main app (FastApi), where I initialize sentry, I have:
In my logger.py I have:
I hope some clear documentation on loguru/sentry integration might come out from this draft in order to help future users of both !
The text was updated successfully, but these errors were encountered: