Deletion Message for SQS Emitted as a Seperate Trace

[harrryr]

Describe the bug

We have a Spring Boot microservice that uses AWS Java SDK 3.0.5 to trigger a message pull from SQS, process the message, then do an external API call. Based on the response of the external API call, the following action is taken:

• Successful - the Spring Cloud library handles the deletion of the message
• Unsuccessful - message is left in the queue (not deleted) and after 3 unsuccessful processing attempts, the message is routed by SQS to a DLQ

We expect one trace to be generated containing all actions taken, but instead we get 2 separate traces.
We believe that this is an issue related to instrumentation with Spring-Cloud-AWS lib.

Steps to reproduce

Pending, will update link if available

Expected behavior

We expect one trace to be generated with the following three actions:

1. Pull from SQS
2. Call External API
3. Delete message from SQS

Actual behavior

We received two separate traces:
Trace 1: Contains pulling from SQS and calling external API
Trace 2: Contains the delete message

Javaagent or library instrumentation version

v2.10.0

Environment

JDK:
OS:

Additional context

No response

[laurit]

Please provide a minimal sample app that reproduce the issue.