Daily release/12 19 24 evening

scripts/releaseNotes.mjs

@@ -70,6 +70,7 @@ const INCLUDE_AGENTS = new Set([
   'python',
   'ruby',
   'sdk',
+  'fluentbit'
 ]);
 
 const generateReleaseNoteObject = async (filePath) => {

src/content/docs/apis/nerdgraph/examples/nerdgraph-distributed-trace-data-tutorial.mdx

@@ -82,7 +82,7 @@ Additional trace-level data:
       </td>
 
       <td>
-        The trace's start time in milliseconds since the Unix epoch]([https://currentmillis.com/](https://currentmillis.com/)).
+        The trace's start time in milliseconds since the [Unix epoch](https://currentmillis.com/).
       </td>
     </tr>
   </tbody>

src/content/docs/apm/agents/go-agent/installation/install-automation-new-relic-go.mdx

@@ -52,13 +52,15 @@ The scope of what this tool can instrument in your application is limited to the
 * Capturing errors in any function wrapped or traced by a transaction
 * Tracing locally defined functions that are invoked in the application's `main()` method with a transaction
 * Tracing async functions and function literals with an async segment
-* Wrapping HTTP handlers
+* Adding middleware to supported libraries for tracing
 * Injecting distributed tracing into external traffic
 
 ### Supported Libraries [#supported-libraries]
 
 * standard library
 * net/http
+* gin
+* gRPC
 
 ## Installation [#go-easy-install]
 
@@ -74,7 +76,7 @@ go install github.com/newrelic/go-easy-instrumentation@latest
         id="setup-go-path"
         title="Setting up your GOPATH"
     >
-    The easiest way to use the installed `go-easy-instrumentation` binary is by adding your `GOPATH` bin to your `PATH`.
+    To install `go-easy-instrumentation` make sure `GOPATH` bin is in your `PATH`.
 
     <CollapserGroup>
       <Collapser
@@ -106,7 +108,7 @@ This tool works best with Git. We recommend you verify your application is on a
 
 1. Run the following CLI command to create a file named `new-relic-instrumentation.diff` in your working directory:
     ```sh
-    go-easy-instrumentation -path ../my-application/
+    go-easy-instrumentation instrument ../my-application/
     ```
 2. Open the `.diff` file and verify or correct the contents.
 3. When you are satisfied with the instrumentation suggestions, save the file, and then apply the changes:

src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx

@@ -275,20 +275,20 @@ version.
 | --- | --- | --- | --- |
 | `@apollo/gateway` | 2.3.0 | 2.9.3 | `@newrelic/[email protected]` |
 | `@apollo/server` | 4.0.0 | 4.11.2 | `@newrelic/[email protected]` |
-| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.706.0 | 11.13.0 |
-| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.705.0 | 8.7.1 |
-| `@aws-sdk/client-sns` | 3.0.0 | 3.699.0 | 8.7.1 |
-| `@aws-sdk/client-sqs` | 3.0.0 | 3.699.0 | 8.7.1 |
-| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.705.0 | 8.7.1 |
+| `@aws-sdk/client-bedrock-runtime` | 3.474.0 | 3.714.0 | 11.13.0 |
+| `@aws-sdk/client-dynamodb` | 3.0.0 | 3.714.0 | 8.7.1 |
+| `@aws-sdk/client-sns` | 3.0.0 | 3.714.0 | 8.7.1 |
+| `@aws-sdk/client-sqs` | 3.0.0 | 3.714.0 | 8.7.1 |
+| `@aws-sdk/lib-dynamodb` | 3.377.0 | 3.714.0 | 8.7.1 |
 | `@aws-sdk/smithy-client` | 3.47.0 | 3.374.0 | 8.7.1 |
-| `@elastic/elasticsearch` | 7.16.0 | 8.16.2 | 11.9.0 |
-| `@grpc/grpc-js` | 1.4.0 | 1.12.4 | 8.17.0 |
+| `@elastic/elasticsearch` | 7.16.0 | 8.17.0 | 11.9.0 |
+| `@grpc/grpc-js` | 1.4.0 | 1.12.5 | 8.17.0 |
 | `@hapi/hapi` | 20.1.2 | 21.3.12 | 9.0.0 |
 | `@koa/router` | 11.0.2 | 13.1.0 | 3.2.0 |
-| `@langchain/core` | 0.1.17 | 0.3.22 | 11.13.0 |
+| `@langchain/core` | 0.1.17 | 0.3.24 | 11.13.0 |
 | `@nestjs/cli` | 9.0.0 | 10.4.9 | 10.1.0 |
-| `@prisma/client` | 5.0.0 | 6.0.1 | 11.0.0 |
-| `@smithy/smithy-client` | 2.0.0 | 3.4.6 | 11.0.0 |
+| `@prisma/client` | 5.0.0 | 6.1.0 | 11.0.0 |
+| `@smithy/smithy-client` | 2.0.0 | 3.5.0 | 11.0.0 |
 | `amqplib` | 0.5.0 | 0.10.5 | 2.0.0 |
 | `apollo-server` | 3.0.0 | 3.13.0 | `@newrelic/[email protected]` |
 | `apollo-server-express` | 3.0.0 | 3.13.0 | `@newrelic/[email protected]` |
@@ -298,27 +298,27 @@ version.
 | `cassandra-driver` | 3.4.0 | 4.7.2 | 1.7.1 |
 | `connect` | 3.0.0 | 3.7.0 | 2.6.0 |
 | `express` | 4.6.0 | 4.21.2 | 2.6.0 |
-| `fastify` | 2.0.0 | 5.1.0 | 8.5.0 |
+| `fastify` | 2.0.0 | 5.2.0 | 8.5.0 |
 | `generic-pool` | 3.0.0 | 3.9.0 | 0.9.0 |
 | `ioredis` | 4.0.0 | 5.4.1 | 1.26.2 |
 | `kafkajs` | 2.0.0 | 2.2.4 | 11.19.0 |
 | `koa` | 2.0.0 | 2.15.3 | 3.2.0 |
 | `koa-route` | 3.0.0 | 4.0.1 | 3.2.0 |
 | `koa-router` | 11.0.2 | 13.0.1 | 3.2.0 |
 | `memcached` | 2.2.0 | 2.2.2 | 1.26.2 |
-| `mongodb` | 4.1.4 | 6.11.0 | 1.32.0 |
+| `mongodb` | 4.1.4 | 6.12.0 | 1.32.0 |
 | `mysql` | 2.2.0 | 2.18.1 | 1.32.0 |
 | `mysql2` | 2.0.0 | 3.11.5 | 1.32.0 |
-| `next` | 13.4.19 | 15.0.4 | 12.0.0 |
-| `openai` | 4.0.0 | 4.76.0 | 11.13.0 |
+| `next` | 13.4.19 | 15.1.1 | 12.0.0 |
+| `openai` | 4.0.0 | 4.77.0 | 11.13.0 |
 | `pg` | 8.2.0 | 8.13.1 | 9.0.0 |
 | `pg-native` | 3.0.0 | 3.2.0 | 9.0.0 |
 | `pino` | 7.0.0 | 9.5.0 | 8.11.0 |
 | `q` | 1.3.0 | 1.5.1 | 1.26.2 |
 | `redis` | 3.1.0 | 4.7.0 | 1.31.0 |
 | `restify` | 11.0.0 | 11.1.0 | 2.6.0 |
 | `superagent` | 3.0.0 | 10.1.1 | 4.9.0 |
-| `undici` | 5.0.0 | 7.1.0 | 11.1.0 |
+| `undici` | 5.0.0 | 7.2.0 | 11.1.0 |
 | `when` | 3.7.0 | 3.7.8 | 1.26.2 |
 | `winston` | 3.0.0 | 3.17.0 | 8.11.0 |
 

src/content/docs/infrastructure/amazon-integrations/aws-integrations-list/aws-s3-monitoring-integration.mdx

@@ -19,6 +19,8 @@ freshnessValidatedDate: never
 
 [New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) include an integration for reporting your Amazon S3 data to New Relic. This document explains how to activate the integration and describes the data reported.
 
+AWS states that [S3 CloudWatch metrics are provided on a best-effort](https://docs.aws.amazon.com/AmazonS3/latest/userguide/metrics-dimensions.html) basis and may not always be current. If the CloudWatch metrics are delayed over 48 hours at collection, [New Relic cannot ingest them](https://docs.newrelic.com/docs/data-apis/ingest-apis/metric-api/metric-api-limits-restricted-attributes/).
+
 ## Features [#features]
 
 [Amazon Simple Storage Service](https://aws.amazon.com/s3) (Amazon S3), provides developers and IT teams with secure, durable, highly-scalable cloud storage.
@@ -52,7 +54,7 @@ Note that changing the polling interval for this integration will only affect da
 
 To find your integration data, go to <DNT>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Infrastructure > AWS**</DNT> and select one of the S3 integration links.
 
-You can [query and explore your data](/docs/using-new-relic/data/understand-data/query-new-relic-data) using the `DatastoreSample` [event type](/docs/data-apis/understand-data/new-relic-data-types/#event-data), with a `provider` value of `S3Bucket`.
+You can [query and explore your data](/docs/using-new-relic/data/understand-data/query-new-relic-data) using the `DatastoreSample` [event type](/docs/data-apis/understand-data/new-relic-data-types/#event-data), with a `provider` value of `S3Bucket` or `S3BucketRequests` in case you have enabled Request and Transfer metrics.
 
 For more on how to use your data, see [Understand integration data](/docs/infrastructure/integrations/find-use-infrastructure-integration-data).
 

src/content/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-12-9-0.mdx

@@ -0,0 +1,37 @@
+---
+subject: Node.js agent
+releaseDate: '2024-12-18'
+version: 12.9.0
+downloadLink: 'https://www.npmjs.com/package/newrelic'
+security: []
+bugs: []
+features: ["Added entity linking attributes to aws-sdk v3 Lambda segments","Provided ability to define newrelic config as `newrelic.mjs`"]
+---
+
+## Notes
+
+#### Features
+
+* Added entity linking attributes to aws-sdk v3 Lambda segments ([#2845](https://github.com/newrelic/node-newrelic/pull/2845)) ([8820265](https://github.com/newrelic/node-newrelic/commit/882026502dbc12b700b893485458176bcd03f68e))
+* Provided ability to define newrelic config as `newrelic.mjs` ([#2836](https://github.com/newrelic/node-newrelic/pull/2836)) ([972b59d](https://github.com/newrelic/node-newrelic/commit/972b59d4c4bd5f212d5fd695ce1007802354b7a0))
+
+#### Documentation
+
+* Updated compatibility report ([#2828](https://github.com/newrelic/node-newrelic/pull/2828)) ([d5fe8e3](https://github.com/newrelic/node-newrelic/commit/d5fe8e323c34464e8cc10be3f5c968a96357b6f6))
+
+#### Miscellaneous chores
+
+* **deps:** Updated @newrelic/security-agent to v2.2.0 ([#2842](https://github.com/newrelic/node-newrelic/pull/2842)) ([170941e](https://github.com/newrelic/node-newrelic/commit/170941e2f16d7e84edabfff40fd31906612b393e))
+* Updated borp configs to target tests correctly ([#2835](https://github.com/newrelic/node-newrelic/pull/2835)) ([66ae59d](https://github.com/newrelic/node-newrelic/commit/66ae59d1e047dead092b3fa681017e3d42ce9474))
+
+#### Tests
+
+* Removed `tap` and cleaned up left over tap helpers ([#2804](https://github.com/newrelic/node-newrelic/pull/2804)) ([37407b6](https://github.com/newrelic/node-newrelic/commit/37407b6d14c2bd6a1c577cce811277753eb8069e))
+* Updated `match` to fail if you pass in an object that lacks the expected keys ([#2843](https://github.com/newrelic/node-newrelic/pull/2843)) ([a3db8bd](https://github.com/newrelic/node-newrelic/commit/a3db8bd993d82a3c1c8873f9e552ba5fdf7cb5f4))
+
+
+### Support statement:
+
+We recommend updating to the latest agent version as soon as it's available. If you can't upgrade to the latest version, update your agents to a version no more than 90 days old. Read more about keeping agents up to date. (https://docs.newrelic.com/docs/new-relic-solutions/new-relic-one/install-configure/update-new-relic-agent/)
+
+See the New Relic Node.js agent EOL policy for information about agent releases and support dates. (https://docs.newrelic.com/docs/apm/agents/nodejs-agent/getting-started/nodejs-agent-eol-policy/)

src/content/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1590.mdx

@@ -0,0 +1,14 @@
+---
+subject: Infrastructure agent
+releaseDate: '2024-12-19'
+version: 1.59.0
+---
+
+A new version of the agent is now available. Follow standard procedures to [update the Infrastructure agent](https://docs.newrelic.com/docs/infrastructure/install-configure-manage-infrastructure/update-or-uninstall/update-infrastructure-agent).
+New Relic recommends that you upgrade the agent and at a minimum every 3 months. As of this release, the oldest supported version is [Infrastructure agent 1.48.1](https://docs.newrelic.com/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes/new-relic-infrastructure-agent-1481/).
+
+##  Changed
+
+* Update newrelic-infra-template.yml.example in [#1956](https://github.com/newrelic/infrastructure-agent/pull/1956)
+* Adding fips compliant agents to prerelease on demand in [#1942](https://github.com/newrelic/infrastructure-agent/pull/1942)
+* Bump nri-docker, nri-flex and nri-prometheus to last versions in [#1968](https://github.com/newrelic/infrastructure-agent/pull/1968)

src/content/docs/release-notes/logs-release-notes/logs-24-12-19.mdx

@@ -0,0 +1,18 @@
+---
+subject: Logs
+releaseDate: '2024-12-19'
+version: '241219'
+---
+
+### Removal of aws.region, aws.realm, aws.accountId and plugin.type attributes for the new AWS logs onboarding integrations
+
+The recent release of New Relic's one-step observability for AWS services logs included some unwanted attributes in the ingested logs. This issue has been resolved in the current release.
+
+### Changed
+
+* The AWS Lambda and Firehose log shipping integrations [released on December 18th 2024](/docs/release-notes/logs-release-notes/logs-24-12-18) will no longer include the `aws.region`, `aws.realm` and `aws.accountId` attributes in the ingested logs. These attributes, meant for internal use in the Logs product, and shouldn't appear as attributes on log data.
+* The Firehose log shipping integration [released on December 18th 2024](/docs/release-notes/logs-release-notes/logs-24-12-18) shouldn't have included a `plugin.type: "aws-firehose"` attribute in the ingested logs. We're removing this attribute in favor of the newly introduced `instrumentation.provider: "aws"` and `instrumentation.name: "firehose"` attributes.
+
+### Notes
+
+To stay up to date with the most recent fixes and enhancements, subscribe to our [Logs RSS feed](/docs/release-notes/logs-release-notes/).

src/content/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-418.mdx

@@ -1,6 +1,6 @@
 ---
 subject: Job Manager
-releaseDate: '2024-11-03'
+releaseDate: '2024-12-03'
 version: '418'
 ---
 

src/content/docs/release-notes/synthetics-release-notes/job-manager-release-notes/job-manager-release-424.mdx

@@ -0,0 +1,10 @@
+---
+subject: Job Manager
+releaseDate: '2024-12-19'
+version: '424'
+---
+
+### Fixes
+
+* Fix for the bug introduced in VSE enabled monitors in Private Location in release-418.
+

src/content/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.12.mdx

@@ -1,6 +1,6 @@
 ---
 subject: Node browser runtime
-releaseDate: '2024-11-03'
+releaseDate: '2024-12-03'
 version: 3.0.12
 ---
 

src/content/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-3.0.15.mdx

@@ -0,0 +1,9 @@
+---
+subject: Node browser runtime
+releaseDate: '2024-12-10'
+version: 3.0.15
+---
+
+### Fixes
+
+* Removes ssh keys from the runtime image to improve security.

src/content/docs/vulnerability-management/integrations/intro.mdx

@@ -180,9 +180,9 @@ CVE detection coverage differs between agents:
     id="php-packages"
     title="PHP package support"
   >
-    As of release [v10.17.0.7](/docs/release-notes/agent-release-notes/php-release-notes/2/#new-relic-php-agent-v101707), New Relic [PHP APM Agent](/docs/apm/agents/php-agent/getting-started/introduction-new-relic-php) supports detecting CVEs in the core packages of these [frameworks](/docs/apm/agents/php-agent/getting-started/php-agent-compatibility-requirements/#frameworks).
+    As of release [v10.17](/docs/release-notes/agent-release-notes/php-release-notes/2/#new-relic-php-agent-v101707), New Relic [PHP APM Agent](/docs/apm/agents/php-agent/getting-started/introduction-new-relic-php) supports detecting CVEs in the core packages of these [frameworks](/docs/apm/agents/php-agent/getting-started/php-agent-compatibility-requirements/#frameworks).
 
-    If your project uses [Composer](https://getcomposer.org/) to manage dependencies, till [v11.2.0.15](/docs/release-notes/agent-release-notes/php-release-notes/#new-relic-php-agent-v112015) you can configure the New Relic [PHP APM agent](/docs/apm/agents/php-agent/getting-started/introduction-new-relic-php) to detect vulnerabilities in all your packages.
+    If your project uses [Composer](https://getcomposer.org/) to manage dependencies, as of release [v11.2](/docs/release-notes/agent-release-notes/php-release-notes/#new-relic-php-agent-v112015), you can configure the New Relic [PHP APM agent](/docs/apm/agents/php-agent/getting-started/introduction-new-relic-php) to detect vulnerabilities in all your packages.
 
 
     <Callout variant="tip">

src/utils/getAgentName.js

@@ -18,6 +18,7 @@ const AGENTS = {
   'job-manager-release-notes': 'job manager',
   'kubernetes-integration-release-notes': 'kubernetes',
   'logs-release-notes': 'logs',
+  'fluentbit-release-notes': 'fluentbit',
   'net-maui-release-notes': '.net maui',
   'net-release-notes': '.net',
   'new-relic-android-release-notes': 'newrelic for android',