v1.3.0

Changes

Powertools now works out of the box with code guru profile handler implementation.

Metrics:

• Module now by default captures AWS Request id as property if used together with Metrics annotation. It will also capture Xray Trace ID as property if tracing is enabled. This ensures good observability and tracing.

• withSingleMetric from MetricsUtils can now pick the default namespace specified either on Metrics annotation or via POWERTOOLS_METRICS_NAMESPACE env var, without need to specify explicitly for each call.

• Metrics annotation captures metrics even in case of unhandled exception from Lambda function.

Logging:

• Ability to override object mapper used for logging event. This provides customers ability to customize how and what they want to log from event.

📜 Documentation updates

This release also marks our documentation system migration from Gatsby to MKdocs, including navigation improvements to address customers feedback.

• chore: migrate docs from gatsby to mkdocs (#308) by @pankajagrawal16
• chore: consistent field names for trace and req id with logger (#309) by @pankajagrawal16
• fix: powertools specific log level env var to not conflict with the system LOG_LEVEL (#306) by @pankajagrawal16
• docs: ability to override object mapper used for logging event (#303) by @pankajagrawal16
• feat: single metric utility method to pick default namespace (#305) by @pankajagrawal16
• feat: ability to override object mapper used for logging event (#302) by @pankajagrawal16
• feat: respect code guru profile handler implementation (#304) by @pankajagrawal16
• feat: Add function_request_id to each EMF log. (#301) by @msailes
• fix: Spotbugs issues when using Powertools(#300) @msailes
• feat: capture metrics even when handler results in exception (#286) by @pankajagrawal16
• fix(example): Update the example to v1.2.0 (#288) by @michaelbrewer

This release was made possible by the following contributors:

@michaelbrewer, @msailes and @pankajagrawal16