Is your feature related to a problem? Please describe.
Currently, a span is created for every retry (just the default process span), but there's no dedicated span to move the message to the error queue, which could be useful to make this explicit. Now a user would have to understand their recoverability settings, and the total amount of retries to guess whether the message was moved to the error queue.
Describe the feature.
Is your feature related to a problem? Please describe.
Currently, a span is created for every retry (just the default process span), but there's no dedicated span to move the message to the error queue, which could be useful to make this explicit. Now a user would have to understand their recoverability settings, and the total amount of retries to guess whether the message was moved to the error queue.
Describe the requested feature
Describe alternatives you've considered
Additional Context
No response