Decide on a clear exception handling strategy for extensibility components in SDK

[utpilla]

We need to decide on whether we should let faulty third party extensibility components crash the SDK.

There are several extensibility components which can throw an exception anytime after initialization, and can cause app to fail in the middle of execution.

• Sampler
• Processor
• Exporter (SimpleExportProcessor catches exceptions thrown by an exporter)
• Instrumentation's Enrich
• Instrumentations's Filter - (We do catch user exception here)
• ExemplarFilter
• ExemplarReservoir

[martinjt]

I believe that we're solved this in that all those examples won't cause a failure.

I'd suggest, if there is more to this, that a ticket as a bug is created and if there is discussion to be had, we reopen this and discuss at the next SIG so we can get concrete actions.

[utpilla]

I believe that we're solved this in that all those examples won't cause a failure.

A custom extension component can throw an exception. We need to formulate our stance on how we want to treat them. It would be good to discuss this in the SIG meeting.

[github-actions]

This issue was marked stale due to lack of activity and will be closed in 7 days. Commenting will instruct the bot to automatically remove the label. This bot runs once per day.