Metrics - Periodic reader calls otel.Handle with error during shutdown if collectAndExport is running

[patagonia-fan]

If collectAndExport is running in the run loop, and Shutdown is called, the cancel function of the run loop context will be called, and the context error propagated to otel.Handle without a way to distinguish this case from actual problematic errors.

Since data will be reported after cancellation in the Shutdown code, it would be ideal to have a way to disinguish this case to not handle it as an actual error.

Consider WithCancelCause or similar to differentiate this valid case from actual errors.

[flc1125]

Can you describe why it is necessary to distinguish such erroneous scenarios and their causes?

[patagonia-fan]

Since its a valid case (calling shutdown while reporting metrics) I assume that delegating to the error handler is accidental, and meant for actually reporting errors during the usual run loop.

Given this is already in place, in order to not break backward compatibility, maybe flagging the error with the cancel cause could allow to be explicitly ignored by the otel.Handle set by people using the library.

The reasoning is this is reporting and error when its a handled case.

[flc1125]

Is this the effect you expected? https://github.com/open-telemetry/opentelemetry-go/pull/7265/files

[patagonia-fan]

The cause should be an exported error, so its usable from outside with errors.Is but yes that would make sense

[flc1125]

We hope to gather feedback from more people to assess whether this need is personal or shared by the majority.

Or you can provide more information that makes it absolutely necessary.