Bump powertools-tracing from 1.2.0 to 1.3.0 in /templates/java8.al2/cookiecutter-aws-sam-hello-powertools-java-gradle/{{ cookiecutter.project_slug }}/HelloWorldFunction

[dependabot]

⚠️ Dependabot is rebasing this PR ⚠️

If you make any changes to it yourself then they will take precedence over the rebase.

---

Bumps powertools-tracing from 1.2.0 to 1.3.0.

Release notes

Sourced from powertools-tracing's releases.

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

Changelog

Sourced from powertools-tracing's changelog.

[1.3.0] - 2021-03-05

• Powertools: It now works out of the box with code guru profile handler implementation.
• 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.
• 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.
• Metrics: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:Metrics annotation captures metrics even in case of unhandled exception from Lambda function.
• Docs: Migrated from Gatsby to MKdocs documentation system

Commits

• 087e691 chore: Prep release 1.3.0 (#316)
• 161d2ab chore: migrate docs from gatsby to mkdocs (#308)
• 4717a5f build(deps): bump software.amazon.awssdk:bom from 2.16.10 to 2.16.12 (#315)
• 8b907cc build(deps): bump jackson-databind from 2.12.1 to 2.12.2 (#313)
• e310022 build(deps): bump software.amazon.awssdk:bom from 2.16.9 to 2.16.10 (#312)
• ca7f1a1 chore: consistent field names for trace and req id with logger (#309)
• 86d7448 build(deps): bump software.amazon.awssdk:bom from 2.16.8 to 2.16.9 (#311)
• 81e3203 build(deps): bump commons-lang3 from 3.11 to 3.12.0 (#310)
• 15de652 build(deps): bump software.amazon.awssdk:bom from 2.16.7 to 2.16.8 (#307)
• 4505213 fix: powertools specific log level env var to not conflict with the system LO...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)