Bump AWS.Lambda.Powertools.Metrics from 3.1.0 to 3.2.0#85
Open
dependabot[bot] wants to merge 1 commit intodevelopfrom
Open
Bump AWS.Lambda.Powertools.Metrics from 3.1.0 to 3.2.0#85dependabot[bot] wants to merge 1 commit intodevelopfrom
dependabot[bot] wants to merge 1 commit intodevelopfrom
Conversation
--- updated-dependencies: - dependency-name: AWS.Lambda.Powertools.Metrics dependency-version: 3.2.0 dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: AWS.Lambda.Powertools.Metrics dependency-version: 3.2.0 dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: AWS.Lambda.Powertools.Metrics dependency-version: 3.2.0 dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: AWS.Lambda.Powertools.Metrics dependency-version: 3.2.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated AWS.Lambda.Powertools.Metrics from 3.1.0 to 3.2.0.
Release notes
Sourced from AWS.Lambda.Powertools.Metrics's releases.
3.2.0
Summary
In this release we added new logging features including
ExtraKeysfor temporary key management within scopes, anEnabledproperty for LogBufferingconfiguration, andTenantIdsupport for Lambda Tenant Isolation observability. We also fixed a stdout file descriptor leak in the logging utility and an idempotency key collision issue when using multiple idempotent methods.Thank you @jihed-garaouch for your first contribution ⭐
What's New
✨ ExtraKeys for Logger
| Docs
Added
ExtraKeys()method to Logger for temporary key management within scopes. Keys are automatically cleaned up when the scope exits, with full support for async/await boundaries using AsyncLocal-based scope storage. Supports multiple overloads: Dictionary, params tuples, and nested scopes.Dictionary syntax:
Tuple syntax:
✨ LogBuffering Enabled Property
| Docs
Added
Enabledproperty toLogBufferingOptionsto explicitly control log buffering activation. This allows configuring log buffering through property assignment instead of requiring constructor parameters.✨ TenantId Support
Added
TenantIdfromILambdaContextto the default logger properties to support AWS Lambda Tenant Isolation observability. When using Lambda Tenant Isolation, theTenantIdis automatically captured and included in your structured log output.