We are discussing adding span link support. One of the motivations for this is to be able to represent the batch processing of several messages. A transaction/span cannot have multiple parents, so span links are a mechanism to link that transaction to the many initiating messages.

This includes:

• Adding span links to messaging system instrumentation
• Revert the special case for SQS triggered AWS Lambda instrumentation that invocations with a single message are handled differently from invocations with batch messages.

Spec issue

• [META 605] Spec: Add span links for message tracing #606

Agent issues

• [META 605] Add span links for message tracing apm-agent-java#2489
• [META 605] Add span links for message tracing apm-agent-dotnet#1638
• [META 605] Add span links for message tracing apm-agent-go#1222
• [META 605] Add span links for message tracing apm-agent-nodejs#2593
• [META 605] Add span links for message tracing apm-agent-python#1473
• [META 605] Add span links for message tracing apm-agent-ruby#1239
• [META 605] Add span links for message tracing apm-agent-php#633