-
Notifications
You must be signed in to change notification settings - Fork 417
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
Third Party Python Modules Warnings are Logged as Errors in Datadog #10963
Comments
I've managed to make all app only related log to have proper levels in DD with using custom log config, custom formatter class and log config in
class
But what I cannot make to work is to get proper logs from Which looks to me as actual warning. My guess is because
Anyone knows if there is a way to make those as warnings? |
Hey datadog team,
I used datadog to monitor my python application, the warnings in the third party python modules will appear as errors in the datadog log explorer. even the DD trace module warnings or debugging could be shown as errors in Datadog UI. For example, I got a lot of error logs of
Error getting lock acquire/release call location and variable name: 'Model' object has no attribute '_has_params'
But I believe these are warnings in the dd-trace-py code. Also in my error log explorer, I could see error logs like
sent 958B in 1s to <datadog trace host>
, which is debugging info.I know I could resolve this by set the logger level to ERROR, but would like to understand why DD cannot grab the right logger type.
The text was updated successfully, but these errors were encountered: