aws-lambda-powertools-roadmap VS aws-xray-sdk-node

The Lambda Powertools for Python make it easy to add a correlation_id. By using the structured logs from the powertools you can use each property in the log line to query on. It has a lot more utilities, so I encourage go check it out! Not a python developer? There is a Java version and there are some initiatives on the roadmap to add other languages as well.

You see in the node xrays sdk that each AWS service is customized with the captureAWSRequest function, which is responsible for the X-Ray calls.

Generally speaking, it is encouraged on serverless-heavy environments (assuming Lambdas, API Gateways, AppSync, DynamoDB and similar services were configured to use it). However, some crucial pieces are still missing, like a proper SQS integration. Bear that in mind.

So what do we get for that? The Tracer module wraps the AWS X-Ray SDK (as a transitive dependency). It doesn't really add any net new capabilities, but makes the SDK easier to work with. In my experience, that SDK is a bit of a bear so this may be well worth it. We can decorate class methods to introduce new trace segments in a single line of code. We can also use the imperative form to add new traces where we see fit. We can capture AWS clients, but that simply exposes the X-Ray SDK.

aws-xray-sdk-node: https://github.com/aws/aws-xray-sdk-node/issues/208