-
Notifications
You must be signed in to change notification settings - Fork 478
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 is not logging ERROR logs by default #1191
Comments
No I don't think we want to enable logs by default, having it as a config for debugging is fine. |
Then is there a way to set logging level from config? I'd like to enable only ERROR logs, not the DEBUG ones? |
It's not exposed as config but you can just import the logger and do whatever you want with it.
|
Thank you! I will use that approach. |
Hi!
I have realised lately that not all of the events from my service were reaching Sentry.
I noticed that the event didn't reach the Sentry server when I was testing some case for which I was expecting to see the alarm. The alarm was not triggered and the event was not in Sentry even when I was able to see the service error log.
I started to dig depper by enabling DEBUG logs.
It turned out that rarely, when Sentry was trying to send an event, it was failiing with "Connection reset by peer" error.
This was most like caused by following issue (just in case if someone bumped into the same problem):
Issue: urllib3/urllib3#944 (comment)
Workaround: psf/requests#4937 (comment)
The problem I see here is that I have been using Sentry for 3 years not realising that some events were not passed to the Sentry server.
Do you think it would make sense to actually enable Sentry ERROR logs by default so we are aware if the integration is not working as expected?
The text was updated successfully, but these errors were encountered: