Releases: newrelic/newrelic-lambda-extension
Releases · newrelic/newrelic-lambda-extension
v2.3.14
What's Changed
- Update information about environment variable
NR_TAGS
in the Readme.NR_TAGS
can be used to add tags to all the lambda log events by @chaudharysaket in #229 - Fixed docker handler warning issue for containerized lambda by @chaudharysaket in #230
- Introduce support for
NEW_RELIC_ENABLED
Environment variable to disable agent and extension by @chaudharysaket in #233 - Update
NEW_RELIC_ENABLED
to env bool type by @chaudharysaket in #234 - Adds a feature to ignore Extension Startup Checks using the Lambda environment variable
NEW_RELIC_IGNORE_EXTENSION_CHECKS
. One can ignore selected Extension Checks by using a comma-separated value. For example,agent,handler
will ignore agent and handler Extension Checks. Useall
to ignore all Extension Checks. It is recommended to ignoreall
Extension Checks after the Lambda function has been successfully instrumented. by @chaudharysaket in #235 - Release v2.3.14 by @chaudharysaket in #237
Full Changelog: v2.3.13...v2.3.14
v2.3.13
What's Changed
- Update readme build step. Updated target for
make
command, examplemake dist-x86_64
andmake 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 whenlogsEnabled
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
totrue
. Currently it supports only Python runtime. It generates the lambda layers forx86
andarm
architectures layers, usingpublish.sh
script and invokes the test lambdas usingtest.sh
script by @chaudharysaket in #201 - Remove
SSM parameter store
calls. Extension has sanitycheck calls toSSM store
that add to production quotas for customers. CallSSM store
only whenNEW_RELIC_LICENSE_KEY_SSM_PARAMETER_NAME
var is set totrue
by @chaudharysaket in #203 - Added timeout for calls to
Secrets Manager
&SSM Parameter Store
by @chaudharysaket in #206 - Resolved Extension
warning
messages for Node.js runtime with ESM scripts. Previously, correctly configuringnewrelic-lambda-wrapper.handler
andNEW_RELIC_LAMBDA_HANDLER
did not eliminatewarning
message for the Node.js ESM scripts. The solution involved usingNEW_RELIC_USE_ESM
to detect ESM scripts by @chaudharysaket in #209 - Give priority to
NEW_RELIC_LICENSE_KEY
and bypass calls toSecrets Manager
ifNEW_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
- Fixed crashing on closed pipe caused by race condition during extension startup
- Fixed 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
v2.3.9
v2.3.8
v2.3.7
v2.3.6
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.