Open lmolkova opened 1 week ago
Yes, this problem keeps coming up. We have a "meta" bug here for it #4261 and I agree we need to rethink the approach like the recommendations you mentioned:
The recommendation:
- use a different channel to report SDK issues (not python logging) and keep it off by default. AND/OR
- throttle self-reporting logs when publishing them to python.logging (e.g. log once and, if throttling, add a message on how to enable internal logging)
If log exporter raises an exception, it fails the process with
RecursionError: maximum recursion depth exceeded
You'd see something like
This issue is originally discovered in a natural case of dependency version conflict and mismatch between exporter and the SDK. While the exporter and/or app is to blame, we should handle it gracefully and avoid killing the app process.
The recommendation:
Related to https://github.com/open-telemetry/opentelemetry-python-contrib/issues/2813
Part of https://github.com/open-telemetry/community/issues/1751