Trace span longer than invocation

[liveFreeOrCode]

I don't know if this is supposed to be this way or not, but when I have my lambdas hooked up to the v8 extension my traces look something like this. This is with x-ray merging in place as well. The green and yellow trace spans are from xray, and everything in orange is from the datadog-lambda-extension

1. Why are there varying span lengths for Invoke? (I assume this is just aws nonsense, and less of a concern than the next question)
2. Why does the first span from datadog-lambda-extension go far beyond the invocation spans?

The lambda has the following layers:

with the following environment variables (api_key not shown):

[tianchu]

@liveFreeOrCode So sorry for the super late reply, we just fixed our integration with JIRA 🙇‍♂️ I hope my answer is still relevant. The long aws.lambda.function span is also from X-Ray, so I cannot explain why it's so off. BTW, all the spans converted from X-Ray receive an xray.trace_id tag that you can use to confirm it's from X-Ray and use the id to look up the trace in X-Ray to see how does it look there.

[maxday]

Closing this issue for now. Feel free to re-open it if you need