Version 3.3.0

What's Changed

• Remove Apache commons-lang classes from final logging extension jars

Full Changelog: v3.2.0...v3.3.0

Version 3.2.0

What's Changed

• Upgrade logback-core and logback-classic dependencies to version 1.2.13

Full Changelog: v3.1.0...v3.2.0

Version 3.1.0

What's Changed

• Exception Stack Traces
  • Capture the full (nested) stack trace for exceptions.
  • Add configuration option to allow unlimited stack trace size, by setting the maximum stack trace option to 0.
    • This can be configured via
      • System property: -Dnewrelic.log_extension.max_stack_size=0
      • Environment variable: NEW_RELIC_LOG_EXTENSION_MAX_STACK_SIZE=0
• Logback MDC (Mapped Diagnostic Context)
  • Fix bug where MDC values were not retained when using the extension with Logback v1.4.8 and higher.

New Contributors

• @jtduffy made their first contribution in #77
• @kanderson250 made their first contribution in #79
• @deleonenriqueta made their first contribution in #80

Full Changelog: v3.0.0...v3.1.0

Version 3.0.0

What's Changed

• Exception Stack Trace Size - this has been changed from a default of 10 to 300. This applies to all logging libraries supported by the java-log-extension project.
  • This is configurable via:
    • System property: -Dnewrelic.log_extension.max_stack_size=integer
    • Environment Variable: NEW_RELIC_LOG_EXTENSION_MAX_STACK_SIZE=integer
• Mapped Diagnostic Context (MDC) - decorating logs with MDC data is now generally supported but disabled by default. MDC keys will be prefixed by context. to prevent clashes with New Relic specific attributes. This applies to all logging libraries supported by the java-log-extension project, except for Java Util Logging (JUL) which does not provide an MDC mechanism.
  • This is configurable via:
    • System property: -Dnewrelic.log_extension.add_mdc=boolean
    • Environment Variable: NEW_RELIC_LOG_EXTENSION_ADD_MDC=boolean
  • Note: This is considered a breaking change as previously some of the logging libraries automatically added MDC. If you upgrade to this version of the java-log-extension and wish to have MDC added to your logs then you will need to explicitly enable it. Currently, this will add all MDC as filtering out specific keys is not yet supported.

Full Changelog: v2.6.0...v3.0.0

Version 2.6.0

What's Changed

• Removed the log forwarder. Please use the New Relic Java Agent if you want log forwarding to be used.
• Upgrade Gradle to version 7.5.1

New Contributors

• @kford-newrelic made their first contribution in #66
• @obenkenobi made their first contribution in #68

Full Changelog: v2.5.0...v2.6.0

Version 2.5.0

What's Changed

• feat: added logback marker to JSON layout if present by @derylseale in #52
• Update to TelemetrySDK 0.13.2 to address CVE-2022-25647 by @jasonjkeller in #59

New Contributors

• @derylseale made their first contribution in #52

Full Changelog: v2.4.0...v2.5.0

Version 2.4.0

What's Changed

• Add a forwarder module that does log forwarding using the New Relic Java Telemetry SDK
• Implement com.newrelic.logging.logback.NewRelicHttpAppender to do log forwarding for logback
• Update log4j2 dependencies to version 2.17.2
• Update Java agent API dependencies to version 7.6.0

New Contributors

• @noly made their first contribution in #45

Full Changelog: v2.3.2...v2.4.0

Version 2.3.2

What's Changed

• Update documentation to specify support for Log4J 2.13.2 or higher by @twcrone in #47
• Add warning for CVE-2021-44228 by @twcrone in #48
• update l4j and newr api point releases by @tbradellis in #49
• point release by @tbradellis in #50

New Contributors

• @twcrone made their first contribution in #47

Full Changelog: v2.3.1...v2.3.2

2.3.1

What's Changed

• update log4j compile time dep by @tbradellis in #42

• bump gradle version by @tbradellis in #44

• Updates log4j compile time dependencies to use 2.16. While these are not used at runtime, we are updating dependency versions to avoid any concern in the community that the vulnerability from CVE-2021-44228 exists in the jar for this extension.
  related links:
  https://logging.apache.org/log4j/2.x/security.html
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228

• This release also bumps the the newrelic-api:7.4.2 jar which coincides with the same patch for log4j in the newrelic-java-agent.

• This point release also updates the log4j dependency version for examples included in the repository, which in fact did use a bundled log4j.

New Contributors

• @tbradellis made their first contribution in #42

Full Changelog: v2.3...v2.3.1

2.3

Add support for custom arguments in the JSON log for logback. Thank you @krishnatejadinavahi

Usage:

import static com.newrelic.logging.logback.CustomArgument.keyValue;
logger.info("Custom log", keyValue("customKey", "customValue"));