v2.3.13

What's Changed

• Update readme build step. Updated target for make command, example make dist-x86_64 and make dist-arm64 by @chaudharysaket in #221
• Introduce support for Ruby lambda runtime by @fallwith in #204
• Change .NET Extension example to use newly released New Relic .NET lambda layer instead of OpenTracing by @jaffinito in #222
• Add tags for logs. Introduces environment variable to configure custom attributes or other metadata when sending logs directly using Extension. Use NR_TAGS & NR_ENV_DELIMITER environment variables similar to the log-ingestion-lambda to add metadata to the logs by @chaudharysaket in #224
• fix: NR_EXT log lines. Extension will not print any NR_EXT lines when logsEnabled is false, including the startup line by @keegoid-nr in #226
• Remove debug logs which get printed for each log line. Modify confusing message log - mainLoop: blocking is confusing customer and Add payloadSize to the log message Telemetry client error: %s, payload size: %d bytes" by @chaudharysaket in #227

New Contributors

• @fallwith made their first contribution in #204
• @jaffinito made their first contribution in #222
• @keegoid-nr made their first contribution in #226

Full Changelog: v2.3.12...v2.3.13

v2.3.12

What's Changed

• Update README.md to Community Plus by @iamemilio in #200
• Add local testing for Extension. Local testing is enabled by setting NEWRELIC_LOCAL_TESTING to true. Currently it supports only Python runtime. It generates the lambda layers for x86 and arm architectures layers, using publish.sh script and invokes the test lambdas using test.sh script by @chaudharysaket in #201
• Remove SSM parameter store calls. Extension has sanitycheck calls to SSM store that add to production quotas for customers. Call SSM store only when NEW_RELIC_LICENSE_KEY_SSM_PARAMETER_NAME var is set to true by @chaudharysaket in #203
• Added timeout for calls to Secrets Manager & SSM Parameter Store by @chaudharysaket in #206
• Handle Extension Warning for Node.js handlers using ES Modules. Even after accurately modifying the lambda handler to use newrelic-lambda-wrapper.handler and setting the environment variable NEW_RELIC_LAMBDA_HANDLER to be path to the initial handler, Extension was throwing warning. Used NEW_RELIC_USE_ESM to understand that customer is using ES module by @chaudharysaket in #209
• Give priority to NEW_RELIC_LICENSE_KEY and bypass calls to Secrets Manager if NEW_RELIC_LICENSE_KEY is set by @ashishsinghnr in #219

New Contributors

• @ashishsinghnr made their first contribution in #219

Full Changelog: v2.3.11...v2.3.12

v2.3.11

Lambda Release Notes:

2.3.11

Fixed

• Crashing on closed pipe caused by race condition during extension startup
• Crashing on write to closed channel due to race condition during extension shutdown
• Fixes for handler checks for docker and ESM JS environments
• Minor version bump Go grpc
• Minor version bump Go net
• Minor version bump Java gson

v2.3.10

Includes additional debugging prints for troubleshooting the logserver logic.

v2.3.9

Fixed

This release fixes a bug that crashes the extension when a single telemetry payload exceeds 1Mb when compressed.

v2.3.8

Fixed

• updated the SAM template for python to use the latest resources for python 3.10
• added additional debug logging and simplified the code for the sending of log payloads to New Relic

v2.3.7

New Relic Lambda Extension v2.3.7

Added

• support for handlers with the .mjs file extension
• allow new relic license key to be fetched from an SSM parameter

Fixed

• bumped dependencies to be compatible with latest Golang 1.19 features

v2.3.6

• HTTP Timeout: increased to 2.4 seconds
• code cleanup around timeout logic
• docs updates

v2.3.5

Users can now adjust how long the extension will attempt to retry
sending a data payload to New Relic using the environment variable
NEW_RELIC_DATA_COLLECTION_TIMEOUT. This gives customers more control
over the expected runtime of their application. Note that the extension may need to send more than one payload. The value of this timeout can be any
valid golang duration string. Some examples include 10s = 10 seconds;
500ms = 500 milliseconds; 1m = 1 minute. See
https://pkg.go.dev/maze.io/x/duration#ParseDuration for more info.

10s is the default.

v2.3.4

Prevents panics from occurring when request id map is accessed concurrently.