Bump net.logstash.logback:logstash-logback-encoder from 7.1.1 to 7.3

[dependabot]

Bumps net.logstash.logback:logstash-logback-encoder from 7.1.1 to 7.3.

Release notes

Sourced from net.logstash.logback:logstash-logback-encoder's releases.

logstash-logback-encoder-7.3

This new version brings support for the new features introduced in Logback 1.3 while remaining compatible with both Logback 1.2 (can be used with both versions).

What's Changed

⚠️ Update considerations and deprecations

• Support for Timestamp with nanosecond precision (logback 1.3+) by @​brenuart in logfellow/logstash-logback-encoder#833 TimestampJsonProvider has been upgraded to take advantage of the nanosecond precision introduced in Logback 1.3 when recording event timestamp.

  When upgrading to Logback 1.3, people using one of the standard java.time.DateTimeFormatter formats like [ISO_OFFSET_DATE_TIME] (see documentation for more information) will have their timestamp rendered with nanoseconds instead of millis. If this is not desired you should instead configure the explicit format you need instead of making reference to one of the standard formats provided by java.time.DateTimeFormatter.

• Add support for Event#getSequenceNumber (logback 1.3+) by @​brenuart in logfellow/logstash-logback-encoder#843 Starting from version 1.3 Logback can assign a unique sequence number to each event as long as the LoggerContext is configured with a SequenceNumberGenerator (see Logback). This number can later be retrieved from the event itself by calling the newly introduced getSequenceNumber() method.

  The SequenceJsonProvider has been upgraded to leverage this new feature. The actual behaviour depends on which version of Logback is found on the class path at runtime:

  • Logback >= 1.3: get the sequence value from the event itself provided a SequenceNumberGenerator is defined in the LoggerContext. If not, revert to using a locally incremented sequence number (old behaviour)
  • Logback < 1.3: use a locally incremented sequence number (old behaviour)

  If this behaviour is not desired, you have the choice to set your own custom strategy (see the documentation for more information).

• ShortenedThrowableConverter: <exclude> and <exclusions> are mutually exclusive (#876) by @​brenuart in logfellow/logstash-logback-encoder#881

• Add ability to customize the PrettyPrinter by @​philsttr in logfellow/logstash-logback-encoder#926

✨ New features and improvements

• Add support for multiple Markers attached to a single LoggingEvent by @​brenuart in logfellow/logstash-logback-encoder#840

• 848 ipv6 support in DestinationParser by @​brenuart in logfellow/logstash-logback-encoder#849

• Implement initialSendDelay feature by @​brenuart in logfellow/logstash-logback-encoder#860 It may happen you want to add an extra delay before sending the first events after the connection is established. This may come in handy in situations where the appender connects to an intermediate proxy that needs some time to establish a connection to the final destination. Without this extra delay, the first events written by the appender immediately after the connection to the proxy is created may be lost if the proxy ultimately fails to connect to the final destination.

  To enable this feature, set the new initialSendDelay property to the desired value. The default value is 0 which means "no delay", that is start flushing events immediately after the connection is established. See Initial Send Delay for more information.

• 859 LogstashEncoder should throw IllegalArgumentException instead of logging an error status when attempting to use by @​brenuart in logfellow/logstash-logback-encoder#861

• 867 shortenedthrowableconverter truncate stacktrace based on regex pattern by @​brenuart in logfellow/logstash-logback-encoder#874 The ShortenedThrowableConverter now allows you to shorten the stacktrace by cutting it just after frames matching a regular expression. See Truncate after Regex in the documentation for more details about this new feature.

• Add a way to escape the comma in comma separated property values by @​brenuart in logfellow/logstash-logback-encoder#882

• ShortenedThrowableConverter: add option to set my own custom abbreviator by @​brenuart in logfellow/logstash-logback-encoder#893

• Build consumer (flatten) POM by @​brenuart in logfellow/logstash-logback-encoder#898

🐞 Bug fixes

• Fix absolute PathMask issue by @​brenuart in logfellow/logstash-logback-encoder#845
• Fix non-JSON generators (regression in 7.0) by @​philsttr in logfellow/logstash-logback-encoder#930

📖 Documentation, Tests and Build

• Fix hyperlinks in README by @​cand126 in logfellow/logstash-logback-encoder#869
• Use instead of nested appenders in XML configuration by @​brenuart in logfellow/logstash-logback-encoder#875
• Bump github actions to their latest version by @​brenuart in logfellow/logstash-logback-encoder#884
• Fix link in readme by @​wsargent in logfellow/logstash-logback-encoder#887
• Bump build to JDK 17 by @​philsttr in logfellow/logstash-logback-encoder#924
• Setup release notes categories for automatic release notes generation by @​philsttr in logfellow/logstash-logback-encoder#927
• Remove usage of the animal-sniffer-maven-plugin by @​brenuart in logfellow/logstash-logback-encoder#932

🆙 Dependency Upgrades

... (truncated)

Commits

• 84212bf [maven-release-plugin] prepare release logstash-logback-encoder-7.3
• 289fefd [release]
• e5f19f0 Merge pull request #935 from logfellow/dependabot/maven/org.apache.maven.plug...
• 0b9cd9d Bump maven-javadoc-plugin from 3.4.1 to 3.5.0
• ecae1af Merge pull request #932 from logfellow/931-build-remove-animal-sniffer-maven-...
• c9ab293 Merge pull request #930 from logfellow/fix_non_json_generators
• 489498b Re-enable javadoc links to Logback
• 8b839c4 Fix typo in comments
• f85dcd8 Remove <source> and <target> compiler arguments
• 74cc56e Remove animal-sniffer-maven-plugin
• 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)