- Duration doesn’t roll up naturally. It wouldn’t make sense to include the duration of a downstream transaction (e.g. an SQS consumer) as part of the duration of the transaction that produced the message (e.g. the producer Lambda) — the two run independently, often at completely different times.
- A single transaction can have multiple sources. A consumer might process a batch of several messages in one invocation, and those messages could have been sent by different upstream transactions.
Consumed By— the downstream transaction(s) that consumed the message(s) this transaction sent.Produced By— the upstream transaction(s) that sent the message(s) this transaction consumed.




- Did any of my downstream async services fail?
- Which transaction sent the message that triggered this one?