SQS Event and SQS Message have links to SQS message AWSTraceHeader?

[rackerWard]

In the aws-lambda.md https://github.com/open-telemetry/semantic-conventions/blob/main/docs/faas/aws-lambda.md SQS it seems the SQS Event will have a span link for each message containing AWSTraceHeader and each SQS Message will have a span link to the AWSTraceHeader

Is there a reason the span link is performed on both the SQS Event and the SQS Message? What is the intent behind adding the span links to the SQS Event?

Is the intent so that the SQS Event's span links document all the SQS messages received? Because the lambda may not process all of the SQS Messages or may not call the instrumentation for processing SQS messages?

Doesn't this create a tree where the SQS Message trace context has two entry points into the SQS trigger Lambda invocation? One at the SQS Event (Lambda Invoke) and the SQS Message span?

What kind of trace trees are not allowed in OpenTelemetry? What kind of trace trees should be expected?

[joaopgrassi]

This was closed by mistake by the stale bot. Re-opening