Aaron Abbott

The way the SDK is implemented today, the error handling should happen in processor implementations. For example https://github.com/open-telemetry/opentelemetry-python/blob/b06cf803605dd323ad134a9a434a204bf7fb150f/opentelemetry-sdk/src/opentelemetry/sdk/_logs/_internal/export/__init__.py#L120-L123 For the batch processors, everything is already happening in a background thread...

Thanks! I think we can improve the docs for implementors.

We did also deprecate the Event API but this seems like a small thing we can easily do a fix. Sorry for the warnings.

@emdneto will take a look

Given that the stack trace has `azure/core/tracing/decorator.py`, I'm guessing this is an Azure specific issue. @lzchen @jeremydvoss

Going by the stack trace, it looks like an error in the console exporter. https://github.com/open-telemetry/opentelemetry-python/blob/23aad5e4adc143e8ca0cbca4b05802822b6d554f/opentelemetry-sdk/src/opentelemetry/sdk/_logs/_internal/export/__init__.py#L98 I don't think this is related to #4688. It looks like you're using Windows, I'm...

> The argument against is valid for every other instrumentation 😅 True just trying to present some counterargument. Existing logging instrumentation confusion aside, are you in favor or against moving...

Thanks for the feedback Tammy. I was thinking we can just copy the handler into a new package and leave the old one around for a while with deprecation notice....

This problem seems to be only happening in a recent python change. I only see the issue on non-EOL versions and the most recent patch release. For example 3.13.7 but...

I'm not sure what's going on with the python versions, but the issue is that 1. Both packages provide opentelemetry proto code. See xds-protos source https://github.com/grpc/grpc/blob/46b1795eacc99065c46e3fb60fad808c19f71a87/tools/distrib/python/xds_protos/opentelemetry/proto/trace/v1/trace_pb2.py#L29 2. The xds-protos version...