From 2e54d613ce633ecafd1df9a1d51d8f332f32d513 Mon Sep 17 00:00:00 2001 From: Marty Tippin <120425148+tippmar-nr@users.noreply.github.com> Date: Thu, 29 Aug 2024 14:01:54 -0500 Subject: [PATCH 001/173] docs(dotnet): Update Oracle compatibility --- ...nt-compatibility-requirements-net-core.mdx | 22 +++++++++++++++++++ ...mpatibility-requirements-net-framework.mdx | 7 +++++- 2 files changed, 28 insertions(+), 1 deletion(-) diff --git a/src/content/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements-net-core.mdx b/src/content/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements-net-core.mdx index 811c78547c0..2e00fc6b8fa 100644 --- a/src/content/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements-net-core.mdx +++ b/src/content/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements-net-core.mdx @@ -435,6 +435,28 @@ If your application is hosted in ASP.NET Core, the agent automatically creates a + + + Oracle + + + + + + + + Use [Oracle.ManagedDataAccess.Core](https://www.nuget.org/packages/Oracle.ManagedDataAccess.Core/) + + * Minimum supported version: 23.4.0 + * Latest verified compatible version: 23.5.1 + + Older versions of `Oracle.ManagedDataAccess.Core` may be instrumented, but have not been tested and are not supported. + + + PostgreSQL diff --git a/src/content/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements-net-framework.mdx b/src/content/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements-net-framework.mdx index 8c3e244e032..5828e3474cc 100644 --- a/src/content/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements-net-framework.mdx +++ b/src/content/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements-net-framework.mdx @@ -675,7 +675,12 @@ The .NET agent doesn't directly monitor datastore processes. Also, by default th /> - + + Use [Oracle.ManagedDataAccess](https://www.nuget.org/packages/Oracle.ManagedDataAccess/) + + * Minimum supported version: 12.1.2400 + * Latest verified compatible version: 23.5.1 + From c6eaa884463e83632cc62b83c3c48485dce45679 Mon Sep 17 00:00:00 2001 From: Jordan Porter Date: Fri, 30 Aug 2024 15:44:43 -0600 Subject: [PATCH 002/173] add deprecation note --- .../browser/new-relic-browser/browser-apis/createtracer.mdx | 4 ++++ .../new-relic-browser/browser-apis/using-browser-apis.mdx | 2 +- .../event-data/events-reported-browser-monitoring.mdx | 2 +- .../browser/new-relic-browser/browser-apis/createtracer.mdx | 4 ++++ .../new-relic-browser/browser-apis/using-browser-apis.mdx | 2 +- .../browser/new-relic-browser/browser-apis/createtracer.mdx | 4 ++++ .../new-relic-browser/browser-apis/using-browser-apis.mdx | 2 +- .../event-data/events-reported-browser-monitoring.mdx | 2 +- .../browser/new-relic-browser/browser-apis/createtracer.mdx | 4 ++++ .../new-relic-browser/browser-apis/using-browser-apis.mdx | 2 +- .../event-data/events-reported-browser-monitoring.mdx | 2 +- .../browser/new-relic-browser/browser-apis/createtracer.mdx | 4 ++++ .../new-relic-browser/browser-apis/using-browser-apis.mdx | 2 +- .../event-data/events-reported-browser-monitoring.mdx | 2 +- 14 files changed, 29 insertions(+), 9 deletions(-) diff --git a/src/content/docs/browser/new-relic-browser/browser-apis/createtracer.mdx b/src/content/docs/browser/new-relic-browser/browser-apis/createtracer.mdx index a0fefd78210..5f12b081ced 100644 --- a/src/content/docs/browser/new-relic-browser/browser-apis/createtracer.mdx +++ b/src/content/docs/browser/new-relic-browser/browser-apis/createtracer.mdx @@ -16,6 +16,10 @@ redirects: freshnessValidatedDate: never --- + + The createTracer browser API has been deprecated. The recommended way to trace the duration of a task is to capture a performance [mark](https://developer.mozilla.org/en-US/docs/Web/API/Performance/mark) and/or [measure](https://developer.mozilla.org/en-US/docs/Web/API/Performance/measure). Future browser agent versions will capture marks and measures automatically, at which point support for createTracer will cease. + + ## Syntax ```js diff --git a/src/content/docs/browser/new-relic-browser/browser-apis/using-browser-apis.mdx b/src/content/docs/browser/new-relic-browser/browser-apis/using-browser-apis.mdx index 2ec6318e759..be67861e40e 100644 --- a/src/content/docs/browser/new-relic-browser/browser-apis/using-browser-apis.mdx +++ b/src/content/docs/browser/new-relic-browser/browser-apis/using-browser-apis.mdx @@ -211,7 +211,7 @@ To track single page applications, use these SPA API methods: - [`newrelic.interaction().createTracer()`](/docs/browser/new-relic-browser/browser-apis/createtracer) + [`newrelic.interaction().createTracer()`](/docs/browser/new-relic-browser/browser-apis/createtracer) (deprecated) diff --git a/src/content/docs/data-apis/understand-data/event-data/events-reported-browser-monitoring.mdx b/src/content/docs/data-apis/understand-data/event-data/events-reported-browser-monitoring.mdx index d3ed6655b23..e5af264bf9f 100644 --- a/src/content/docs/data-apis/understand-data/event-data/events-reported-browser-monitoring.mdx +++ b/src/content/docs/data-apis/understand-data/event-data/events-reported-browser-monitoring.mdx @@ -91,7 +91,7 @@ Select an event name in the following table to see its attributes. - `BrowserTiming` is a custom event that captures SPA timing data for browser interactions started using the custom [createTracer](/docs/browser/new-relic-browser/browser-agent-spa-api/createtracer-browser-spa-api) SPA API method. `BrowserTiming` contains many of the same attributes used by other events, especially `AjaxRequest`. + `BrowserTiming` is a custom event that captures SPA timing data for browser interactions started using the custom [createTracer](/docs/browser/new-relic-browser/browser-agent-spa-api/createtracer-browser-spa-api) SPA API method. `BrowserTiming` contains many of the same attributes used by other events, especially `AjaxRequest`. (deprecated) diff --git a/src/i18n/content/es/docs/browser/new-relic-browser/browser-apis/createtracer.mdx b/src/i18n/content/es/docs/browser/new-relic-browser/browser-apis/createtracer.mdx index 47bbe8d79a0..d0b51a941b5 100644 --- a/src/i18n/content/es/docs/browser/new-relic-browser/browser-apis/createtracer.mdx +++ b/src/i18n/content/es/docs/browser/new-relic-browser/browser-apis/createtracer.mdx @@ -11,6 +11,10 @@ freshnessValidatedDate: never translationType: machine --- + + The createTracer browser API has been deprecated. The recommended way to trace the duration of a task is to capture a performance [mark](https://developer.mozilla.org/en-US/docs/Web/API/Performance/mark) and/or [measure](https://developer.mozilla.org/en-US/docs/Web/API/Performance/measure). Future browser agent versions will capture marks and measures automatically, at which point support for createTracer will cease. + + ## Sintaxis ```js diff --git a/src/i18n/content/es/docs/browser/new-relic-browser/browser-apis/using-browser-apis.mdx b/src/i18n/content/es/docs/browser/new-relic-browser/browser-apis/using-browser-apis.mdx index 09993418030..181de5dc1df 100644 --- a/src/i18n/content/es/docs/browser/new-relic-browser/browser-apis/using-browser-apis.mdx +++ b/src/i18n/content/es/docs/browser/new-relic-browser/browser-apis/using-browser-apis.mdx @@ -187,7 +187,7 @@ Para realizar un seguimiento de una aplicación de una sola página, utilice est - [`newrelic.interaction().createTracer()`](/docs/browser/new-relic-browser/browser-apis/createtracer) + [`newrelic.interaction().createTracer()`](/docs/browser/new-relic-browser/browser-apis/createtracer) (deprecated) diff --git a/src/i18n/content/jp/docs/browser/new-relic-browser/browser-apis/createtracer.mdx b/src/i18n/content/jp/docs/browser/new-relic-browser/browser-apis/createtracer.mdx index 0707a059fc2..f4048eb9afd 100644 --- a/src/i18n/content/jp/docs/browser/new-relic-browser/browser-apis/createtracer.mdx +++ b/src/i18n/content/jp/docs/browser/new-relic-browser/browser-apis/createtracer.mdx @@ -11,6 +11,10 @@ freshnessValidatedDate: never translationType: machine --- + + The createTracer browser API has been deprecated. The recommended way to trace the duration of a task is to capture a performance [mark](https://developer.mozilla.org/en-US/docs/Web/API/Performance/mark) and/or [measure](https://developer.mozilla.org/en-US/docs/Web/API/Performance/measure). Future browser agent versions will capture marks and measures automatically, at which point support for createTracer will cease. + + ## 構文 ```js diff --git a/src/i18n/content/jp/docs/browser/new-relic-browser/browser-apis/using-browser-apis.mdx b/src/i18n/content/jp/docs/browser/new-relic-browser/browser-apis/using-browser-apis.mdx index 4db2cfc1dc0..e67ccc630aa 100644 --- a/src/i18n/content/jp/docs/browser/new-relic-browser/browser-apis/using-browser-apis.mdx +++ b/src/i18n/content/jp/docs/browser/new-relic-browser/browser-apis/using-browser-apis.mdx @@ -207,7 +207,7 @@ browser APIすると、 をカスタマイズお - [`newrelic.interaction().createTracer()`](/docs/browser/new-relic-browser/browser-apis/createtracer) + [`newrelic.interaction().createTracer()`](/docs/browser/new-relic-browser/browser-apis/createtracer) (deprecated) diff --git a/src/i18n/content/jp/docs/data-apis/understand-data/event-data/events-reported-browser-monitoring.mdx b/src/i18n/content/jp/docs/data-apis/understand-data/event-data/events-reported-browser-monitoring.mdx index 15796d4b5f2..4e41d8a8882 100644 --- a/src/i18n/content/jp/docs/data-apis/understand-data/event-data/events-reported-browser-monitoring.mdx +++ b/src/i18n/content/jp/docs/data-apis/understand-data/event-data/events-reported-browser-monitoring.mdx @@ -81,7 +81,7 @@ translationType: human - `BrowserTiming` は、カスタム[createTracer](/docs/browser/new-relic-browser/browser-agent-spa-api/createtracer-browser-spa-api) SPA APIメソッドを使用して開始されたブラウザインタラクションのSPAタイミングデータをキャプチャするカスタムイベントです。`BrowserTiming`には、他のイベント（特に`AjaxRequest`）で使用されるものと同じ多くの属性が含まれています。 + `BrowserTiming` は、カスタム[createTracer](/docs/browser/new-relic-browser/browser-agent-spa-api/createtracer-browser-spa-api) SPA APIメソッドを使用して開始されたブラウザインタラクションのSPAタイミングデータをキャプチャするカスタムイベントです。`BrowserTiming`には、他のイベント（特に`AjaxRequest`）で使用されるものと同じ多くの属性が含まれています。 (deprecated) diff --git a/src/i18n/content/kr/docs/browser/new-relic-browser/browser-apis/createtracer.mdx b/src/i18n/content/kr/docs/browser/new-relic-browser/browser-apis/createtracer.mdx index 8ce0d006a11..4ac86c629f9 100644 --- a/src/i18n/content/kr/docs/browser/new-relic-browser/browser-apis/createtracer.mdx +++ b/src/i18n/content/kr/docs/browser/new-relic-browser/browser-apis/createtracer.mdx @@ -11,6 +11,10 @@ freshnessValidatedDate: never translationType: machine --- + + The createTracer browser API has been deprecated. The recommended way to trace the duration of a task is to capture a performance [mark](https://developer.mozilla.org/en-US/docs/Web/API/Performance/mark) and/or [measure](https://developer.mozilla.org/en-US/docs/Web/API/Performance/measure). Future browser agent versions will capture marks and measures automatically, at which point support for createTracer will cease. + + ## 통사론 ```js diff --git a/src/i18n/content/kr/docs/browser/new-relic-browser/browser-apis/using-browser-apis.mdx b/src/i18n/content/kr/docs/browser/new-relic-browser/browser-apis/using-browser-apis.mdx index 2926f47056c..04651cb0797 100644 --- a/src/i18n/content/kr/docs/browser/new-relic-browser/browser-apis/using-browser-apis.mdx +++ b/src/i18n/content/kr/docs/browser/new-relic-browser/browser-apis/using-browser-apis.mdx @@ -207,7 +207,7 @@ translationType: machine - [`newrelic.interaction().createTracer()`](/docs/browser/new-relic-browser/browser-apis/createtracer) + [`newrelic.interaction().createTracer()`](/docs/browser/new-relic-browser/browser-apis/createtracer) (deprecated) diff --git a/src/i18n/content/kr/docs/data-apis/understand-data/event-data/events-reported-browser-monitoring.mdx b/src/i18n/content/kr/docs/data-apis/understand-data/event-data/events-reported-browser-monitoring.mdx index ef62a42549c..c6fcb15731b 100644 --- a/src/i18n/content/kr/docs/data-apis/understand-data/event-data/events-reported-browser-monitoring.mdx +++ b/src/i18n/content/kr/docs/data-apis/understand-data/event-data/events-reported-browser-monitoring.mdx @@ -81,7 +81,7 @@ translationType: machine - `BrowserTiming` 사용자 정의 [createTracer](/docs/browser/new-relic-browser/browser-agent-spa-api/createtracer-browser-spa-api) SPA API 메소드를 사용하여 시작된 브라우저 상호 작용에 대한 SPA 타이밍 데이터를 캡처하는 사용자 정의 이벤트입니다. `BrowserTiming` 에는 다른 이벤트, 특히 `AjaxRequest` 에서 사용하는 것과 동일한 속성이 많이 포함되어 있습니다. + `BrowserTiming` 사용자 정의 [createTracer](/docs/browser/new-relic-browser/browser-agent-spa-api/createtracer-browser-spa-api) SPA API 메소드를 사용하여 시작된 브라우저 상호 작용에 대한 SPA 타이밍 데이터를 캡처하는 사용자 정의 이벤트입니다. `BrowserTiming` 에는 다른 이벤트, 특히 `AjaxRequest` 에서 사용하는 것과 동일한 속성이 많이 포함되어 있습니다. (deprecated) diff --git a/src/i18n/content/pt/docs/browser/new-relic-browser/browser-apis/createtracer.mdx b/src/i18n/content/pt/docs/browser/new-relic-browser/browser-apis/createtracer.mdx index a22aeb41a0e..df5c20f8d22 100644 --- a/src/i18n/content/pt/docs/browser/new-relic-browser/browser-apis/createtracer.mdx +++ b/src/i18n/content/pt/docs/browser/new-relic-browser/browser-apis/createtracer.mdx @@ -11,6 +11,10 @@ freshnessValidatedDate: never translationType: machine --- + + The createTracer browser API has been deprecated. The recommended way to trace the duration of a task is to capture a performance [mark](https://developer.mozilla.org/en-US/docs/Web/API/Performance/mark) and/or [measure](https://developer.mozilla.org/en-US/docs/Web/API/Performance/measure). Future browser agent versions will capture marks and measures automatically, at which point support for createTracer will cease. + + ## Sintaxe ```js diff --git a/src/i18n/content/pt/docs/browser/new-relic-browser/browser-apis/using-browser-apis.mdx b/src/i18n/content/pt/docs/browser/new-relic-browser/browser-apis/using-browser-apis.mdx index 02ad35c7f22..6d9ebcc5338 100644 --- a/src/i18n/content/pt/docs/browser/new-relic-browser/browser-apis/using-browser-apis.mdx +++ b/src/i18n/content/pt/docs/browser/new-relic-browser/browser-apis/using-browser-apis.mdx @@ -207,7 +207,7 @@ Para rastrear aplicativos de página única, use estes métodos de API SPA: - [`newrelic.interaction().createTracer()`](/docs/browser/new-relic-browser/browser-apis/createtracer) + [`newrelic.interaction().createTracer()`](/docs/browser/new-relic-browser/browser-apis/createtracer) (deprecated) diff --git a/src/i18n/content/pt/docs/data-apis/understand-data/event-data/events-reported-browser-monitoring.mdx b/src/i18n/content/pt/docs/data-apis/understand-data/event-data/events-reported-browser-monitoring.mdx index 8feeef767c2..8d6b086972f 100644 --- a/src/i18n/content/pt/docs/data-apis/understand-data/event-data/events-reported-browser-monitoring.mdx +++ b/src/i18n/content/pt/docs/data-apis/understand-data/event-data/events-reported-browser-monitoring.mdx @@ -81,7 +81,7 @@ Selecione um nome de evento na tabela a seguir para ver seu atributo. - `BrowserTiming` é um evento personalizado que captura dados de tempo do SPA para interação do browser iniciada usando o método [createTracer](/docs/browser/new-relic-browser/browser-agent-spa-api/createtracer-browser-spa-api) SPA API personalizado. `BrowserTiming` contém muitos dos mesmos atributos usados por outros eventos, especialmente `AjaxRequest`. + `BrowserTiming` é um evento personalizado que captura dados de tempo do SPA para interação do browser iniciada usando o método [createTracer](/docs/browser/new-relic-browser/browser-agent-spa-api/createtracer-browser-spa-api) SPA API personalizado. `BrowserTiming` contém muitos dos mesmos atributos usados por outros eventos, especialmente `AjaxRequest`. (deprecated) From ed2e026bf3b7c189f8dc35fb44f66c01a3f31660 Mon Sep 17 00:00:00 2001 From: Gulab Sidhwani <113113837+gsidhwani-nr@users.noreply.github.com> Date: Mon, 2 Sep 2024 16:47:18 +0530 Subject: [PATCH 003/173] fix: Update vmware-tanzu-firehose-nozzle-integration.mdx --- .../vmware-tanzu-firehose-nozzle-integration.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/src/content/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration.mdx b/src/content/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration.mdx index 8a5f5e952a1..8a21bed5a58 100644 --- a/src/content/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration.mdx +++ b/src/content/docs/infrastructure/other-infrastructure-integrations/cloudfoundry-integrations/vmware-tanzu-firehose-nozzle-integration.mdx @@ -34,7 +34,7 @@ New Relic Nozzle for VMware Tanzu has the following requirements: * An active New Relic account with a Pro or Pro Trial license. If you do not already have a New Relic account, you can obtain a [14-day free trial license](http://newrelic.com/signup?funnel=pivotal-cloud-foundry&partner=Pivotal+Cloud+Foundry). * New Relic Insights included in the license -* VMware Tanzu versions v2.10.x through v5.0.x. +* VMware Tanzu versions v2.10.x through v6.0.x. ## Key features [#key-features] @@ -97,7 +97,7 @@ The following table provides version and version-support information about New R - 2.9.0 + 2.10.0 @@ -107,7 +107,7 @@ The following table provides version and version-support information about New R - November 14, 2023 + Sep 09, 2024 @@ -117,7 +117,7 @@ The following table provides version and version-support information about New R - New Relic Nozzle v2.9.0 + New Relic Nozzle v2.10.0 @@ -137,7 +137,7 @@ The following table provides version and version-support information about New R - v2.10.x, v2.11.x, v2.12.x, v2.13.x, v3.0.x, v4.0.x and v5.0.x + v2.10.x, v2.11.x, v2.12.x, v2.13.x, v3.0.x, v4.0.x , v5.0.x & v6.0.x From cb66ffafd57cf8378125af86d8096f40e77d915d Mon Sep 17 00:00:00 2001 From: nbaenam Date: Tue, 3 Sep 2024 12:47:52 +0200 Subject: [PATCH 004/173] feat(IAST): Added the iast configuration file --- src/content/docs/iast/iast-configuration.mdx | 89 ++++++++++++++++++++ src/nav/iast.yml | 4 +- 2 files changed, 92 insertions(+), 1 deletion(-) create mode 100644 src/content/docs/iast/iast-configuration.mdx diff --git a/src/content/docs/iast/iast-configuration.mdx b/src/content/docs/iast/iast-configuration.mdx new file mode 100644 index 00000000000..3719c8944d3 --- /dev/null +++ b/src/content/docs/iast/iast-configuration.mdx @@ -0,0 +1,89 @@ +--- +title: IAST configuration +tags: + - IAST + - New Relic IAST + - Configuration +metaDescription: Find out how to configure IAST. +freshnessValidatedDate: 2024-09-16 +--- + +You can configure your IAST to handle scan scheduling. These configurations allow you to exclude certain APIs, parameters, and vulnerability categories from IAST analysis. You can also delay IAST scans or schedule them for specific times of the day. + +## Scheduling IAST Scans [#scheduling-iast-scans] + +You can start and stop your scheduled IAST scans using 2 variables. These variables allow you to set specific times for the IAST scan or add a delay to the IAST scan start time from the application. + + +### Configure your scheduled IAST scans [#configure-scheduled] + +Open the `newrelic.yml` configuration file to set the `scan_schedule` parameters. + +```yml +security: + scan_schedule: + delay: 0 #In minutes, default is 0 min + duration: 0 #In minutes, default is forever + schedule: "" #Cron Expression to define start time + always_sample_traces: false #regardless of scan schedule +``` + + + delay (in minutes)} + > + The `delay` field specifies the time in minutes before an IAST scan begins after the application starts. The default value is `0`. + + + duration (in minutes)} + > + The `duration` field specifies the length of time in minutes that the IAST scan will run. The default value is forever, it has no limits. + + For example, if you set `duration: 300`, the IAST scan will run for 300 minutes (5 hours). + + + schedule (Cron expression)} + > + The `schedule` field specifies a cron expression that defines when the IAST scan should run. By default, `schedule` is disabled. The [cron expression](https://www.quartz-scheduler.org/documentation/quartz-2.3.0/tutorials/crontrigger.html) consists of six fields separated by spaces: + + * **second**: Specifies the second of the hour (0-59) + * **minute**: Specifies the minute of the hour (0-59) + * **hour**: Specifies the hour of the day (0-23) + * **day**: Specifies the day of the month (1-31) + * **month**: The month of the year (1-12 or JAN-DEC) + * **day_of_week**: Specifies the day of the week (1-7 or SUN-SAT), where 1 = Sunday + + + What happens if `duration` is not specified? Omitting the duration parameter implies that the IAST scan should never stop. In this scenario, the specified schedule is treated as a start time rather than a recurring operation. The scan will continue indefinitely without interruption or termination. For example, `schedule: "0 0 0 * * ?"` would schedule the IAST scan to run at 12am every day. + + + + always_sample_traces (Boolean)} + > + `always-sample-traces` allows IAST to actively collect trace data in the background, and the security agent will use this collected data to perform an IAST scan at the scheduled time. However, for applications with session management, we strongly recommend setting the `always_sample_traces` flag to false. This ensures that IAST sampling and scanning is limited to a specified window. Sessions typically have a short lifetime, often ending within 30 minutes. In this scenario, sampling traces before the window will not provide valuable insight and may result in missed vulnerabilities. By default, the value of `always_sample_traces` is false. + + + + + + + + + + + + + + + + + + + diff --git a/src/nav/iast.yml b/src/nav/iast.yml index 16751fd27e4..c7211af2d31 100644 --- a/src/nav/iast.yml +++ b/src/nav/iast.yml @@ -3,8 +3,10 @@ path: /docs/iast pages: - title: Introduction to IAST path: /docs/iast/introduction - - title: Install IAST + - title: IAST installation path: /docs/iast/install + - title: IAST configuration + path: /docs/iast/iast-configuration - title: Navigating IAST UI pages: - title: IAST testing status From a7bcae325e27b94d3b808e96dbbfc37f7b857008 Mon Sep 17 00:00:00 2001 From: Marty Tippin <120425148+tippmar-nr@users.noreply.github.com> Date: Tue, 3 Sep 2024 09:47:24 -0500 Subject: [PATCH 005/173] Re-apply Oracle compatibility changes --- .../net-agent-compatibility-requirements.mdx | 31 +++++++++++++++++-- 1 file changed, 29 insertions(+), 2 deletions(-) diff --git a/src/content/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx b/src/content/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx index 3ec397b1027..9167102e4cc 100644 --- a/src/content/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx +++ b/src/content/docs/apm/agents/net-agent/getting-started/net-agent-compatibility-requirements.mdx @@ -416,6 +416,28 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co + + + Oracle + + + + + + + + Use [Oracle.ManagedDataAccess.Core](https://www.nuget.org/packages/Oracle.ManagedDataAccess.Core/) + + * Minimum supported version: 23.4.0 + * Latest verified compatible version: 23.5.1 + + Older versions of `Oracle.ManagedDataAccess.Core` may be instrumented, but have not been tested and are not supported. + + + PostgreSQL @@ -1373,9 +1395,14 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co /> - + + Use [Oracle.ManagedDataAccess](https://www.nuget.org/packages/Oracle.ManagedDataAccess/) + + * Minimum supported version: 12.1.2400 + * Latest verified compatible version: 23.5.1 + - + PostgreSQL From 72aa943fd217a1b83dc1a14150422ff1b01d0b5f Mon Sep 17 00:00:00 2001 From: Anusha Hegde Date: Thu, 5 Sep 2024 14:30:21 +0530 Subject: [PATCH 006/173] Updated firehose integration & fedramp page to include firehose in fedramp unsupported list --- .../stream-logs-using-kinesis-data-firehose.mdx | 2 ++ .../certificates-standards-regulations/fedramp.mdx | 14 ++++++++++++++ 2 files changed, 16 insertions(+) diff --git a/src/content/docs/logs/forward-logs/stream-logs-using-kinesis-data-firehose.mdx b/src/content/docs/logs/forward-logs/stream-logs-using-kinesis-data-firehose.mdx index 98ec1a04269..559894f8c03 100644 --- a/src/content/docs/logs/forward-logs/stream-logs-using-kinesis-data-firehose.mdx +++ b/src/content/docs/logs/forward-logs/stream-logs-using-kinesis-data-firehose.mdx @@ -19,6 +19,8 @@ If your log data is already being monitored by [Amazon CloudWatch Logs](https:// Forwarding your CloudWatch Logs or other logs compatible with a Kinesis stream to New Relic will give you enhanced capabilities to collect, process, explore, query, and alert on your log data. +You should not enable Log Streaming using Kinesis Data Firehose if you're a [FedRAMP customer](/docs/security/security-privacy/compliance/certificates-standards-regulations/fedramp-moderate), because AWS Kinesis Data Firehose integration is not currently FedRAMP authorized. + ## Create the delivery stream for New Relic [#create-delivery-stream] To forward your logs from Kinesis Data Firehose to New Relic: diff --git a/src/content/docs/security/security-privacy/compliance/certificates-standards-regulations/fedramp.mdx b/src/content/docs/security/security-privacy/compliance/certificates-standards-regulations/fedramp.mdx index a654d780166..b2ed36f662e 100644 --- a/src/content/docs/security/security-privacy/compliance/certificates-standards-regulations/fedramp.mdx +++ b/src/content/docs/security/security-privacy/compliance/certificates-standards-regulations/fedramp.mdx @@ -247,5 +247,19 @@ The following services are not FedRAMP-authorized: [AI Monitoring](/docs/ai-monitoring/compatibility-requirements-ai-monitoring/) + + + + N/A + + + + AWS + + + + [Logs Streaming using Kinesis Data Firehose](/docs/logs/forward-logs/stream-logs-using-kinesis-data-firehose/) + + From f13f80f04cb22af6d86999af5bb5aedf9ed0f3bb Mon Sep 17 00:00:00 2001 From: Anusha Hegde Date: Thu, 5 Sep 2024 15:27:18 +0530 Subject: [PATCH 007/173] Updated firehose integration page to add text in important block --- .../forward-logs/stream-logs-using-kinesis-data-firehose.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/content/docs/logs/forward-logs/stream-logs-using-kinesis-data-firehose.mdx b/src/content/docs/logs/forward-logs/stream-logs-using-kinesis-data-firehose.mdx index 559894f8c03..add7f7e729e 100644 --- a/src/content/docs/logs/forward-logs/stream-logs-using-kinesis-data-firehose.mdx +++ b/src/content/docs/logs/forward-logs/stream-logs-using-kinesis-data-firehose.mdx @@ -19,7 +19,9 @@ If your log data is already being monitored by [Amazon CloudWatch Logs](https:// Forwarding your CloudWatch Logs or other logs compatible with a Kinesis stream to New Relic will give you enhanced capabilities to collect, process, explore, query, and alert on your log data. + You should not enable Log Streaming using Kinesis Data Firehose if you're a [FedRAMP customer](/docs/security/security-privacy/compliance/certificates-standards-regulations/fedramp-moderate), because AWS Kinesis Data Firehose integration is not currently FedRAMP authorized. + ## Create the delivery stream for New Relic [#create-delivery-stream] From 7486412627f86dbc34fb8b0eb80e9f77c4873e14 Mon Sep 17 00:00:00 2001 From: pati04g <101635997+pati04g@users.noreply.github.com> Date: Thu, 5 Sep 2024 13:29:48 +0200 Subject: [PATCH 008/173] Update dashboard-template-variables.mdx This PR updates the documentation to include a new feature (Include Variable) that will be released on the 10th of September. Do not merge until then --- .../dashboard-template-variables.mdx | 35 +++++++++++++++++-- 1 file changed, 33 insertions(+), 2 deletions(-) diff --git a/src/content/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx b/src/content/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx index fb16b62f398..2591f04c160 100644 --- a/src/content/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx +++ b/src/content/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables.mdx @@ -7,7 +7,7 @@ redirects: freshnessValidatedDate: never --- -For custom dashboards, you can use **template variables** to dynamically filter charts and other widgets. Template variables help make your dashboards more useful, and help you more easily create dashboards you can reuse for different use cases. +For custom dashboards, you can use **template variables** to dynamically filter charts and other widgets. Template variables help make your dashboards more useful, and help you to more easily create dashboards you can reuse for different use cases. ## Why use template variables? [#defined] @@ -31,6 +31,32 @@ With template variables, you can set up a wide variety of variables and filters * A dropdown to select specific durations or other numeric values * Filters that use free text fields to find matching strings +Furthermore, you can now decide if you want to include the variable or not without having to modify your queries. See the [Include variable](/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables/#include-variable) section for details. + +## Include variable [#include-variable] + +You now have the flexibility to include/exclude a variable in your dashboards as required by setting the "Include variable" toggle to the desired value, as well as configuring its default value (see the [template variables](/docs/query-your-data/explore-query-data/dashboards/dashboard-template-variables/#create-variables) section). +For instance, you are investigating an issue that is not specific to any particular value defined by the variable. In fact, the values defined for that variable may be limiting the results delivered by the queries using this variable even when you select all its possible values. In this case, the best option would be to use a query that does not take under consideration that particular attribute defined by the variable but having to edit the impacted widgets is time consuming. You can now choose to not include the variable which will effectively remove it from the query and replace the condition with a neutral boolean value (true or false). This ensures that your query remains valid and returns the expected results. +For example, the following query: + + ```sql + FROM PageAction SELECT count(*) AS 'views' WHERE countryCode IN ({{countryCode}}) and appName = 'Test App' FACET countryCode + ``` + +With the variable not included would become: + + ```sql + FROM PageAction SELECT count(*) AS 'views' WHERE true and appName = 'Test App' FACET countryCode + ``` +This feature is particularly useful when: +* The variable has more values than the maximum allowed (for instance, 5000 max results for uniques by default) or a very high number of values. Choosing to disable the variable by default will deliver considerable performance improvements. +* The data source for the variable differs from the database you're querying. +In these cases, selecting all values from the database using "Select all" isn't sufficient. By excluding the variable, you can retrieve all values from the database. + +Limitations on Include variable: +* When used in FACET cases the condition is replaced with true, converting it to an always-true condition. +* When used in other contexts like functions or with the SELECT statement, you will get an error ("Unknown function Disable_variable()"). This is because the disable variable function isn't implemented for these specific cases yet. + ## Requirements and limitations [#requirements] Template variables can only be used in the context of making widgets for custom dashboards. See [NRQL variables](/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-syntax-clauses-functions/#with-as-nrql-var) for using variables in a NRQL query. @@ -185,9 +211,14 @@ Creating a template variable consists of two steps. - Optional. These are the defaults value that the dashboard will filter on. For example, if you used the `country` query above, you could input `ES` as the default value and the dashboard would automatically filter to that value. You can also select all possibilities. + Optional. These are the default values that the dashboard will filter on. For example, if you used the `country` query above, you could input `ES` as the default value and the dashboard would automatically filter to that value. You can also select all possibilities. To use multiple values on a `WHERE` clause you need to use [`IN`](/docs/query-your-data/nrql-new-relic-query-language/get-started/nrql-syntax-clauses-functions/#sel-where) instead of `=`. + + The "Include variable" toggle will determine the default configuration, include or exclude, for that variable in the dashboard. This configuration can be modified by the user viewing the dashboard by using the "Include variable" toggle in the variable dropdown menu. The user selected configuration will be valid for the duration of the session. + + Note that you can only configure default values when the toggle is set to include variable. Once you select the default values you can switch the toggle so the variable is not included by default. The default values will be preselected when any user turns the toggle to include the variable from the variable dropdown menu. + From 0078825d07349d078450eaa0b9e199adcf2a2c6f Mon Sep 17 00:00:00 2001 From: nbaenam Date: Thu, 5 Sep 2024 17:23:48 +0200 Subject: [PATCH 009/173] feat(Alerts): Updated the Muting rules: Suppress notifications doc --- .../muting-rules-suppress-notifications.mdx | 330 ++++++++++-------- ..._screenshot-crop_incidents-muted-icon.webp | Bin 0 -> 232402 bytes ...ot-crop_issue-critical-incident-muted.webp | Bin 0 -> 159562 bytes ...rts_screenshot-crop_issues-muted-icon.webp | Bin 0 -> 173394 bytes ...creenshot-crop_schedule-muting window.webp | Bin 0 -> 33334 bytes ...erts_screenshot-crop_violation-filter.webp | Bin 0 -> 51364 bytes .../alerts_screenshot-full_muting-rules.webp | Bin 0 -> 118246 bytes 7 files changed, 177 insertions(+), 153 deletions(-) create mode 100644 static/images/alerts_screenshot-crop_incidents-muted-icon.webp create mode 100644 static/images/alerts_screenshot-crop_issue-critical-incident-muted.webp create mode 100644 static/images/alerts_screenshot-crop_issues-muted-icon.webp create mode 100644 static/images/alerts_screenshot-crop_schedule-muting window.webp create mode 100644 static/images/alerts_screenshot-crop_violation-filter.webp create mode 100644 static/images/alerts_screenshot-full_muting-rules.webp diff --git a/src/content/docs/alerts/get-notified/muting-rules-suppress-notifications.mdx b/src/content/docs/alerts/get-notified/muting-rules-suppress-notifications.mdx index 5fd295984fa..37c0f2b68f2 100644 --- a/src/content/docs/alerts/get-notified/muting-rules-suppress-notifications.mdx +++ b/src/content/docs/alerts/get-notified/muting-rules-suppress-notifications.mdx @@ -17,78 +17,88 @@ Alerts sends out timely notifications when your system is having problems. Somet Once you've spotted the common elements in your unwanted notifications, you can define muting rules that specifically target those elements, while letting other notifications through. Even when a notification is muted, still gathers data on those incidents. Muting rules don't interfere with the alerts process and are applied at the point right before a notification is sent. -## Manage muting rules [#manage] +## How muting rules work [#overview] -A muting rule condition is the set of individual expressions made up of attributes, operators, and values that define which incidents to target for muting. +Muting rules are applied at the end of the default alert lifecycle in order to suppress or mute notifications. They don't disable existing policies or conditions. For example, you can mute notifications during known system disruptions, such as maintenance windows and deployments. System disruption incidents will still be identified, even though the notifications for those incidents are muted. -You can create, enable, disable, and manage muting rules. Go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts > Muting rules**. Enable or disable muting rules at any time. Click the icon on the row of each rule to edit and remove rules. +A muting rule uses a set of conditions that match against attributes in a [incident event](/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/understand-technical-concepts/incident-event-attributes). The muting rules tell us how to: -Rules can have one of the following statuses: +1. Identify individual incidents after they're created, but before an issue is opened. +2. Override their default condition to indicate that they should be "muted." -* **Active**: Muting is enabled and active. -* **Scheduled**: Muting is enabled but not active yet (there's a future schedule). -* **Ended**: Muting is enabled, but no longer active (there's no future schedule). -* **Inactive**: Muting is disabled. +Currently, muting an incident means that the normal alerts incident lifecycle will be maintained, except that an issue that only contains muted incidents will not send out any notifications. -Manage muting rules +Muting rules are determined by the first event which triggered a notification within an issue. Meaning, if the first notification event was muted because of a muting state, the rest of the issue will be muted as well. -
- **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts > Muting rules**: You can create complex muting rules to target a small or large set of unwanted notifications. -
+Muting rules override specific incidents. They don't disable existing policies or conditions. This allows you to mute incidents from specific entities that may be covered by a policy or condition that covers a large number of entities. This also keeps you from having to over-mute your monitoring when you are performing maintenance on a subset of your system. -## Create a muting rule [#create] +The following table describes how the alerts incident lifecycle is affected by muted incidents: - - Before creating muting rules, you'll need to [create policies](/docs/alerts/new-relic-alerts/configuring-alert-policies/create-edit-or-find-alert-policy) and [conditions](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/create-alert-conditions/) that generate [notifications](/docs/alerts-applied-intelligence/notifications/intro-notifications/). - + + + + -To create a muting rule, go to **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts > Muting rules** and click **+ Add a rule**. Enter a name and a description (optional) for the muting rule, and select the account to which the rule will apply. + + + -Next, build the incidents filter. You can use a subset of [incident event attributes](/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/understand-technical-concepts/incident-event-attributes). Choose an attribute, an [operator](#sub-conditions), and a value. These are the attributes: `accountId`, `conditionId`, `conditionName`, `conditionType`, `entity.guid`, `nrqlEventType`, `nrqlQuery`, `policyId`, `policyName`, `product`,`runbookUrl` (as `conditionRunbookUrl`), `tags.`, and `targetName`). Values are compared against one of your incident attributes, such as an alerts policy ID or a condition name. -Click **Add another condition** if you want to include more filters. + + + + -Muting rule edit screen + + -
- **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts > Muting rules**: You can create complex muting rules to target a small or large set of unwanted notifications. -
+ + -## Schedule a muting rule [#schedule-muting-rule] + + -If needed, you can schedule your muting rules. + + + +
+ IF + + THEN +
+ **Event**: Issue is activated +
+ An issue is activated because of an incident that is **not** muted + + Notifications for this issue will be sent. +
+ An issue is activated due to an incident that **is** muted + + Notifications for this issue will **not** be sent (muted). +
-To do this, select a start time and/or end time. Optionally, you can set the muting rule to last an entire day. +### Muting behavior with workflows [#workflow-behavior] -You can also choose to select a time zone for the muting rule schedule. The default is the time zone selected in your user preferences. +A triggered incident has a 1:1 ratio with an issue so if an incident is muted then the matching issue will be muted as well. +Workflows are triggered by issues that can have one or more incidents, therefore there could be a scenario of muted and not muted incidents combined. -Schedule your muting window +Each issue has one of the following muting states: -
- **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts > Muting rules**: Flexible and powerful options for scheduling your muting rules. -
+* **Fully muted (`FULLY_MUTED`)**: an issue has all of its open incidents muted (Default value). +* **Partially muted (`PARTIALLY_MUTED`)**: an issue that has at least one open incident that is muted and one open incident that is not muted. +* **Not muted (`NOT_MUTED`)**: an issue that has no open muted incidents. -You can schedule your muting rules to recur daily, weekly, or monthly. A muting rule that's scheduled to repeat weekly includes the option to select the days of the week to recur. If no days are selected, the weekly recurrence will default to repeating on the day of the week that the muting rule is scheduled to start. +For a step-by-step guide on how to set up your workflows, check out an example demo below (approx. 2:17 minutes): - - The **Repeat** day of the week checkboxes override the **Starts** and **Ends** date fields. If you set a start date and also choose a day of the week, your muting rules will be applied on the first of those days after your start date. - +