chore(deps): bump logger_json from 5.1.4 to 6.2.1

[dependabot]

Bumps logger_json from 5.1.4 to 6.2.1.

Release notes

Sourced from logger_json's releases.

6.2.1

What's Changed

• fix: check if Decimal is loaded in encoder by @​davidjulien in Nebo15/logger_json#135

Full Changelog: Nebo15/logger_json@6.2.0...6.2.1

6.2.0

• Added :encoder_opts formatter option which allows passing any options down to Jason encoder, eg. if you want to format the output during development. Thanks to @​anthonator;
• Keep native DateTime, Date and Time structs when encoding them. This prevents those structs from being logged as maps. Thanks to @​imricardoramos;
• Always return :ok even if nothing is logged fixes a bug when plug logger is configured not to return anything. Thanks to @​adamu;
• A new metadata option is added which allows reading configuration from the default logger or any other place in the application environment. The downside of using it is that the application environment will be read on every logged message (since there is no way to init the state of :logger formatter);
• Replace μs with us because unicode is not always available in log aggregators. This value then also will be copied to appropriate provider-specific field. And separately copy it to an appropriate field depending on the formatter used. Thanks to @​bvobart;
• Various docs, typos, and typespec fixes. Thanks to @​dvic, @​moxley.
• Fix Task/GenServer exits correctly in Google Cloud Logger formatter. Thanks @​BrentWheeldon.

6.0.3

• Improve exception structure when logged using Elastic formatter;
• Document usage of the crash_reason metadata key across formatters.

6.0.2

Bugs

• Do not crash when metadata is set to nil, we will assume that is an empty list instead;
• Elastic logger did not write message and other keys when a conn was present in the metadata.

6.0.1

• Fixed an issue where LoggerJSON will not compile in projects where Plus or Ecto are not added as a dependency

LoggerJSON is now a set of :logger formatters

This package has undergone a full rewrite and now it's just a set of Erlang's :logger formatters. This means it has a much better integration with the ecosystem and the (outdated) custom Elixir's Logger backend is removed.

The minimum supported Elixir version is now 1.15.

Notable changes

• The logged structure for all providers has been updated to get up to date with the latest changes on those providers (eg. more metadata is logged for GoogleCloud and DataDog; Basic logs are cleaner);
• GoogleCloud formatter now logs errors that are recognized by Google Cloud Error Reporting;
• Now you can redact values in map/keyword/struct using a new LoggerJSON.Redactors.RedactKeys redactor;
• Both LoggerJSON.Plug and LoggerJSON.Ecto are now attached using Telemetry (old instrumentation callbacks are removed). Please keep in mind that using them in production is discouraged as it can be very expensive to log on every single request/database query;
• We don't use Jason.Encoder protocol for structs anymore and just encode them as any other map.
• A formatter for ElasticSearch, LogStash, FileBeat, and Kibana is added by @​bvobart.

Upgrading from 5.X

1. Update the package in mix.exs and then run mix deps.get:

++ {:logger_json, "~> 5.1"}
-- {:logger_json, "~> 6.0"}

2. Replace the legacy backend configuration and configure a default handler formatter instead:

... (truncated)

Commits

• 584a624 Bump version
• 99f2fa7 fix: check if Decimal is compiled in encoder (#135)
• 1371032 Make plug's duration/1 function private
• 274557c Bump all deps
• 17025e0 Make sure GCP/Elastic formatters won't crash on unknown error terms
• f1b0cc9 Improve formatting of the crash reports
• 09b7dc6 Bump version
• 885c731 Properly format HTTP request latency for GCL
• a27b61d Handle Task/GenServer exits correctly in Google formatter (#133)
• 5ad0dee Remap duration_us to spec-compliant fields for Elastic and DataDog formatte...
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)