You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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: