From 15c552b59a9a45473585157c7aeada3b6325709b Mon Sep 17 00:00:00 2001 From: Dkairu <40675135+Dkairu@users.noreply.github.com> Date: Tue, 12 Mar 2024 12:10:15 -0400 Subject: [PATCH 01/24] Update host-integrations-standard-configuration-format.mdx Put an example for escaping backslashes in windows --- .../host-integrations-standard-configuration-format.mdx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/specifications/host-integrations-standard-configuration-format.mdx b/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/specifications/host-integrations-standard-configuration-format.mdx index 9fca3890df4..f2b230b979e 100644 --- a/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/specifications/host-integrations-standard-configuration-format.mdx +++ b/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/specifications/host-integrations-standard-configuration-format.mdx @@ -249,7 +249,11 @@ integrations: If there is no executable with this name in the above folders the agent logs an error and the integration is not executed. - In Windows, do not append the `.exe` extension to the name. The agent does this for you (for example, `name: nri-mysql` would look for `nri-mysql.exe` in the above folders). + In Windows, do not append the `.exe` extension to the name. The agent does this for you (for example, `name: nri-mysql` would look for `nri-mysql.exe` in the above folders). You also need to escape the backslashes when entering this parameter. For example + ``` + - name: nri-mysql + exec: '"D:\\CustomFolder\\NewRelic\\Newrelic-infra\\newrelic-integrations\\bin\\nri-mysql"' + ``` From 8fc6763cf351276c903f8d25aa4d9d346fe0c716 Mon Sep 17 00:00:00 2001 From: Rob Siebens Date: Tue, 12 Mar 2024 13:38:05 -0700 Subject: [PATCH 02/24] fix(Infrastructure agent): Add colon --- .../host-integrations-standard-configuration-format.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/specifications/host-integrations-standard-configuration-format.mdx b/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/specifications/host-integrations-standard-configuration-format.mdx index f2b230b979e..cfd82f69942 100644 --- a/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/specifications/host-integrations-standard-configuration-format.mdx +++ b/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/specifications/host-integrations-standard-configuration-format.mdx @@ -249,7 +249,7 @@ integrations: If there is no executable with this name in the above folders the agent logs an error and the integration is not executed. - In Windows, do not append the `.exe` extension to the name. The agent does this for you (for example, `name: nri-mysql` would look for `nri-mysql.exe` in the above folders). You also need to escape the backslashes when entering this parameter. For example + In Windows, do not append the `.exe` extension to the name. The agent does this for you (for example, `name: nri-mysql` would look for `nri-mysql.exe` in the above folders). You also need to escape the backslashes when entering this parameter. For example: ``` - name: nri-mysql exec: '"D:\\CustomFolder\\NewRelic\\Newrelic-infra\\newrelic-integrations\\bin\\nri-mysql"' From aca5a16f282608e731048aac01a245d2f3087c10 Mon Sep 17 00:00:00 2001 From: Rob Siebens Date: Tue, 12 Mar 2024 16:44:58 -0700 Subject: [PATCH 03/24] fix(Infrastructure agent): Temporarily back out the escape section --- .../host-integrations-standard-configuration-format.mdx | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/specifications/host-integrations-standard-configuration-format.mdx b/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/specifications/host-integrations-standard-configuration-format.mdx index cfd82f69942..90b023089b7 100644 --- a/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/specifications/host-integrations-standard-configuration-format.mdx +++ b/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/specifications/host-integrations-standard-configuration-format.mdx @@ -249,11 +249,7 @@ integrations: If there is no executable with this name in the above folders the agent logs an error and the integration is not executed. - In Windows, do not append the `.exe` extension to the name. The agent does this for you (for example, `name: nri-mysql` would look for `nri-mysql.exe` in the above folders). You also need to escape the backslashes when entering this parameter. For example: - ``` - - name: nri-mysql - exec: '"D:\\CustomFolder\\NewRelic\\Newrelic-infra\\newrelic-integrations\\bin\\nri-mysql"' - ``` + In Windows, do not append the `.exe` extension to the name. The agent does this for you (for example, `name: nri-mysql` would look for `nri-mysql.exe` in the above folders). From 93b737a2e7b3d15fc0cf212c2cb018290a9fe17b Mon Sep 17 00:00:00 2001 From: Svetlana Brennan <50715937+svetlanabrennan@users.noreply.github.com> Date: Wed, 20 Mar 2024 13:30:23 -0500 Subject: [PATCH 04/24] update min versions and add more supported libraries --- ...ompatibility-requirements-nodejs-agent.mdx | 129 +++++++++++++++++- 1 file changed, 122 insertions(+), 7 deletions(-) diff --git a/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx b/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx index 67c96dd7cc3..e54802db7e5 100644 --- a/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx +++ b/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx @@ -206,42 +206,92 @@ The Node.js agent monitors the performance of Node.js application calls to these Datastore + + `npm` module name + + + + Minimum module version + + + + Minimum agent version + + Notes [Cassandra](https://www.npmjs.com/package/cassandra-driver) + `cassandra-driver` + 3.4.0 + 1.7.1 [ElasticSearch](https://www.npmjs.com/package/@elastic/elasticsearch) + `elasticsearch` + 7.13.0 + 11.2.0 [Memcached](https://www.npmjs.com/package/memcached) + `memcached` + 0.0.7 + 0.9.0 [MongoDB](https://www.npmjs.com/package/mongodb) + `mongodb` + 2.1.0 + 0.9.0< - MySQL - Via [mysql](https://www.npmjs.com/package/mysql) and [mysql2](https://www.npmjs.com/package/mysql2) packages + [MySQL](https://www.npmjs.com/package/mysql) + `mysql` + 2.2.0 + 0.9.0 + + + + [MySQL 2](https://www.npmjs.com/package/mysql2) + `mysql2` + 1.31.1 + 1.25.2 + [Redis](https://www.npmjs.com/package/redis) + `redis` + 2.0.0 + 0.9.2 [Postgres](https://www.npmjs.com/package/pg) + `pg` + 8.2+ + 9.0.0 Including the [native](https://www.npmjs.com/package/pg-native) and [pure JavaScript](https://www.npmjs.com/package/pg-js) packages [Prisma](https://www.prisma.io/) + [`prisma/client`](https://www.npmjs.com/package/@prisma/client) + 5.0.0 + 9.11.0 The Prisma instrumentation treats Prisma itself as the datastore, not the underlying SQL or NoSQL datastore that Prisma is configured to use. This means metrics and traces will show Prisma ORM queries such as `find` or `updateMany` and not SQL statements such as `SELECT` or `UPDATE`. As an exception, raw Prisma queries will record the actual raw SQL or NoSQL query. + + [ioredis](https://www.npmjs.com/package/ioredis) + [`ioredis`](https://www.npmjs.com/package/ioredis) + 3.0+ + 1.26.2 + + @@ -303,11 +353,11 @@ We collect [instance details for a variety of databases and database drivers](/d - 4.0.0 + 8.2+ - 1.31.0 + 9.0.0 @@ -447,11 +497,11 @@ We collect [instance details for a variety of databases and database drivers](/d - 4.0.0 + 5.0.0 - 9.11.0 + 11.0.0 @@ -559,6 +609,71 @@ In order to support [APM logs in context](/docs/apm/new-relic-apm/getting-starte For other message queue libraries, use [custom instrumentation](/docs/agents/nodejs-agent/supported-features/nodejs-custom-instrumentation#message-client). + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Library + + `npm` module name + + Minimum module version + + Minimum agent version +
+ [Director](https://www.npmjs.com/package/director) + + `director` + + 1.2+ + + 2.0.0 +
+ [generic-pool](https://www.npmjs.com/package/generic-pool) + + `generic-pool` + + 2.4+ + + 0.9+ +
+ + - [Hapi](https://www.npmjs.com/package/hapi) + [Hapi](https://www.npmjs.com/package/@hapi/hapi) From 865fd8d6b745b195dae99f18971807f719ef7db4 Mon Sep 17 00:00:00 2001 From: lromer22 <85335776+lromer22@users.noreply.github.com> Date: Wed, 20 Mar 2024 15:02:18 -0400 Subject: [PATCH 05/24] node-browser-runtime-2.2.45 release notes --- .../node-browser-runtime-2.2.45.mdx | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 src/content/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-2.2.45.mdx diff --git a/src/content/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-2.2.45.mdx b/src/content/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-2.2.45.mdx new file mode 100644 index 00000000000..1e4c8e07ab5 --- /dev/null +++ b/src/content/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-2.2.45.mdx @@ -0,0 +1,16 @@ +--- +subject: Node browser runtime +releaseDate: '2024-03-20' +version: 2.2.45 +--- + +### Features +* Adds form-data module +* Adds async module + +### Fixes +* Assert element throwing error when element not found +* Masks sensitive header values in HAR log + +### Security patches +* CVE-2023-4228 From 62d664fd9e2f3efbe52d2007b8f4ea6049560f28 Mon Sep 17 00:00:00 2001 From: lromer22 <85335776+lromer22@users.noreply.github.com> Date: Wed, 20 Mar 2024 15:05:21 -0400 Subject: [PATCH 06/24] Update node-browser-runtime-2.2.45.mdx --- .../node-browser-runtime-2.2.45.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-2.2.45.mdx b/src/content/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-2.2.45.mdx index 1e4c8e07ab5..b4b8299a645 100644 --- a/src/content/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-2.2.45.mdx +++ b/src/content/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-2.2.45.mdx @@ -9,7 +9,7 @@ version: 2.2.45 * Adds async module ### Fixes -* Assert element throwing error when element not found +* Step monitor Assert element step preemptively throwing error when element not found * Masks sensitive header values in HAR log ### Security patches From e8a81a56a8556889920bce33174207ddfe8f7238 Mon Sep 17 00:00:00 2001 From: lromer22 <85335776+lromer22@users.noreply.github.com> Date: Wed, 20 Mar 2024 15:06:54 -0400 Subject: [PATCH 07/24] Update node-browser-runtime-2.2.45.mdx --- .../node-browser-runtime-2.2.45.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-2.2.45.mdx b/src/content/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-2.2.45.mdx index b4b8299a645..06f0e072eb0 100644 --- a/src/content/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-2.2.45.mdx +++ b/src/content/docs/release-notes/synthetics-release-notes/node-browser-runtime-release-notes/node-browser-runtime-2.2.45.mdx @@ -9,7 +9,7 @@ version: 2.2.45 * Adds async module ### Fixes -* Step monitor Assert element step preemptively throwing error when element not found +* Step monitor Assert element step no longer preemptively throws error when element not found * Masks sensitive header values in HAR log ### Security patches From aa4f8f10678674903eff996cb760c870c6b7bf03 Mon Sep 17 00:00:00 2001 From: Svetlana Brennan <50715937+svetlanabrennan@users.noreply.github.com> Date: Wed, 20 Mar 2024 15:45:45 -0500 Subject: [PATCH 08/24] fix other libraries min support and doc format --- ...ompatibility-requirements-nodejs-agent.mdx | 180 +++++++++++++++--- 1 file changed, 156 insertions(+), 24 deletions(-) diff --git a/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx b/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx index e54802db7e5..454b9f3b4e8 100644 --- a/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx +++ b/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx @@ -232,43 +232,43 @@ The Node.js agent monitors the performance of Node.js application calls to these [ElasticSearch](https://www.npmjs.com/package/@elastic/elasticsearch) `elasticsearch` - 7.13.0 - 11.2.0 + 7.16.0 + 11.9.0 [Memcached](https://www.npmjs.com/package/memcached) `memcached` - 0.0.7 - 0.9.0 + 1.0.0 + 1.33.0 [MongoDB](https://www.npmjs.com/package/mongodb) `mongodb` 2.1.0 - 0.9.0< + 1.32.0< [MySQL](https://www.npmjs.com/package/mysql) `mysql` 2.2.0 - 0.9.0 + 1.32.0 [MySQL 2](https://www.npmjs.com/package/mysql2) `mysql2` 1.31.1 - 1.25.2 + 1.32.0 [Redis](https://www.npmjs.com/package/redis) `redis` 2.0.0 - 0.9.2 + 1.31.0 @@ -280,7 +280,7 @@ The Node.js agent monitors the performance of Node.js application calls to these [Prisma](https://www.prisma.io/) - [`prisma/client`](https://www.npmjs.com/package/@prisma/client) + [`@prisma/client`](https://www.npmjs.com/package/@prisma/client) 5.0.0 9.11.0 The Prisma instrumentation treats Prisma itself as the datastore, not the underlying SQL or NoSQL datastore that Prisma is configured to use. This means metrics and traces will show Prisma ORM queries such as `find` or `updateMany` and not SQL statements such as `SELECT` or `UPDATE`. As an exception, raw Prisma queries will record the actual raw SQL or NoSQL query. @@ -407,7 +407,7 @@ We collect [instance details for a variety of databases and database drivers](/d - 2.4.1 + 2.2.0 @@ -417,7 +417,7 @@ We collect [instance details for a variety of databases and database drivers](/d - [MySQL](http://www.mysql.com/) + [MySQL 2](http://www.mysql.com/) @@ -602,9 +602,120 @@ In order to support [APM logs in context](/docs/apm/new-relic-apm/getting-starte > [Message queue instrumentation](/docs/agents/nodejs-agent/troubleshooting/troubleshoot-message-consumers) is only available with the [New Relic Node.js agent v2 or higher](/docs/release-notes/agent-release-notes/nodejs-release-notes). Currently supported message queue instrumentation: - * [amqplib](https://www.npmjs.com/package/amqplib). - * [Amazon SQS](https://www.npmjs.com/package/aws-sdk) - both versions 2 and 3 of AWS SDK. - * [Amazon SNS](https://www.npmjs.com/package/aws-sdk) - both versions 2 and 3 of AWS SDK. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ Message queue + + `npm` module name + + Minimum module version + + Minimum agent version +
+ [Amqplib](https://www.npmjs.com/package/amqplib) + + `amqplib` + + 0.5.0 + + 2.0.0 +
+ [Amazon SQS - Amazon SDK V2](https://www.npmjs.com/package/aws-sdk) + + `@aws-sdk/client-sqs + + @aws-sdk 2.2.48 + + 6.2.0 +
+ [Amazon SQS - Amazon SDK V3](https://github.com/aws/aws-sdk-js-v3) + + `@aws-sdk/client-sqs + + @aws-sdk v3.0.0 + + 8.7.1 +
+ [Amazon SNS - Amazon SDK V2](https://www.npmjs.com/package/aws-sdk) + + `@aws-sdk/client-sqs + + @aws-sdk 2.2.48 + + 6.2.0 +
+ [Amazon SNS - Amazon SDK V3](https://github.com/aws/aws-sdk-js-v3) + + `@aws-sdk/client-sqs + + @aws-sdk v3.0.0 + + 8.7.1 +
For other message queue libraries, use [custom instrumentation](/docs/agents/nodejs-agent/supported-features/nodejs-custom-instrumentation#message-client). @@ -695,8 +806,12 @@ For other message queue libraries, use [custom instrumentation](/docs/agents/nod Framework + + `npm` module name + + - Supported versions + Minimum module version @@ -715,12 +830,13 @@ For other message queue libraries, use [custom instrumentation](/docs/agents/nod [Express](https://www.npmjs.com/package/express) + `express` + 4.6.0+ - - + 2.6.0 @@ -731,12 +847,14 @@ For other message queue libraries, use [custom instrumentation](/docs/agents/nod [Restify](https://www.npmjs.com/package/restify) - - + `restify` + 5.0.0 + 2.6.0 + @@ -747,12 +865,15 @@ For other message queue libraries, use [custom instrumentation](/docs/agents/nod + `connect` + 2.0.0 + 2.6.0 @@ -761,6 +882,10 @@ For other message queue libraries, use [custom instrumentation](/docs/agents/nod [Hapi](https://www.npmjs.com/package/@hapi/hapi) + + `@hapi/hapi` + + 20.0.0+ @@ -779,13 +904,14 @@ For other message queue libraries, use [custom instrumentation](/docs/agents/nod [Koa](https://www.npmjs.com/package/koa) - - 2.0.0+ - + `koa` + 2.0.0 + 3.2.0 + [External module](https://github.com/newrelic/node-newrelic-koa) loaded with the agent @@ -796,8 +922,10 @@ For other message queue libraries, use [custom instrumentation](/docs/agents/nod [Fastify](https://www.npmjs.com/package/fastify) + `fastify` + - 2+ + 2.0.0 @@ -813,8 +941,10 @@ For other message queue libraries, use [custom instrumentation](/docs/agents/nod [Nest.js](https://nestjs.com/) + `@nestjs/core` + - 8.0.0+ + 8.0.0 @@ -831,6 +961,8 @@ For other message queue libraries, use [custom instrumentation](/docs/agents/nod [Next.js](https://www.npmjs.com/package/next) + `next` + 12.0.9 - 13.3.0 From 9516edb3e86b52d80e193b66eef03412cddfc274 Mon Sep 17 00:00:00 2001 From: Svetlana Brennan <50715937+svetlanabrennan@users.noreply.github.com> Date: Thu, 21 Mar 2024 09:36:30 -0500 Subject: [PATCH 09/24] fix typo --- .../getting-started/compatibility-requirements-nodejs-agent.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx b/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx index 454b9f3b4e8..29f41b5a28d 100644 --- a/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx +++ b/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx @@ -247,7 +247,7 @@ The Node.js agent monitors the performance of Node.js application calls to these [MongoDB](https://www.npmjs.com/package/mongodb) `mongodb` 2.1.0 - 1.32.0< + 1.32.0 From efc4c9264560fa14349cd571143926a0f423e83a Mon Sep 17 00:00:00 2001 From: Svetlana Brennan <50715937+svetlanabrennan@users.noreply.github.com> Date: Thu, 21 Mar 2024 11:54:30 -0500 Subject: [PATCH 10/24] fix mdx errors --- ...ompatibility-requirements-nodejs-agent.mdx | 108 ++++-------------- 1 file changed, 22 insertions(+), 86 deletions(-) diff --git a/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx b/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx index 29f41b5a28d..987d0b4e4cf 100644 --- a/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx +++ b/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx @@ -602,118 +602,54 @@ In order to support [APM logs in context](/docs/apm/new-relic-apm/getting-starte > [Message queue instrumentation](/docs/agents/nodejs-agent/troubleshooting/troubleshoot-message-consumers) is only available with the [New Relic Node.js agent v2 or higher](/docs/release-notes/agent-release-notes/nodejs-release-notes). Currently supported message queue instrumentation: - +
- - - - - - - - - - - + + + + - - - - - - - - + + + + - - - - - - - - + + + + - - - - - - - - - + + + + + - - - - - - - - + + + + -
Message queue `npm` module name Minimum module version Minimum agent version
- [Amqplib](https://www.npmjs.com/package/amqplib) - - `amqplib` - - 0.5.0 - - 2.0.0 - [Amqplib](https://www.npmjs.com/package/amqplib)`amqplib`0.5.02.0.0
- [Amazon SQS - Amazon SDK V2](https://www.npmjs.com/package/aws-sdk) - - `@aws-sdk/client-sqs - - @aws-sdk 2.2.48 - - 6.2.0 - [Amazon SQS - Amazon SDK V2](https://www.npmjs.com/package/aws-sdk)`@aws-sdk/client-sqs`@aws-sdk 2.2.486.2.0
- [Amazon SQS - Amazon SDK V3](https://github.com/aws/aws-sdk-js-v3) - - `@aws-sdk/client-sqs - - @aws-sdk v3.0.0 - - 8.7.1 - [Amazon SQS - Amazon SDK V3](https://github.com/aws/aws-sdk-js-v3)`@aws-sdk/client-sqs`@aws-sdk v3.0.08.7.1
- [Amazon SNS - Amazon SDK V2](https://www.npmjs.com/package/aws-sdk) - - `@aws-sdk/client-sqs - - @aws-sdk 2.2.48 - - 6.2.0 -
[Amazon SNS - Amazon SDK V2](https://www.npmjs.com/package/aws-sdk)`@aws-sdk/client-sqs`@aws-sdk 2.2.486.2.0
- [Amazon SNS - Amazon SDK V3](https://github.com/aws/aws-sdk-js-v3) - - `@aws-sdk/client-sqs - - @aws-sdk v3.0.0 - - 8.7.1 - [Amazon SNS - Amazon SDK V3](https://github.com/aws/aws-sdk-js-v3)`@aws-sdk/client-sqs`@aws-sdk v3.0.08.7.1
From 1189d1828292e851cc97eb1b870df44db2276a3a Mon Sep 17 00:00:00 2001 From: jeff-colucci <116673918+jeff-colucci@users.noreply.github.com> Date: Fri, 22 Mar 2024 11:16:56 -0500 Subject: [PATCH 11/24] fix(NRQL): clarifying the example for SQJ --- .../docs/nrql/using-nrql/subquery-joins.mdx | 48 +++++++++---------- 1 file changed, 24 insertions(+), 24 deletions(-) diff --git a/src/content/docs/nrql/using-nrql/subquery-joins.mdx b/src/content/docs/nrql/using-nrql/subquery-joins.mdx index 9cd2b2ea050..a96dddd493a 100644 --- a/src/content/docs/nrql/using-nrql/subquery-joins.mdx +++ b/src/content/docs/nrql/using-nrql/subquery-joins.mdx @@ -26,30 +26,6 @@ Much of the data stored within New Relic relates to other data: `Transaction` an A [subquery](/docs/query-your-data/nrql-new-relic-query-language/get-started/subqueries-in-nrql) is a query that is nested inside another query. With subquery joins, you can combine the result of a subquery with the result of its outer query based on a key, allowing for analysis and enrichment across datasets. -This example joins infrastructure data with transaction data: - -Datasets Related by Container ID - -The image above contains two datasets: the average CPU percentage of infrastructure containers (`ProcessSample`) and the average duration of app transactions by container. Often, data from different sources is correlated. In this case, you can determine if a container's higher CPU usage is causing slower transactions by using the following subquery join: - -```sql -FROM Transaction - JOIN (FROM ProcessSample SELECT average(cpuPercent) AS cpu - FACET containerId LIMIT MAX) ON containerId -SELECT average(duration)/latest(cpu) FACET containerId, containerName -``` -Datasets Joined by Container ID - -With this query, you can see the containers that have a higher average transaction duration given their CPU usage, and investigate outliers to see if there is a bug to fix or optimizations to be made. - ## How to write a subquery join A subquery join requires three components: two datasets and a primary key to link the two together. @@ -80,6 +56,30 @@ FROM JavaScriptError SELECT count(*) FACET city, currentUrl, session, errorClass ``` +The image below contains two datasets: the average CPU percentage of infrastructure containers (`ProcessSample`) and the average duration of app transactions by container. + +Datasets Related by Container ID + + Often, data from different sources is correlated. In this case, you can determine if a container's higher CPU usage is causing slower transactions by using the following subquery join: + +```sql +FROM Transaction + JOIN (FROM ProcessSample SELECT average(cpuPercent) AS cpu + FACET containerId LIMIT MAX) ON containerId +SELECT average(duration)/latest(cpu) FACET containerId, containerName +``` +Datasets Joined by Container ID + +With this query, you can see the containers that have a higher average transaction duration given their CPU usage, and investigate outliers to see if there is a bug to fix or optimizations to be made. + ## Subquery join limitations [#subquery-join-limitations] Subquery joins have the following limitations: From 973fb3ca0eb09bd2795274900f976224c478c66e Mon Sep 17 00:00:00 2001 From: jcol <116673918+jeff-colucci@users.noreply.github.com> Date: Fri, 22 Mar 2024 12:05:24 -0500 Subject: [PATCH 12/24] Update subquery-joins.mdx slight copy positioning fix --- src/content/docs/nrql/using-nrql/subquery-joins.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/nrql/using-nrql/subquery-joins.mdx b/src/content/docs/nrql/using-nrql/subquery-joins.mdx index a96dddd493a..8c3dc111ea7 100644 --- a/src/content/docs/nrql/using-nrql/subquery-joins.mdx +++ b/src/content/docs/nrql/using-nrql/subquery-joins.mdx @@ -24,10 +24,10 @@ import nrqlJoinTuturialCalculationsJoined from 'images/nrql-join-tutorial-calcul Much of the data stored within New Relic relates to other data: `Transaction` and `TransactionError`, `PageView` and `PageAction`, `Log` and infrastructure events, and more. You can perform analysis and calculate correlations between these events using subquery joins. -A [subquery](/docs/query-your-data/nrql-new-relic-query-language/get-started/subqueries-in-nrql) is a query that is nested inside another query. With subquery joins, you can combine the result of a subquery with the result of its outer query based on a key, allowing for analysis and enrichment across datasets. - ## How to write a subquery join +A [subquery](/docs/query-your-data/nrql-new-relic-query-language/get-started/subqueries-in-nrql) is a query that is nested inside another query. With subquery joins, you can combine the result of a subquery with the result of its outer query based on a key, allowing for analysis and enrichment across datasets. + A subquery join requires three components: two datasets and a primary key to link the two together. ```sql From 58d7dee243a773877b2741c533d6abf1ec3bb200 Mon Sep 17 00:00:00 2001 From: Svetlana Brennan <50715937+svetlanabrennan@users.noreply.github.com> Date: Wed, 27 Mar 2024 13:33:38 -0500 Subject: [PATCH 13/24] fix typos --- .../compatibility-requirements-nodejs-agent.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx b/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx index 987d0b4e4cf..05f57aa40fa 100644 --- a/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx +++ b/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx @@ -640,13 +640,13 @@ In order to support [APM logs in context](/docs/apm/new-relic-apm/getting-starte [Amazon SNS - Amazon SDK V2](https://www.npmjs.com/package/aws-sdk) - `@aws-sdk/client-sqs` + `@aws-sdk/client-sns` @aws-sdk 2.2.48 6.2.0 [Amazon SNS - Amazon SDK V3](https://github.com/aws/aws-sdk-js-v3) - `@aws-sdk/client-sqs` + `@aws-sdk/client-sns` @aws-sdk v3.0.0 8.7.1 @@ -702,7 +702,7 @@ For other message queue libraries, use [custom instrumentation](/docs/agents/nod - [generic-pool](https://www.npmjs.com/package/generic-pool) + [Generic Pool](https://www.npmjs.com/package/generic-pool) From adc63ff0645eebba0f0a6feaf079e5a715ff8a02 Mon Sep 17 00:00:00 2001 From: Svetlana Brennan <50715937+svetlanabrennan@users.noreply.github.com> Date: Wed, 27 Mar 2024 15:08:29 -0500 Subject: [PATCH 14/24] add missing row and remove plus sign --- .../compatibility-requirements-nodejs-agent.mdx | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx b/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx index 05f57aa40fa..245edb15f93 100644 --- a/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx +++ b/src/content/docs/apm/agents/nodejs-agent/getting-started/compatibility-requirements-nodejs-agent.mdx @@ -769,7 +769,7 @@ For other message queue libraries, use [custom instrumentation](/docs/agents/nod `express` - 4.6.0+ + 4.6.0 2.6.0 @@ -811,6 +811,9 @@ For other message queue libraries, use [custom instrumentation](/docs/agents/nod 2.6.0 + + + @@ -823,7 +826,7 @@ For other message queue libraries, use [custom instrumentation](/docs/agents/nod - 20.0.0+ + 20.0.0 From 43ba8e65c9cc1665eb4b72c8e386310187c7cc13 Mon Sep 17 00:00:00 2001 From: Brian Goleno Date: Fri, 29 Mar 2024 11:13:17 -0700 Subject: [PATCH 15/24] Update custom-anomalies.mdx I removed the references to "Custom Anomaly Detection" and standardized on the simpler "Anomaly Detection" form as there is now only one type of Anomaly Detection. --- .../anomaly-detection/custom-anomalies.mdx | 27 ++++++++++--------- 1 file changed, 14 insertions(+), 13 deletions(-) diff --git a/src/content/docs/alerts-applied-intelligence/applied-intelligence/anomaly-detection/custom-anomalies.mdx b/src/content/docs/alerts-applied-intelligence/applied-intelligence/anomaly-detection/custom-anomalies.mdx index 7833d83bddc..d5015ebca99 100644 --- a/src/content/docs/alerts-applied-intelligence/applied-intelligence/anomaly-detection/custom-anomalies.mdx +++ b/src/content/docs/alerts-applied-intelligence/applied-intelligence/anomaly-detection/custom-anomalies.mdx @@ -1,10 +1,11 @@ --- -title: Custom anomaly detection +title: Anomaly detection tags: - Alerts and applied intelligence - Applied intelligence - - Proactive detection -metaDescription: Learn how custom anomaly detection in New Relic notifies you of unusual app behavior. + - Anomaly detection + - Alerts +metaDescription: Learn how anomaly detection in New Relic notifies you of unusual app behavior. redirects: - /docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/other-condition-types/create-anomaly-alert-conditions - /docs/alerts/new-relic-alerts/defining-conditions/create-anomaly-alert-conditions @@ -24,24 +25,24 @@ import alertsFacetedAnomaliesTwo from 'images/alerts_screenshot-full_faceted-ano import alertsAnomaliesSetUpperandLowerRanges from 'images/alerts_screenshot-full_anomalies-set-upper-and-lower-ranges.webp' -Custom anomalies allow your team the most versatility when detecting unusual behavior in your system. Not only are they flexible and dynamic, custom anomalies provide your team with the ability to alert on any entity or signal and to adjust and optimize your thresholds. Custom anomalies are built using the same advanced tuning settings as static alerting so you can ensure your team sees only incidents that are important to you. +Anomaly detection allows your team the most versatility when detecting unusual behavior in your system. Anomaly detection provides your team with the ability to alert on any entity or signal and to adjust and optimize your sensitivity thresholds. Anomaly detection uses the same streaming alerting pipeline as static threshold alerts, and threfore shares the same advanced tuning settings. This ensures that the stream processing is aligned to your telemetry signal's characteristics to reduce false alerting. -You can also enrich your custom anomaly detection configuration with additional metadata to provide further context and add custom incident descriptions that can provide additional instructions to your on-call engineers. +You can also enrich your anomaly detection configuration with additional metadata to provide further context and add custom incident descriptions that can provide additional instructions to your on-call engineers. -## Configure custom anomaly thresholds [#configure-custom-anomalies] +## Configure anomaly sensitivity thresholds [#configure-custom-anomalies] -You can create custom anomalies thresholds from an [alert condition](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/create-nrql-alert-conditions/). Here are some tips for setting anomaly thresholds: +You can create anomaly sensitivity thresholds from an [alert condition](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/create-nrql-alert-conditions/). Here are some tips for setting anomaly thresholds: * Set the [anomaly direction](#anomaly-direction) to monitor incidents that happen either above or below the anomaly. -* Use the slider bar to adjust the **Critical** threshold sensitivity, represented in the preview chart by the light gray area around the anomaly. The tighter the band around the anomaly, the more sensitive it is and the more incidents it will generate. +* Use the slider bar to adjust the **Critical** sensitivity threshold, represented in the preview chart by the light gray area around the signal. The tighter the band around the signal, the more sensitive it is and the more incidents it will generate. * You can create a [**Warning** threshold](/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/advanced-techniques/set-thresholds-alert-condition/#threshold-levels) (the darker gray area around the anomaly). -Follow these steps to create your custom anomaly: +Follow these steps to create an anomaly detection alert condition: 1. Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts & AI > Alert Conditions**. -2. Click **+ New alert condition > Use guided mode**. +2. Click **+ New alert condition > Use guided mode** (or the more advanced Query mode). 3. Go through the guided steps until you get to **Set thresholds**. @@ -54,7 +55,7 @@ Follow these steps to create your custom anomaly: src={alertsTryAnomalyThresholds} /> -5. Configure the settings for one or more thresholds. Anomaly detection makes a prediction on what the next data point will be based on prior activity. The threshold value for custom anomaly detection is the number of standard deviations your signal value is away from the value that was predicted. +5. Configure the settings for one or more thresholds. Anomaly detection makes a prediction on what the next data point will be based on prior activity. The threshold value for anomaly detection controls how sensitive the alert condition will be for tolerating how far off the actual value is from the predicted value. We track the standard deviation between the predicted value and the actual value for the prior 7 days of data. The threshold is the number of standard deviations your signal value is away from the value that was predicted. To configure the threshold, you'll need to: @@ -97,7 +98,7 @@ Here are examples of how large fluctuations in your data would be treated under The algorithm for calculating the prediction is mathematically complex. Here are some of the major rules governing its predictive abilities: -* **Age of data** On initial creation, the prediction is calculated using between 1 to 4 weeks of data, depending on data availability and prediction type. After its creation, the algorithm takes into account ongoing data fluctuations over a long time period, although greater weight is given to more recent data. For data that has only existed for a short time, the predicted value will likely fluctuate a good deal and not be very accurate. This is because there isn't enough data to determine its usual values and behavior. The more history the data has, the more accurate the prediction and thresholds will become. -* **Consistency of data** For metric values that remain in a consistent range or that trend slowly and steadily, their more predictable behavior means that their thresholds will become tighter around the prediction. Data that is more varied and unpredictable will have looser (wider) thresholds. +* **Age of data** On initial creation, the prediction is calculated using between 1 to 4 weeks of data, depending on data availability and prediction type. Currently, queries that use the FACET clause are not trained on stored data. After its creation, the algorithm takes into account ongoing data fluctuations over a long time period, although greater weight is given to more recent data. For data that has only existed for a short time, the predicted value will likely fluctuate a good deal and not be very accurate. This is because there isn't enough data to determine its usual values and behavior. The more history the data has, the more accurate the prediction will become. +* **Consistency of data** For metric values that remain in a consistent range or that trend slowly and steadily, their more predictable behavior means that their sensitivity thresholds will become tighter around the prediction. Data that is more varied and unpredictable will have looser (wider) sensitivity thresholds. * **Regular fluctuations** For shorter-than-one-week cyclical fluctuations (such as weekly Wednesday 1pm deployments or nightly reports), the prediction algorithm looks for these cyclical fluctuations and attempts to adjust to them. From c547a78ab79a8372b79a2aafae2a23f25de6027d Mon Sep 17 00:00:00 2001 From: jcol <116673918+jeff-colucci@users.noreply.github.com> Date: Fri, 29 Mar 2024 14:23:23 -0500 Subject: [PATCH 16/24] Update custom-anomalies.mdx style fixes --- .../anomaly-detection/custom-anomalies.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/content/docs/alerts-applied-intelligence/applied-intelligence/anomaly-detection/custom-anomalies.mdx b/src/content/docs/alerts-applied-intelligence/applied-intelligence/anomaly-detection/custom-anomalies.mdx index d5015ebca99..9583a6e0214 100644 --- a/src/content/docs/alerts-applied-intelligence/applied-intelligence/anomaly-detection/custom-anomalies.mdx +++ b/src/content/docs/alerts-applied-intelligence/applied-intelligence/anomaly-detection/custom-anomalies.mdx @@ -25,7 +25,7 @@ import alertsFacetedAnomaliesTwo from 'images/alerts_screenshot-full_faceted-ano import alertsAnomaliesSetUpperandLowerRanges from 'images/alerts_screenshot-full_anomalies-set-upper-and-lower-ranges.webp' -Anomaly detection allows your team the most versatility when detecting unusual behavior in your system. Anomaly detection provides your team with the ability to alert on any entity or signal and to adjust and optimize your sensitivity thresholds. Anomaly detection uses the same streaming alerting pipeline as static threshold alerts, and threfore shares the same advanced tuning settings. This ensures that the stream processing is aligned to your telemetry signal's characteristics to reduce false alerting. +Anomaly detection allows your team the most versatility when detecting unusual behavior in your system. Anomaly detection gives your team the ability to alert on any entity or signal and to adjust and optimize your sensitivity thresholds. Anomaly detection uses the same streaming-alerting pipeline as static threshold alerts and shares the same advanced tuning settings. This ensures that the stream processing is aligned to your telemetry signal's characteristics to reduce false alerting. You can also enrich your anomaly detection configuration with additional metadata to provide further context and add custom incident descriptions that can provide additional instructions to your on-call engineers. @@ -55,7 +55,7 @@ Follow these steps to create an anomaly detection alert condition: src={alertsTryAnomalyThresholds} /> -5. Configure the settings for one or more thresholds. Anomaly detection makes a prediction on what the next data point will be based on prior activity. The threshold value for anomaly detection controls how sensitive the alert condition will be for tolerating how far off the actual value is from the predicted value. We track the standard deviation between the predicted value and the actual value for the prior 7 days of data. The threshold is the number of standard deviations your signal value is away from the value that was predicted. +5. Configure the settings for one or more thresholds. Anomaly detection makes a prediction on what the next data point will be based on prior activity. The threshold value for anomaly detection controls the sensitivity of the alert condition for tolerating how far off the actual value is from the predicted value. The threshold is the number of standard deviations your signal value is away from the value that was predicted. We track the standard deviation between the predicted value and the actual value for the prior 7 days of data. To configure the threshold, you'll need to: @@ -98,7 +98,7 @@ Here are examples of how large fluctuations in your data would be treated under The algorithm for calculating the prediction is mathematically complex. Here are some of the major rules governing its predictive abilities: -* **Age of data** On initial creation, the prediction is calculated using between 1 to 4 weeks of data, depending on data availability and prediction type. Currently, queries that use the FACET clause are not trained on stored data. After its creation, the algorithm takes into account ongoing data fluctuations over a long time period, although greater weight is given to more recent data. For data that has only existed for a short time, the predicted value will likely fluctuate a good deal and not be very accurate. This is because there isn't enough data to determine its usual values and behavior. The more history the data has, the more accurate the prediction will become. +* **Age of data** On initial creation, the prediction is calculated using between 1 to 4 weeks of data, depending on data availability and prediction type. Currently, queries that use the `FACET` clause aren't trained on stored data. After its creation, the algorithm takes into account ongoing data fluctuations over a long time period, although greater weight is given to more recent data. For data that has only existed for a short time, the predicted value will likely fluctuate a good deal and not be very accurate. This is because there isn't enough data to determine its usual values and behavior. The more history the data has, the more accurate the prediction will become. * **Consistency of data** For metric values that remain in a consistent range or that trend slowly and steadily, their more predictable behavior means that their sensitivity thresholds will become tighter around the prediction. Data that is more varied and unpredictable will have looser (wider) sensitivity thresholds. * **Regular fluctuations** For shorter-than-one-week cyclical fluctuations (such as weekly Wednesday 1pm deployments or nightly reports), the prediction algorithm looks for these cyclical fluctuations and attempts to adjust to them. From a14a15c2fecf74e743eaf2f350338bedbb8b06c0 Mon Sep 17 00:00:00 2001 From: Brian Goleno Date: Fri, 29 Mar 2024 12:35:53 -0700 Subject: [PATCH 17/24] Update alerts-ai-overview-page.mdx removed references to anomalies feed. That is being removed as part of the EOL for Proactive Detection --- .../get-started/alerts-ai-overview-page.mdx | 87 +------------------ 1 file changed, 2 insertions(+), 85 deletions(-) diff --git a/src/content/docs/alerts-applied-intelligence/new-relic-alerts/get-started/alerts-ai-overview-page.mdx b/src/content/docs/alerts-applied-intelligence/new-relic-alerts/get-started/alerts-ai-overview-page.mdx index 427080d9952..45109234a9f 100644 --- a/src/content/docs/alerts-applied-intelligence/new-relic-alerts/get-started/alerts-ai-overview-page.mdx +++ b/src/content/docs/alerts-applied-intelligence/new-relic-alerts/get-started/alerts-ai-overview-page.mdx @@ -11,11 +11,11 @@ redirects: freshnessValidatedDate: never --- -On the **Overview** page, you'll find a consolidated view of your current alerts incidents. The **Issues & activity** page has views of your active issues, recent incidents, and anomalies. +On the **Overview** page, you'll find a consolidated view of your current alerts incidents. The **Issues & activity** page has views of your active issues and recent incidents. ## Why it matters [#why] -The **Overview** and **Issues & activity** pages provide analytics on how your system is (or isn't) performing. You can quickly switch between the [**Overview**](#summary), [**Issues**](#issues), [**Incidents**](#incidents), and [**Anomalies**](#anomalies) to scan for critical problems affecting your systems. +The **Overview** and **Issues & activity** pages provide analytics on how your system is (or isn't) performing. You can quickly switch between the [**Overview**](#summary), [**Issues**](#issues) and [**Incidents**](#incidents) to scan for critical problems affecting your systems. ## Overview page [#summary] @@ -356,86 +356,3 @@ Click an incident's row to see the incident's details. -## Anomalies - -On the **Issues & activity** page, anomalies are outliers in your system's performance and operation that might be the sign of a problem. See every anomaly in one place. You can filter your anomalies by anomaly state, entity, configuration and configuration type. - -By default, this page shows a list of all your recent anomalies in the selected account. Select an anomaly to view a detailed analysis and more context. - -### Anomalies feed columns - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Column name - - Explanation -
- State of anomaly - - Values: open or closed. -
- Anomaly category - - Values: error rate, web throughput, non-web throughput. -
- (no column name) - - A graph to illustrate the anomaly. -
- Start time - - How long ago the anomaly started. -
- Duration - - How long the anomaly lasted. -
- Entity - - Name of the entity. -
From e99c1211b39b8e90bf66de41bbb4b43059968bd8 Mon Sep 17 00:00:00 2001 From: Brian Goleno Date: Fri, 29 Mar 2024 12:40:59 -0700 Subject: [PATCH 18/24] Update product-based-pricing-usage-new-relic-platform-pricing-usage-plan.mdx removed outdated reference to proactive detection --- ...-new-relic-platform-pricing-usage-plan.mdx | 19 +------------------ 1 file changed, 1 insertion(+), 18 deletions(-) diff --git a/src/content/docs/licenses/license-information/usage-plans/product-based-pricing-usage-new-relic-platform-pricing-usage-plan.mdx b/src/content/docs/licenses/license-information/usage-plans/product-based-pricing-usage-new-relic-platform-pricing-usage-plan.mdx index 83887fef170..b5213d7592f 100644 --- a/src/content/docs/licenses/license-information/usage-plans/product-based-pricing-usage-new-relic-platform-pricing-usage-plan.mdx +++ b/src/content/docs/licenses/license-information/usage-plans/product-based-pricing-usage-new-relic-platform-pricing-usage-plan.mdx @@ -318,24 +318,7 @@ The following Eligible Services with New Relic are products that are referenced - - - New Relic applied intelligence Proactive Detection Annual - - - - 1,000,000,000 - - - - App Transactions - - - - $250 - - - + \* Customer may utilize either New Relic APM Pro Annual or New Relic APM Pro CUs Annual, but not both. Customer will be provisioned New Relic APM Pro CUs Annual by default, unless otherwise stated in the relevant Order Form. From 86347160f81a796836bfc8ac113968e59e8790cf Mon Sep 17 00:00:00 2001 From: Rob Siebens Date: Fri, 29 Mar 2024 12:45:26 -0700 Subject: [PATCH 19/24] fix(on-host): Clarify escape characters --- .../host-integrations-standard-configuration-format.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/specifications/host-integrations-standard-configuration-format.mdx b/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/specifications/host-integrations-standard-configuration-format.mdx index 90b023089b7..d525284f531 100644 --- a/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/specifications/host-integrations-standard-configuration-format.mdx +++ b/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/specifications/host-integrations-standard-configuration-format.mdx @@ -264,12 +264,12 @@ integrations: exec: /usr/bin/python /opt/integrations/my-script.py --host=127.0.0.1 ``` - If any of the path/arguments have spaces that are part of a single element, you can use a YAML array notation: + If any of the paths or arguments have spaces that are part of a single element, you can use a YAML array notation (use quotation marks to escape backslashes): ``` - name: my-integration exec: - - C:\Program Files\My Integration\integration.exe + - '"C:\Program Files\My Integration\integration.exe"' - --host - 127.0.0.1 - --port From 62a4b7f33371363a4e52d914aeb979c7ef93bd14 Mon Sep 17 00:00:00 2001 From: jeff-colucci <116673918+jeff-colucci@users.noreply.github.com> Date: Fri, 29 Mar 2024 15:05:27 -0500 Subject: [PATCH 20/24] fix(OMA): fixing missing redirect --- .../intro-to-optimal-telemetry.mdx | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/content/docs/tutorial-optimize-telemetry/intro-to-optimal-telemetry.mdx b/src/content/docs/tutorial-optimize-telemetry/intro-to-optimal-telemetry.mdx index 665ddcdf017..a30960c59ca 100644 --- a/src/content/docs/tutorial-optimize-telemetry/intro-to-optimal-telemetry.mdx +++ b/src/content/docs/tutorial-optimize-telemetry/intro-to-optimal-telemetry.mdx @@ -7,8 +7,9 @@ redirects: - /docs/telemetry-data-platform/get-started/manage-data/data-governance - /telemetry-data-platform/get-started/manage-data/data-governance - /docs/new-relic-solutions/observability-maturity/operational-efficiency/dg-intro - - /docs/new-relic-solutions/observability-maturity/operational-efficiency/data-governance-roles-practices-guide/ - - /docs/new-relic-solutions/observability-maturity/operational-efficiency/intro-data-governance/ + - /docs/new-relic-solutions/observability-maturity/operational-efficiency/data-governance-roles-practices-guide + - /docs/new-relic-solutions/observability-maturity/operational-efficiency/intro-data-governance + - /docs/new-relic-solutions/observability-maturity/operational-efficiency/data-governance-optimize-ingest-guide freshnessValidatedDate: 2023-07-26 --- From 15f8b2bb8e7d083477031e4dfde466174321984a Mon Sep 17 00:00:00 2001 From: Rob Siebens Date: Fri, 29 Mar 2024 13:13:46 -0700 Subject: [PATCH 21/24] fix(on-host): Add "Windows" to clarify escape usage --- .../host-integrations-standard-configuration-format.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/specifications/host-integrations-standard-configuration-format.mdx b/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/specifications/host-integrations-standard-configuration-format.mdx index d525284f531..4d5a7ab77ba 100644 --- a/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/specifications/host-integrations-standard-configuration-format.mdx +++ b/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/specifications/host-integrations-standard-configuration-format.mdx @@ -264,7 +264,7 @@ integrations: exec: /usr/bin/python /opt/integrations/my-script.py --host=127.0.0.1 ``` - If any of the paths or arguments have spaces that are part of a single element, you can use a YAML array notation (use quotation marks to escape backslashes): + If any of the paths or arguments have spaces that are part of a single element, you can use a YAML array notation (use quotation marks to escape Windows backslashes): ``` - name: my-integration From cdaa5b5593c2e01e82a1c1dfd552d1f04dc8dcb7 Mon Sep 17 00:00:00 2001 From: Rob Siebens Date: Fri, 29 Mar 2024 13:22:11 -0700 Subject: [PATCH 22/24] fix(on-host): Second try at escape language --- .../host-integrations-standard-configuration-format.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/specifications/host-integrations-standard-configuration-format.mdx b/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/specifications/host-integrations-standard-configuration-format.mdx index 4d5a7ab77ba..def559cc7fd 100644 --- a/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/specifications/host-integrations-standard-configuration-format.mdx +++ b/src/content/docs/infrastructure/host-integrations/infrastructure-integrations-sdk/specifications/host-integrations-standard-configuration-format.mdx @@ -264,7 +264,7 @@ integrations: exec: /usr/bin/python /opt/integrations/my-script.py --host=127.0.0.1 ``` - If any of the paths or arguments have spaces that are part of a single element, you can use a YAML array notation (use quotation marks to escape Windows backslashes): + If any of the paths or arguments have spaces that are part of a single element, you can use a YAML array notation. For Windows, be sure to escape backslashes with quotation marks like this: ``` - name: my-integration From 1724cb42f6adad78b3b457ed53b0131e3c6998c4 Mon Sep 17 00:00:00 2001 From: Hannah Ramadan <76922290+hannahramadan@users.noreply.github.com> Date: Fri, 29 Mar 2024 14:19:37 -0700 Subject: [PATCH 23/24] Update ruby-ai-monitoring.mdx --- .../docs/apm/agents/ruby-agent/api-guides/ruby-ai-monitoring.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/src/content/docs/apm/agents/ruby-agent/api-guides/ruby-ai-monitoring.mdx b/src/content/docs/apm/agents/ruby-agent/api-guides/ruby-ai-monitoring.mdx index 63f58e9fe0e..824eca26a82 100644 --- a/src/content/docs/apm/agents/ruby-agent/api-guides/ruby-ai-monitoring.mdx +++ b/src/content/docs/apm/agents/ruby-agent/api-guides/ruby-ai-monitoring.mdx @@ -40,6 +40,7 @@ The following example code demonstrates setting a callback that calculates token end NewRelic::Agent.set_llm_token_count_callback(token_count_callback) +``` ## User feedback [#user-feedback] From de6cd6592fbb009dd016eb5c0c369ec0cb4f366d Mon Sep 17 00:00:00 2001 From: alexa <81787716+akristen@users.noreply.github.com> Date: Fri, 29 Mar 2024 16:34:53 -0500 Subject: [PATCH 24/24] fix ruby api doc link, add redirect, rename doc in the left nav --- .../api-guides/{ruby-ai-monitoring.mdx => ai-monitoring.mdx} | 1 + src/nav/apm.yml | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) rename src/content/docs/apm/agents/ruby-agent/api-guides/{ruby-ai-monitoring.mdx => ai-monitoring.mdx} (98%) diff --git a/src/content/docs/apm/agents/ruby-agent/api-guides/ruby-ai-monitoring.mdx b/src/content/docs/apm/agents/ruby-agent/api-guides/ai-monitoring.mdx similarity index 98% rename from src/content/docs/apm/agents/ruby-agent/api-guides/ruby-ai-monitoring.mdx rename to src/content/docs/apm/agents/ruby-agent/api-guides/ai-monitoring.mdx index 824eca26a82..ea6c09e0abe 100644 --- a/src/content/docs/apm/agents/ruby-agent/api-guides/ruby-ai-monitoring.mdx +++ b/src/content/docs/apm/agents/ruby-agent/api-guides/ai-monitoring.mdx @@ -8,6 +8,7 @@ metaDescription: 'For information about customizing New Relic''s Ruby agent for freshnessValidatedDate: never redirects: - /docs/apm/agents/ruby-agent/api-guides/ruby-ai-monitoring-apis + - /docs/apm/agents/ruby-agent/api-guides/ruby-ai-monitoring --- When you've instrumented your app for AI monitoring, the New Relic Ruby agent automatically collects many AI metrics, but also provides APIs for collecting information on token count and user feedback. diff --git a/src/nav/apm.yml b/src/nav/apm.yml index 07839c0d16a..5358f1f7c69 100644 --- a/src/nav/apm.yml +++ b/src/nav/apm.yml @@ -1100,7 +1100,7 @@ pages: pages: - title: API guide path: /docs/apm/agents/ruby-agent/api-guides/guide-using-ruby-agent-api - - title: Ruby agent AI monitoring APIs + - title: AI monitoring for Ruby path: /docs/apm/agents/ruby-agent/api-guides/ai-monitoring - title: Ruby custom instrumentation path: /docs/apm/agents/ruby-agent/api-guides/ruby-custom-instrumentation