Skip to content

Releases: newrelic/newrelic-lambda-layers

New Relic Node Agent v6.4.0.1

04 Mar 16:37
6638938

Choose a tag to compare

Re-releasing to guarantee that the Node agent is pulling the latest version (^6.4.0).

New Relic Python Agent v5.6.0.135

24 Feb 20:51
6638938

Choose a tag to compare

  • Now uses newrelic-lambda module (v0.1.1) #7

New Relic Node Agent v6.4.0

12 Feb 23:09
617db6e

Choose a tag to compare

v6.4.0_nodejs

Use Agent Default Logging Settings (#5)

New Relic Node Agent v6.3.0

05 Feb 21:58
617db6e

Choose a tag to compare

v6.3.0_nodejs

Use Agent Default Logging Settings (#5)

New Relic Python Agent v5.6.0.135

05 Feb 21:54
617db6e

Choose a tag to compare

v5.6.0.135_python

Use Agent Default Logging Settings (#5)

New Relic Node Agent v6.2.0

17 Dec 16:06
2a4ba32

Choose a tag to compare

v6.2.0_nodejs

Greedily load module/handler in Node.js layer (#3)

New Relic Python Agent v5.4.1.134

06 Jan 17:11
2a4ba32

Choose a tag to compare

v5.4.1.134_python

Greedily load module/handler in Node.js layer (#3)

New Relic Python Agent v5.4.0.132

16 Dec 23:14

Choose a tag to compare

Greedily load the handler module. (#1)

It turns out that at cold start time, the CPU isn't so throttled. So that's
the time to do big jobs like instrumenting crazy dependencies. So we should
try to load all our user's deps up front, before their first invocation.

Plus, the lazy-load strategy would have them paying for DB connection setup
and stuff on first invoke, which is bad.