Release v1.0.6

##Release v1.0.6

What's Changed

• Feat: Connection failure Management by @gsidhwani-nr in #8
• Update README.md by @gsidhwani-nr in #9
• QueueCapacity and connection tuning by @gsidhwani-nr in #10

Applying a New Version

<dependency>
  <groupId>com.newrelic.labs</groupId>
  <artifactId>custom-log4j2-appender</artifactId>
  <version>1.0.6</version>
</dependency>

App Config Settings - Refer ReadMe

Full Changelog: 1.0.5...1.0.6

v1.0.5

Release Notes - Version 1.0.5

New Relic Log4j2 Appender

New Features

• Configurable Retry Mechanism: Introduced a new configuration parameter maxRetries, allowing users to specify the maximum number of retry attempts for sending logs.

  • Log Failure Management: If logs cannot be sent successfully within the specified retries, they will be discarded. This provides greater control over log failure management.

• Optimized Log Sending: Enhanced the appender to manage retry attempts more effectively by utilizing the configured flushInterval before retrying after a failure.

  • Network Efficiency: This optimization prevents excessive send attempts and reduces potential strain on the network and endpoint.

• Seamless Recovery: Improved the appender's ability to reset the retry counter once the connection to the endpoint is restored and logs are sent successfully.

  • Normal Operations: Allows the appender to resume normal operations, immediately flushing logs when the batch size is reached, ensuring timely log delivery.

• Handling New Messages After Retry Exhaustion: Enhanced the appender to ensure that if the queue is cleared due to retry exhaustion, new messages will be added and processed with a fresh retry cycle.

  • Continued Log Delivery: Each new message will be attempted up to the maxRetries limit, ensuring continued log delivery efforts.

• Connection Timeout Configuration: Introduced a new configuration parameter timeout to specify the connection timeout for HTTP requests to New Relic's logging service.

  • Default Timeout: Set to 30 seconds (30000 milliseconds), this parameter helps manage network conditions and server response times.

Applying a New Version

<dependency>
  <groupId>com.newrelic.labs</groupId>
  <artifactId>custom-log4j2-appender</artifactId>
  <version>1.0.5</version>
</dependency>

App Config Settings - Refer ReadMe

These enhancements in version 1.0.5 aim to improve the robustness and flexibility of your logging setup, providing better control over retry mechanisms and network interactions.

Full Changelog: 1.0.4...1.0.5

v1.0.4

What's Changed

• fix: requeue logentries failed due to case sensitive applicationName parameter

Applying a new Version

<dependency>
  <groupId>com.newrelic.labs</groupId>
  <artifactId>custom-log4j2-appender</artifactId>
  <version>1.0.4</version>
</dependency>

Full Changelog: 1.0.3...1.0.4

v1.0.3

Release Notes - Version 1.0.3

New Relic Log4j2 Appender

New Features

• Custom Fields Configuration: Introduced a new configuration parameter mergeCustomFields. This parameter allows users to control how custom fields are added to log events.
  • Default Behavior: Custom fields are added as subfields under the custom field (e.g., custom.field1, custom.field2).
  • Merge Custom Fields: When mergeCustomFields is set to true, custom fields are added as main attributes (e.g., field1, field2).

Applying a new Version

<dependency>
  <groupId>com.newrelic.labs</groupId>
  <artifactId>custom-log4j2-appender</artifactId>
  <version>1.0.3</version>
</dependency>

What's Changed

• feat: Configurable custom fields storing by @gsidhwani-nr in #6

Full Changelog: 1.0.2...1.0.3

v1.0.2

Release Notes for v1.0.2

We are excited to announce the release of version 1.0.2 of the New Relic Log4j2 Appender. This release includes several enhancements and improvements to better meet your logging needs.

Maven Dependency

Please take a note

This new version has a new group assigned for the Maven dependency:

<dependency>
  <groupId>com.newrelic.labs</groupId>
  <artifactId>custom-log4j2-appender</artifactId>
  <version>1.0.2</version>
</dependency>

New Features and Enhancements

1. Custom Fields Support:

   • Applications can now pass custom fields as a comma-separated list of name-value pairs.
   • This allows for greater flexibility and customization in your log data.

2. Improved Flushing Mechanism:

   • The appender now flushes the log batch whenever the batch is full or the flush interval is triggered.
   • This ensures timely delivery of logs and reduces the risk of log data loss.

What's Changed

• Enhancement: Custom Fields by @gsidhwani-nr in PR #4
• Enhancement: Batch Full Flush by @gsidhwani-nr in PR #5

Full Changelog: Compare v0.0.8...v1.0.2

We hope you find these improvements beneficial. If you have any feedback or encounter any issues, please feel free to reach out to us.

Thank you for using the New Relic Log4j2 Appender!

v0.0.8

v0.0.8

This pre-release is for customers to test the custom Log4j2 appender.

• Artifact: The attached custom-log4j2-appender.jar is a pre-built jar file intended for local use only.
• Instructions: For detailed setup and usage instructions, please refer to the README. You can also integrate the project using Maven Central.

Thank you for testing!

What's Changed

• feat: 1st working draft Custom log4j2 appender by @gsidhwani-nr in #1
• Updated README.md by @gsidhwani-nr in #2

New Contributors

• @gsidhwani-nr made their first contribution in #1

Full Changelog: https://github.com/newrelic-experimental/newrelic-java-log4j-appender/commits/0.0.8