Exception handling for exporter connection errors / exceptions in general

Is your feature request related to a problem?

sometimes my endpoint can be offline, so the problem is that error and exceptions are not handled and are jumping to console and i cannot choose how to handle them (for example, the OTLPSpanExporter is running as a thread and i cannot wrap it in a regular try except. same applys to logs and metrics exporters

Describe the solution you'd like

i would like a callback that handles connection errors or any other type of exceptions that may occur in the open telemetry package. maybe even a way to run the exporter not as a thread, so i can manage the exceptions myself with a generic try except

Describe alternatives you've considered

No response

Additional Context

No response

Would you like to implement a fix?

No

Start with the OTLPSpanExporter entry point and compare how the logs and metrics exporters run in threads and surface exceptions. Determine the intended callback or non-threaded behavior, then define the API and tests needed to demonstrate that connection and other exporter errors can be handled by callers.