powertools-lambda-typescript VS winston

Logger class is now more extensible You can now overwrite the Logger methods createAndPopulateLogItem, printLog, and processLogItem, which were previously private. This allows you to extend the Logger and add new functionality, e.g., implement your own message buffer. Release v2.12.0

The Powertools GitHub repository offers nice examples to integrate and learn from. For example here are nice example written in AWS CDK. Following I will list the features I gained some experience with.

Lambda Powertools TypeScript can't be used directly as an ES Modules dependency, but there is an issue open, so please consider adding your +1. For now, it's possible to get by with a require shim or via cjs tricks but it would be great to see native support for ES Modules in Lambda Powertools TypeScript.

for secrets, I would recommend using AWS PowerTools if you can (depending on your language) - https://github.com/awslabs/aws-lambda-powertools-python - https://github.com/awslabs/aws-lambda-powertools-typescript

The documentation for Lambda Powertools TypeScript is pretty good and provides several examples with even more on GitHub.

Last week, AWS announced the beta release of AWS Lambda Powertools Typescript. This is a suite of TypeScript utilities for AWS Lambda functions to enable the adoption of best practices in areas such as structured logging, tracing and custom metrics.

Winston Logging Library: https://www.npmjs.com/package/winston

and it got me wondering what this package is about. So, when I quickly googled Winston, I found this npm package.

Use a structured logger like Winston to record failures and facilitate debugging in production.

Winston

Logs: pino, winston, bunyan

Server-side logging: Use a logging library like Winston. It keeps track of everything happening on the server – connections, events, and errors.

Express.js does not have built-in support for logging. You can use libraries like Winston to log messages.

Step 1 - create your logger (in my case I used winston, which works great with Datadog that we use for monitoring)

This will not scale with the volume of data, because the overhead associated with sending each piece of data is large in comparison to the volume of each individual piece. This is why most observability frameworks – including loggers like winston – buffer telemetry data before exporting it.