v1.0.0

With this release, we move from release candidate to General Availability 🎉🎉🎉!

This means APIs for the core utilities Tracing, Logging, and Metrics are now stable and they are ready to be used in AWS Lambda functions written in .NET 6 running in production.

Quick links: 📜 Documentation | NuGet | Roadmap | Examples

Logging

Key features

• Capture key fields from Lambda context, cold start and structures logging output as JSON
• Log Lambda event when instructed (disabled by default)
• Log sampling enables DEBUG log level for a percentage of requests (disabled by default)
• Append additional keys to structured log at any point in time

For more information see Logging documentation.

Metrics

Key features

• Aggregate up to 100 metrics using a single CloudWatch EMF object (large JSON blob)
• Validate against common metric definitions mistakes (metric unit, values, max dimensions, max metrics, etc)
• Metrics are created asynchronously by CloudWatch service, no custom stacks needed
• Context manager to create a one off metric with a different dimension

For more information see Metrics documentation.

Tracing

Key features

• Helper methods to improve the developer experience for creating custom AWS X-Ray subsegments.
• Capture cold start as annotation.
• Capture function responses and full exceptions as metadata.
• Better experience when developing with multiple threads.
• Auto-patch supported modules by AWS X-Ray

For more information see Tracing documentation.

Special thank you

We'd like to extend our gratitude to the following people who helped with contributions, feedbacks, and their opinions while we were in developer preview:
@heitorlessa, @t1agob, @sthuber90, @nCubed, @kenfdev, @msimpsonnz, and @pgrm

v0.0.2-preview

What's Changed

• fix: custom exception JSON converter (#152) by @amirkaws
• fix: updated logger casing env vars in samples (#173) by @sliedig
• chore: updated NuGet packages (#172) by @sliedig

📜 Documentation updates

• docs: fix documentation links (#147) by @amirkaws
• docs: add discord invitation link (#155) by @sthuber90
• fix: some grammar; update links to example projects. (#170) by @nCubed
• docs: typo in metrics README (#157) by @kenfdev
• docs: updated documentation (#175) by @sliedig

This release was made possible by the following contributors:

@amirkaws, @sliedig, @sthuber90, @nCubed and @kenfdev

v0.0.1-preview.1

Summary

Introducing AWS Lambda Powertools for .NET, a suite of utilities for AWS Lambda functions running on the .NET 6 runtime, to ease the adoption of best practices such as tracing, structured logging, custom metrics, and more.

⚠️ Do not use this library for production workloads. ⚠️
AWS Lambda Powertools for .NET is currently released in preview and is intended strictly for feedback purposes only.
This version is not stable, and significant breaking changes might incur as part of the upcoming production-ready release.

--

Quick links: 📜 Documentation | ⬇️ NuGet | 💬 Feature request | 🐛 Bug Report | ⚡️Examples

Logger

🤩 Key features 🤩

• Capture key fields from Lambda context, cold start and structures logging output as JSON
• Log Lambda event when instructed (disabled by default)
• Log sampling enables DEBUG log level for a percentage of requests (disabled by default)
• Append additional keys to structured log at any point in time

Metrics

🤩 Key features 🤩

• Aggregate up to 100 metrics using a single CloudWatch EMF object (large JSON blob)
• Validate against common metric definitions mistakes (metric unit, values, max dimensions, max metrics, etc)
• Metrics are created asynchronously by CloudWatch service, no custom stacks needed
• Context manager to create a one off metric with a different dimension

Tracer

🤩 Key features 🤩

• Helper methods to improve the developer experience for creating custom AWS X-Ray subsegments.
• Capture cold start as annotation.
• Capture function responses and full exceptions as metadata.
• Better experience when developing with multiple threads.
• Auto-patch supported modules by AWS X-Ray

This release was made possible by the following contributors:

@sliedig , @amirkaws , @t1agob, @heitorlessa

Credits

Credits for the Lambda Powertools idea go to DAZN with their DAZN Lambda Powertools.