in a single View of AWS X-RAY , i should see an end-to-end tracing path of Lambda functions , API - Gateway and Dynamodb

[niko-achilles]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Goal: in a single View of AWS X-RAY , i should see an end-to-end tracing path of Lambda functions , API - Gateway and Dynamodb .

Question:
what should be the expected tracing result by using the Extension and Layer of OpenTelemetry Javascript and ADOT Collector v0.9.1?

Setup

• functional:
  HTTP-Client --calls --> API-Gateway endpoint "/dev/views" --calls--> Lambda Function --calls--> API-Gateway endpoint "/dev/views/{id}"--calls--> Lambda Function --calls--> Dynamodb

• installation: aws-distro for opentelemetry by deploying the Lambda Layer ARN (includes OpenTelemetry Javascript and ADOT Collector v0.9.1)

• runtime: nodejs 14.x

• no config.yml deployed, defaults apply: XRAY, cloudwatch logging

• installed nodejs libs: aws sdk v2, axios for http requests

Problem Statement:
in AWS X-RAY Traces view, i do not see an end-to-end tracing path, but i see two separate tracing paths in order to have a complete view of my tracing paths.
In concrete i see:

i) HTTP-Client --calls --> API-Gateway endpoint "/dev/views" --calls--> Lambda Function --calls--> API-Gateway endpoint "/dev/views/{id}"

ii) API-Gateway endpoint "/dev/views/{id}" --calls--> Lambda Function --calls--> Dynamodb

Describe the solution you'd like
in a single View of AWS X-RAY , i should see an end-to-end tracing path of Lambda functions , API - Gateway and Dynamodb .

Describe alternatives you've considered

Additional context
in Service map View of XRAY i see in a single view as separate tracing paths:
i) HTTP-Client --calls --> API-Gateway endpoint "/dev/views" --calls--> Lambda Function --calls--> API-Gateway endpoint "/dev/views/{id}"

ii) API-Gateway endpoint "/dev/views/{id}" --calls--> Lambda Function --calls--> Dynamodb