Maintenance: Leverage new InvokeStore module to keep track of X-RAY trace id

[svozza]

Summary

The AWS Lambda team has released a new InvokeStore NPM module that allows us to retriece the X-RAY trace id from AsyncLocalStorage. It means there is now another source which we need to consider when computing the X-ray trace ID. We should use it as well.

Why is this needed?

This is needed to robustly compute the X-ray trace ID.

Which area does this relate to?

Other

Solution

Use InvokeStore module and update the common trace id calculation logic.

Acknowledgment

• This request meets Powertools for AWS Lambda (TypeScript) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers

Please react with 👍 and your use case to help us understand customer demand.

[powertools-for-aws-oss-automation]

Warning

This issue is now closed. Please be mindful that future comments are hard for our team to see.
If you need more assistance, please either reopen the issue, or open a new issue referencing this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.