# Traces not linked across AWS lambdas

**URL:** <https://community.dynatrace.com/t/traces-not-linked-across-aws-lambdas/51853>\
**Category:** OpenTelemetry\
**Tags:** aws, opentelemetry, distributed-tracing, oneagent\
**Created:** [May 28, 2025, 9:47am UTC](https://community.dynatrace.com/t/traces-not-linked-across-aws-lambdas/51853 "2025-05-28T09:47:51Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![marco\_irmer](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/marco_irmer/32/3038_2.png) [@marco\_irmer](https://community.dynatrace.com/u/marco_irmer)\
**Post date:** [May 28, 2025, 12:33pm UTC](https://community.dynatrace.com/t/traces-not-linked-across-aws-lambdas/51853/2 "2025-05-28T12:33:22Z")

</div>

Are you invoking Lambda2 directly from Lambda1 (via hTTP), or are you sending an event to EventBridge and then triggering invocation of Lambda2 via event? I believe this question is important because the documentation for [tracing Lambda](https://docs.dynatrace.com/docs/ingest-from/amazon-web-services/integrate-into-aws/aws-lambda-integration/aws-lambda-extension#known-limitations) functions only seems to mention HTTP requests as a method for tracing across multiple Lambda functions.

---

_[View the full topic](https://community.dynatrace.com/t/traces-not-linked-across-aws-lambdas/51853)._
