feat(logger): add tenantId to logger default properties #4931
+86
−8
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.



Summary
Changes
This PR adds support for the new AWS Lambda Tenant Isolation feature by including tenantId from the Lambda context as a default property in Logger output.
When a Lambda function is invoked with tenant isolation enabled, the tenantId will automatically be included in all log entries as tenant_id, making it easier to trace and filter logs in multi-tenant environments.
Issue number: closes #4914
Implementation Details
tenantIdtoLambdaFunctionContexttype inlogKeys.tstenant_idtoPowertoolsLambdaContextKeystypeaddContext()method inLogger.tsto extracttenantIdfrom Lambda contextPowertoolsLogFormatter.tsto includetenant_idin formatted outputtenantId)tenantIdin mock contextPlease let me know if there are any points that need correction or if there is anything I should improve before merging.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.