From 81c0b7f4f1a2767e940ffade291f21421f2ea98d Mon Sep 17 00:00:00 2001 From: Chris Hynes <111462425+chynesNR@users.noreply.github.com> Date: Fri, 25 Oct 2024 09:08:29 -0700 Subject: [PATCH 01/22] Add custom instrumentation link to .NET datastore instrumentation info --- .../getting-started/net-agent-compatibility-requirements.mdx | 2 ++ 1 file changed, 2 insertions(+) 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 cf5a19ff0c1..a899e27c010 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 @@ -590,6 +590,8 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co The .NET agent does not directly monitor datastore processes. Also, the .NET SQL parameter capture in a query trace does not list parameters for a parameterized query or a stored procedure. Collecting [instance details](/docs/apm/applications-menu/features/analyze-database-instance-level-performance-issues) for supported datastores is enabled by default. To request instance-level information from datastores not currently listed, get support at [support.newrelic.com](https://support.newrelic.com). + + If your datastore is not listed here, you can add custom instrumentation using the `RecordDatastoreSegment` method in the [.NET agent API](/docs/apm/agents/net-agent/net-agent-api/net-agent-api/#ITransaction). Date: Fri, 25 Oct 2024 09:13:24 -0700 Subject: [PATCH 02/22] Missed the .NET Framework section --- .../getting-started/net-agent-compatibility-requirements.mdx | 2 ++ 1 file changed, 2 insertions(+) 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 a899e27c010..3c8868b3b9b 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 @@ -1555,6 +1555,8 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co + + If your datastore is not listed here, you can add custom instrumentation using the `RecordDatastoreSegment` method in the [.NET agent API](/docs/apm/agents/net-agent/net-agent-api/net-agent-api/#ITransaction). Date: Fri, 25 Oct 2024 10:10:02 -0700 Subject: [PATCH 03/22] fix: wrap `\\` in backticks The backslash is an escape char, so having two in a row in plain text only renders one of the two, you need to wrap it in backticks, or do 4 in a row to render two as intended. --- .../nrql/nrql-tutorials/nrql-tutorial-advanced-functions.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/nrql/nrql-tutorials/nrql-tutorial-advanced-functions.mdx b/src/content/docs/nrql/nrql-tutorials/nrql-tutorial-advanced-functions.mdx index 60c2382547f..490810bb69c 100644 --- a/src/content/docs/nrql/nrql-tutorials/nrql-tutorial-advanced-functions.mdx +++ b/src/content/docs/nrql/nrql-tutorials/nrql-tutorial-advanced-functions.mdx @@ -220,7 +220,7 @@ Discovering events and attributes can help answer questions about your available FACET name ``` - The regular expression engine uses RE2 syntax. If you need to delete characters, you may need to use the double backslashing escape sequences. (e.g. \\). + The regular expression engine uses RE2 syntax. If you need to delete characters, you may need to use the double backslashing escape sequences. (e.g. `\\`). Remember that `RLIKE` has inherently more complexity and less performance than `LIKE`. Only use it when `LIKE` and other filtering functionality fails to fit your needs. From 11c70275c5743fc2875c6c2d26b45361dee92d38 Mon Sep 17 00:00:00 2001 From: Brian Hensley <48165493+brnhensley@users.noreply.github.com> Date: Fri, 25 Oct 2024 10:24:24 -0700 Subject: [PATCH 04/22] fix: type, + small syntax updates --- .../nrql-tutorial-advanced-dashboarding.mdx | 22 +++++++++---------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/src/content/docs/nrql/nrql-tutorials/nrql-tutorial-advanced-dashboarding.mdx b/src/content/docs/nrql/nrql-tutorials/nrql-tutorial-advanced-dashboarding.mdx index 28b3f05bbe5..81fee4690df 100644 --- a/src/content/docs/nrql/nrql-tutorials/nrql-tutorial-advanced-dashboarding.mdx +++ b/src/content/docs/nrql/nrql-tutorials/nrql-tutorial-advanced-dashboarding.mdx @@ -15,7 +15,7 @@ We hope seeing example queries and explanations in the context of your own data You'll learn how to advance your dashboarding by using faceting by case, advanced aggregation functions, the `EXTRAPOLATE` keyword, filtering aggregation functions, and overriding values. Specifically, you'll learn how to use: -* Advanced aggregation functions like `filter()`, `apdex()`, `rate()funnel()`, `histogram()`. +* Advanced aggregation functions like `filter()`, `apdex()`, `rate()`, `funnel()`, `histogram()`. * The `EXTRAPOLATE` clauses. * `FACET CASES()`, including how to use attribute and group matching values. * `filter()` to combine Event Types. @@ -221,14 +221,14 @@ When you include `EXTRAPOLATE` in a query, we calculate the ratio between the re Homogenous data like throughput gets the most out of the `EXTRAPOLATE` function. It has less effect when attempting to extrapolate a count of distinct things (like `uniqueCount()` or `uniques()`). So, `EXTRAPOLATE` only works with NRQL queries that use one of the following aggregator functions: -* apdex -* average -* count -* histogram -* sum -* percentage -* rate -* stddev +* `apdex` +* `average` +* `count` +* `histogram` +* `sum` +* `percentage` +* `rate` +* `stddev` With `EXTRAPOLATE` finished, let's move on to using facet cases. @@ -301,7 +301,7 @@ With `EXTRAPOLATE` finished, let's move on to using facet cases. To make this even more useful, the `eventType()` function tells you which event type the record comes from. You can use this to control your data output. In this example, you can see the total number of `Transaction` and `PageView` events combined, as well as the totals for only `Transaction` and `PageView`. ```sql - SELECT count(*) as 'Combined Events', filter(count(*), WHERE eventType() = 'PageView') as 'Page Views', filter(count(*), WHERE eventType()='Transaction') as 'Transactions' + SELECT count(*) AS 'Combined Events', filter(count(*), WHERE eventType() = 'PageView') AS 'Page Views', filter(count(*), WHERE eventType()='Transaction') AS 'Transactions' FROM Transaction, PageView SINCE 1 day ago ``` @@ -317,7 +317,7 @@ With `EXTRAPOLATE` finished, let's move on to using facet cases. Let's look at this in more detail: `count(*)` shows the total number of both `Transaction` and `PageView` events. However, you can use the aggregator function `filter()` you recently learned about to do something unique. The query has `WHERE eventType()='PageView'`, which invokes the filter function to observe the event type as part of the total result set. It then filters to display only those specific events. You can even add `TIMESERIES` to visualize 2 directly comparable data points on a line graph. ```sql - SELECT count(*) as 'Combined Events', filter(count(*), WHERE eventType() = 'PageView') as 'Page Views', filter(count(*), WHERE eventType()='Transaction') as 'Transactions' + SELECT count(*) AS 'Combined Events', filter(count(*), WHERE eventType() = 'PageView') AS 'Page Views', filter(count(*), WHERE eventType()='Transaction') AS 'Transactions' FROM Transaction SINCE 1 day ago TIMESERIES max From e928b9dd5918c4f7dfe66df3b78f6b5fb6eaef60 Mon Sep 17 00:00:00 2001 From: Brian Hensley <48165493+brnhensley@users.noreply.github.com> Date: Fri, 25 Oct 2024 10:28:44 -0700 Subject: [PATCH 05/22] fix: typos --- .../nrql/nrql-tutorials/nrql-tutorial-process-your-data.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/nrql/nrql-tutorials/nrql-tutorial-process-your-data.mdx b/src/content/docs/nrql/nrql-tutorials/nrql-tutorial-process-your-data.mdx index 6e7bd1233f6..902bbcbebe8 100644 --- a/src/content/docs/nrql/nrql-tutorials/nrql-tutorial-process-your-data.mdx +++ b/src/content/docs/nrql/nrql-tutorials/nrql-tutorial-process-your-data.mdx @@ -31,7 +31,7 @@ Let's get started! - After completing the first [first NRQL tutorial](/docs/query-your-data/nrql-new-relic-query-language/get-started/introduction-nrql-tutorial/), you've used `count()`, `average()`, `sum()`, `max()` and `min()` to transform your data in meaningful ways. But what if you want to find and count unique values? To find the number of unique values recorded for an attribute over a specified time range, you can use the `uniqueCount() function`. You only need to provide the attribute we want to inspect as an argument. For instance, here is a query to display all the unique public API calls: + After completing the first [first NRQL tutorial](/docs/query-your-data/nrql-new-relic-query-language/get-started/introduction-nrql-tutorial/), you've used `count()`, `average()`, `sum()`, `max()` and `min()` to transform your data in meaningful ways. But what if you want to find and count unique values? To find the number of unique values recorded for an attribute over a specified time range, you can use the `uniqueCount()` function. You only need to provide the attribute we want to inspect as an argument. For instance, here is a query to display all the unique public API calls: @@ -441,7 +441,7 @@ You can now control your data and manipulate it to do what you need, allowing yo - Sometimes you might receive an event time in epoch (unix) time. Conveniently, you can use epoch timestamps with`SINCE` and `UNTIL` clauses so you don't have to manually translate these values into another date format. + Sometimes you might receive an event time in epoch (unix) time. Conveniently, you can use epoch timestamps with `SINCE` and `UNTIL` clauses so you don't have to manually translate these values into another date format. ```sql SELECT average(duration) From 18023b7ffa5272681f306bcabac58a0f0cff4726 Mon Sep 17 00:00:00 2001 From: Brian Hensley <48165493+brnhensley@users.noreply.github.com> Date: Fri, 25 Oct 2024 10:34:25 -0700 Subject: [PATCH 06/22] chore: wrapping code in backticks --- .../docs/nrql/nrql-tutorials/introduction-nrql-tutorial.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/nrql/nrql-tutorials/introduction-nrql-tutorial.mdx b/src/content/docs/nrql/nrql-tutorials/introduction-nrql-tutorial.mdx index 873e07d9de3..1dc29c4ae30 100644 --- a/src/content/docs/nrql/nrql-tutorials/introduction-nrql-tutorial.mdx +++ b/src/content/docs/nrql/nrql-tutorials/introduction-nrql-tutorial.mdx @@ -230,7 +230,7 @@ Ready to get started? Let's go! - You can also specify time ranges relative to when you make queries by using keywords like `day`, `week`, `hour`, `minute`, or their plural equivalents. You can also use logical expressions like `SINCE` today or `SINCE` this week. + You can also specify time ranges relative to when you make queries by using keywords like `day`, `week`, `hour`, `minute`, or their plural equivalents. You can also use logical expressions like `SINCE today` or `SINCE this week`. @@ -330,7 +330,7 @@ Ready to get started? Let's go! src="/images/queries-nrql_screenshot-crop-tutorial-14.webp" /> - Now you've reached new levels of data visualization, breaking out from summarized numbers to line charts of data trends over time. As you can see, using `TIMESERIES` offers full control over visualizations, granularity, and averaging data over specified windows. It's time for the next step: using the 'Where' clause. + Now you've reached new levels of data visualization, breaking out from summarized numbers to line charts of data trends over time. As you can see, using `TIMESERIES` offers full control over visualizations, granularity, and averaging data over specified windows. It's time for the next step: using the `WHERE` clause. From f94b1a6620e4872439f17b9fb6a05e32e276da55 Mon Sep 17 00:00:00 2001 From: Brian Hensley <48165493+brnhensley@users.noreply.github.com> Date: Fri, 25 Oct 2024 15:35:12 -0700 Subject: [PATCH 07/22] chore: cli commands in backticks --- .../diagnostics-cli-nrdiag/interpret-nrdiag-output.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/new-relic-solutions/solve-common-issues/diagnostics-cli-nrdiag/interpret-nrdiag-output.mdx b/src/content/docs/new-relic-solutions/solve-common-issues/diagnostics-cli-nrdiag/interpret-nrdiag-output.mdx index 92a3c3a9d71..8e48462878e 100644 --- a/src/content/docs/new-relic-solutions/solve-common-issues/diagnostics-cli-nrdiag/interpret-nrdiag-output.mdx +++ b/src/content/docs/new-relic-solutions/solve-common-issues/diagnostics-cli-nrdiag/interpret-nrdiag-output.mdx @@ -10,7 +10,7 @@ redirects: freshnessValidatedDate: never --- -After executing the Diagnostics CLI from your terminal, you will see the results for each task as they are completed. Tasks that result in a `Warning` or `Failure` status code will log additional details regarding possible issues found during execution, along with troubleshooting suggestions and relevant links to documentation. If you use the [-attach or -api-key](/docs/new-relic-solutions/solve-common-issues/diagnostics-cli-nrdiag/pass-command-line-options-nrdiag) flag, you can view your results in [the UI](/docs/using-new-relic/cross-product-functions/diagnostics-cli-nrdiag/interpret-nrdiag-output/#diag-in-nr1) +After executing the Diagnostics CLI from your terminal, you will see the results for each task as they are completed. Tasks that result in a `Warning` or `Failure` status code will log additional details regarding possible issues found during execution, along with troubleshooting suggestions and relevant links to documentation. If you use the [`-attach` or `-api-key`](/docs/new-relic-solutions/solve-common-issues/diagnostics-cli-nrdiag/pass-command-line-options-nrdiag) flag, you can view your results in [the UI](/docs/using-new-relic/cross-product-functions/diagnostics-cli-nrdiag/interpret-nrdiag-output/#diag-in-nr1) Date: Fri, 25 Oct 2024 15:36:38 -0700 Subject: [PATCH 08/22] chore: add syntax highlighting --- .../validate-config-file-settings-nrdiag.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/new-relic-solutions/solve-common-issues/diagnostics-cli-nrdiag/validate-config-file-settings-nrdiag.mdx b/src/content/docs/new-relic-solutions/solve-common-issues/diagnostics-cli-nrdiag/validate-config-file-settings-nrdiag.mdx index a49a1fa3554..6ec2432c91c 100644 --- a/src/content/docs/new-relic-solutions/solve-common-issues/diagnostics-cli-nrdiag/validate-config-file-settings-nrdiag.mdx +++ b/src/content/docs/new-relic-solutions/solve-common-issues/diagnostics-cli-nrdiag/validate-config-file-settings-nrdiag.mdx @@ -20,7 +20,7 @@ You can also use this feature as a linter to validate a config file before deplo For example, if your `newrelic.yml` and `nrdiag` are both in the current directory, run the following command to lint the config file: -``` +```shell ./nrdiag -t Java/Config/ValidateSettings -c newrelic.yml ``` From bb151b1d12a5b03f4b37a3df4e77b69555e45848 Mon Sep 17 00:00:00 2001 From: Brian Hensley <48165493+brnhensley@users.noreply.github.com> Date: Fri, 25 Oct 2024 15:38:38 -0700 Subject: [PATCH 09/22] chore: cli commands in backticks --- .../diagnostics-cli-nrdiag/diagnostics-cli-nrdiag.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/new-relic-solutions/solve-common-issues/diagnostics-cli-nrdiag/diagnostics-cli-nrdiag.mdx b/src/content/docs/new-relic-solutions/solve-common-issues/diagnostics-cli-nrdiag/diagnostics-cli-nrdiag.mdx index 630cae918bf..4adc93634d6 100644 --- a/src/content/docs/new-relic-solutions/solve-common-issues/diagnostics-cli-nrdiag/diagnostics-cli-nrdiag.mdx +++ b/src/content/docs/new-relic-solutions/solve-common-issues/diagnostics-cli-nrdiag/diagnostics-cli-nrdiag.mdx @@ -47,7 +47,7 @@ The Diagnostics CLI does not require `superuser` or `admin` permissions to run, To use the Diagnostics CLI: 1. Run the Diagnostics CLI, including [task suites](/docs/new-relic-solutions/solve-common-issues/diagnostics-cli-nrdiag/run-diagnostics-cli-nrdiag) and [command line options](/docs/using-new-relic/cross-product-functions/diagnostics-cli-nrdiag/pass-command-line-options-nrdiag) as needed. -2. Supply the [-attach or -api-key](/docs/using-new-relic/cross-product-functions/diagnostics-cli-nrdiag/pass-command-line-options-nrdiag) flag for uploading results to your New Relic account. +2. Supply the [`-attach` or `-api-key`](/docs/using-new-relic/cross-product-functions/diagnostics-cli-nrdiag/pass-command-line-options-nrdiag) flag for uploading results to your New Relic account. 3. Optional: Validate your [config file settings](/docs/using-new-relic/cross-product-functions/diagnostics-cli-nrdiag/validate-config-file-settings-nrdiag). 4. Interpret the [output](/docs/using-new-relic/cross-product-functions/diagnostics-cli-nrdiag/interpret-nrdiag-output). From da8c18d6c5d84df46bf7d5db2f59774ed606c824 Mon Sep 17 00:00:00 2001 From: Brian Hensley <48165493+brnhensley@users.noreply.github.com> Date: Fri, 25 Oct 2024 15:43:00 -0700 Subject: [PATCH 10/22] choreL add syntax highlighting --- .../run-diagnostics-cli-nrdiag.mdx | 90 +++++++++---------- 1 file changed, 45 insertions(+), 45 deletions(-) diff --git a/src/content/docs/new-relic-solutions/solve-common-issues/diagnostics-cli-nrdiag/run-diagnostics-cli-nrdiag.mdx b/src/content/docs/new-relic-solutions/solve-common-issues/diagnostics-cli-nrdiag/run-diagnostics-cli-nrdiag.mdx index 29145e6d1b7..2113f8ef2e0 100644 --- a/src/content/docs/new-relic-solutions/solve-common-issues/diagnostics-cli-nrdiag/run-diagnostics-cli-nrdiag.mdx +++ b/src/content/docs/new-relic-solutions/solve-common-issues/diagnostics-cli-nrdiag/run-diagnostics-cli-nrdiag.mdx @@ -29,7 +29,7 @@ The Diagnostics CLI can be installed and run with a single command on Linux and > 1. Change directory to the application's root directory. 2. Execute the following: - ``` + ```shell curl -Ls https://download.newrelic.com/nrdiag/scripts/install.sh | bash && sudo ./nrdiag CLI_OPTIONS ``` Recommendation: Scope your troubleshooting with a [task suite](#suites) (`-suites`), and upload relevant files to your New Relic account with the [attachment flag](#automatic) (`-attach`). @@ -41,7 +41,7 @@ The Diagnostics CLI can be installed and run with a single command on Linux and > 1. Change directory to the application's root directory. 2. Execute the following: - ``` + ```powershell [Net.ServicePointManager]::SecurityProtocol = 'tls12, tls'; (New-Object System.Net.WebClient).DownloadFile("https://download.newrelic.com/nrdiag/scripts/install.ps1", "$env:TEMP\install.ps1"); & PowerShell.exe -ExecutionPolicy Bypass -File $env:TEMP\install.ps1; & '.\nrdiag.exe' CLI_OPTIONS ``` Recommendation: Scope your troubleshooting with a [task suite](#suites) (`-suites`), and upload relevant files to your New Relic account with the [attachment flag](#automatic) (`-attach`). @@ -67,7 +67,7 @@ To manually install and run the Diagnostics CLI, follow the procedures for your 3. From the `nrdiag_1.2.3/linux` directory, move `nrdiag` into the application's root directory. 4. Run `nrdiag` (along with any [CLI options](/docs/using-new-relic/cross-product-functions/diagnostics-cli-nrdiag/pass-command-line-options-nrdiag) - ``` + ```shell ./nrdiag CLI_OPTIONS ``` @@ -91,13 +91,13 @@ To manually install and run the Diagnostics CLI, follow the procedures for your Run via PowerShell if you add any `CLI_OPTIONS`: - ``` + ```shell ./nrdiag.exe CLI_OPTIONS ``` **OR**, for x64 systems: - ``` + ```shell ./nrdiag_x64.exe CLI_OPTIONS ``` @@ -118,7 +118,7 @@ To manually install and run the Diagnostics CLI, follow the procedures for your 3. From the `nrdiag_1.2.3/mac` directory, move `nrdiag` into the application's root directory. 4. Run `nrdiag` (along with any [CLI options](/docs/using-new-relic/cross-product-functions/diagnostics-cli-nrdiag/pass-command-line-options-nrdiag) - ``` + ```shell ./nrdiag CLI_OPTIONS ``` @@ -133,7 +133,7 @@ To manually install and run the Diagnostics CLI, follow the procedures for your 2. Unzip `nrdiag.zip` if necessary. 3. From the `nrdiag_1.2.3/`OS directory, run `nrdiag` (along with any [CLI options](/docs/using-new-relic/cross-product-functions/diagnostics-cli-nrdiag/pass-command-line-options-nrdiag): - ``` + ```shell ./nrdiag -browser-url WEBSITE_URL CLI_OPTIONS ``` @@ -149,17 +149,17 @@ To manually install and run the Diagnostics CLI, follow the procedures for your 1. [Download](https://download.newrelic.com/nrdiag/nrdiag_latest.zip) and unzip the `nrdiag_latest.zip` file. 2. Copy the binary to the container. Replace `IMAGE_NAME` with the name of your docker container: - ``` + ```shell docker cp nrdiag/linux/nrdiag IMAGE_NAME:/bin ``` 3. Run the `nrdiag` command in the docker container. Replace `IMAGE_NAME` as above, and replace `APPLICATION_ROOT` with the root directory of your application, where you installed the New Relic agent: - ``` + ```shell docker exec -it -w APPLICATION_ROOT IMAGE_NAME nrdiag ``` 4. (Optional) Remove the `nrdiag` binary when finished: - ``` + ```shell docker exec IMAGE_NAME rm /bin/nrdiag ``` @@ -171,7 +171,7 @@ A suite is a collection of health checks that target specific products or issues To review a list of available suites, run the Diagnostics CLI with the `-help suites` option: -``` +```shell ./nrdiag -help suites ``` @@ -183,12 +183,12 @@ To run suites with `nrdiag`, provide the `-suites` flag and one or more suite na * For 64-bit systems: - ``` + ```shell ./nrdiag_x64 -suites SUITE NAMES ``` * For ARM64 systems: - ``` + ```shell ./nrdiag_arm64 -suites SUITE NAMES ``` @@ -200,17 +200,17 @@ To run from PowerShell, add `./` to the start of `cmd`. * For 32-bit systems: - ``` + ```shell nrdiag.exe -suites SUITE NAMES ``` * For 64-bit systems: - ``` + ```shell nrdiag_x64.exe -suites SUITE NAMES ``` * For ARM64 systems: - ``` + ```shell nrdiag_arm64.exe -suites SUITE NAMES ``` @@ -230,14 +230,14 @@ The results of running a script can be found in the `nrdiag-output.json` file wi ```json "Script": { - "Name": "example", - "Description": "Example Description", - "Output": "example output", - "OutputFiles": [ - "/path/to/example.out", - "/path/to/another-file.out" - ], - "OutputTruncated": false + "Name": "example", + "Description": "Example Description", + "Output": "example output", + "OutputFiles": [ + "/path/to/example.out", + "/path/to/another-file.out" + ], + "OutputTruncated": false } ``` @@ -254,7 +254,7 @@ A list of files the script created can be found in the `Outputfiles` field. > To view a list of the scripts available to run, use `-list-scripts`: - ``` + ```shell ./nrdiag -list-scripts ``` @@ -265,7 +265,7 @@ A list of files the script created can be found in the `Outputfiles` field. > To view a script without running it: - ``` + ```shell ./nrdiag -script SCRIPT_NAME ``` @@ -276,7 +276,7 @@ A list of files the script created can be found in the `Outputfiles` field. > To run a script: - ``` + ```shell ./nrdiag -script SCRIPT_NAME -run ``` @@ -287,7 +287,7 @@ A list of files the script created can be found in the `Outputfiles` field. > To run a script with arguments: - ``` + ```shell ./nrdiag -script SCRIPT_NAME -run -script-flags "-foo bar" ``` @@ -298,7 +298,7 @@ A list of files the script created can be found in the `Outputfiles` field. > To run a script and suites at the same time: - ``` + ```shell ./nrdiag -script SCRIPT_NAME -run -s SUITE NAMES" ``` @@ -316,12 +316,12 @@ Use this in combination with `-attach` to [upload the files](#attach-account-res * For 64-bit systems: - ``` + ```shell ./nrdiag_x64 -include /entire/directory/ -attach ``` * For ARM64 systems: - ``` + ```shell ./nrdiag_arm64 -include /entire/directory/ -attach ``` @@ -333,19 +333,19 @@ To run from PowerShell, add `./` to the start of `cmd`. * For 32-bit systems: - ``` + ```shell nrdiag.exe -include Path\To\File -attach ``` * For 64-bit systems: - ``` + ```shell nrdiag_x64.exe -include \Entire\Directory\ -attach ``` * For ARM64 systems: - ``` + ```shell nrdiag_arm64.exe -include \Entire\Directory\ -attach ``` @@ -368,24 +368,24 @@ Uploading your results to an account will automatically upload the contents of t > * For 64-bit systems: - ``` + ```shell ./nrdiag_x64 -attach ``` OR - ``` + ```shell ./nrdiag_x64 -api-key ${API_KEY} ``` * For ARM64 systems: - ``` + ```shell ./nrdiag_arm64 -attach ``` OR - ``` + ```shell ./nrdiag_arm64 -api-key ${API_KEY} ``` @@ -398,35 +398,35 @@ Uploading your results to an account will automatically upload the contents of t * For 32-bit systems: - ``` + ```shell nrdiag.exe -attach ``` OR - ``` + ```shell nrdiag.exe -api-key ${API_KEY} ``` * For 64-bit systems: - ``` + ```shell nrdiag_x64.exe -attach ``` OR - ``` + ```shell nrdiag_x64.exe -api-key ${API_KEY} ``` * For ARM64 systems: - ``` + ```shell nrdiag_arm64.exe -attach ``` OR - ``` + ```shell nrdiag_arm64.exe -api-key ${API_KEY} ``` @@ -436,6 +436,6 @@ Uploading your results to an account will automatically upload the contents of t By default, the Diagnostics CLI uploads results to New Relic accounts hosted in the US data center. If your account is hosted in the EU data center, ensure to add `-region eu` to the command. -``` +```shell ./nrdiag -region eu ... ``` From f27725f08cb79e0923dc3b71e60e28431b6ea774 Mon Sep 17 00:00:00 2001 From: cehme <135249189+cehme@users.noreply.github.com> Date: Mon, 28 Oct 2024 11:21:29 -0400 Subject: [PATCH 11/22] docs: updating percentage() docs --- src/content/docs/nrql/nrql-syntax-clauses-functions.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/nrql/nrql-syntax-clauses-functions.mdx b/src/content/docs/nrql/nrql-syntax-clauses-functions.mdx index 0811aa78153..573f9a6c764 100644 --- a/src/content/docs/nrql/nrql-syntax-clauses-functions.mdx +++ b/src/content/docs/nrql/nrql-syntax-clauses-functions.mdx @@ -1872,7 +1872,7 @@ SELECT histogram(duration, 10, 20) FROM PageView SINCE 1 week ago > Use the `percentage()` function to return the percentage of a target data set that matches some condition. - The first argument requires an [aggregator function](#functions) against the desired attribute. Use exactly two arguments (arguments after the first two will be ignored). If the attribute is not numeric, this function returns a value of 100%. + This function expects exactly two arguments (arguments after the first two will be ignored). The first argument requires an [aggregator function](#functions) against the desired attribute. If the attribute is not numeric, this function returns a value of 100%. The second argument requires a where clause. ```sql FROM Transaction From ea8fd4c2a292e2d4a386f7c41463ab8d64dc2461 Mon Sep 17 00:00:00 2001 From: Brian Hensley <48165493+brnhensley@users.noreply.github.com> Date: Mon, 28 Oct 2024 08:24:48 -0700 Subject: [PATCH 12/22] fix: typo & capitalize nrql clauses --- .../view-query-data/translate-promql-queries-nrql.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/content/docs/infrastructure/prometheus-integrations/view-query-data/translate-promql-queries-nrql.mdx b/src/content/docs/infrastructure/prometheus-integrations/view-query-data/translate-promql-queries-nrql.mdx index 36e19b4307e..caf8f6d1195 100644 --- a/src/content/docs/infrastructure/prometheus-integrations/view-query-data/translate-promql-queries-nrql.mdx +++ b/src/content/docs/infrastructure/prometheus-integrations/view-query-data/translate-promql-queries-nrql.mdx @@ -325,10 +325,10 @@ This table shows the mapping between NRQL and our PromQL-style queries when expl **5. Add the selected ID to the query.** - Next you can select an `id` value and put it in the NRQL `where` clause. + Next you can select an `id` value and put it in the NRQL `WHERE` clause. ```sql - FROM Metric SELECT latest(container_memory_usage_bytes) WHERE id = "/" timeseries + FROM Metric SELECT latest(container_memory_usage_bytes) WHERE id = "/" TIMESERIES ```
- **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Query your data**: This example shows the data displayed after running `From Metric select latest(container_memory_usage_bytes) where id = "/" timeseries`. + **[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Query your data**: This example shows the data displayed after running `From Metric select latest(container_memory_usage_bytes) where id = "/" TIMESERIES`.
@@ -425,7 +425,7 @@ Here are some example queries: In NRQL use the `LIKE` clause to match part of a string value. In this example, all data will be returned where the job attributes start with `api`. ```sql - FROM Metric SELECT latest(go_memstats_heap_alloc_bytes) WHEREe job LIKE 'api%' TIMESERIES + FROM Metric SELECT latest(go_memstats_heap_alloc_bytes) WHERE job LIKE 'api%' TIMESERIES ``` From 1028bc636caf0dca5243e803a5e261bb9e7a69cb Mon Sep 17 00:00:00 2001 From: David Hersh Date: Mon, 28 Oct 2024 11:32:54 -0400 Subject: [PATCH 13/22] Update Ruby extension --- .../docs/codestream/observability/code-level-metrics.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/codestream/observability/code-level-metrics.mdx b/src/content/docs/codestream/observability/code-level-metrics.mdx index b21568d05c9..259fec5b13f 100644 --- a/src/content/docs/codestream/observability/code-level-metrics.mdx +++ b/src/content/docs/codestream/observability/code-level-metrics.mdx @@ -50,6 +50,6 @@ To see in-editor performance data, your service must meet the requirements liste * **Node.js:** Requires Node.js agent version 10.5.0 or higher. If your codebase include anonymous functions you'll need to either use [change tracking](/docs/change-tracking/change-tracking-introduction/) to send deployment information to New Relic, or you'll need to [send your build SHA via an environment variable](/docs/codestream/observability/error-investigation/#buildsha) in your build pipeline. * **PHP:** Requires PHP agent version 10.6.0 or higher. If you're using VS Code, you must also have the [PHP Intelephense](https://marketplace.visualstudio.com/items?itemName=bmewburn.vscode-intelephense-client) extension installed. * **Python:** Requires Python agent version 7.10.0.175 or higher. Code-level metrics are only available for projects implemented with a [supported Python framework](/docs/apm/agents/python-agent/getting-started/instrumented-python-packages) and for PHP version 7.0 or higher. If you're using VS Code, you must also have the [Python](https://marketplace.visualstudio.com/items?itemName=ms-python.python) extension installed with the language server enabled. -* **Ruby:** Requires Ruby agent version 8.10.0 or higher. Code-level metrics are only available for Rails applications and Ruby methods with manual traces ([learn more about Ruby methods and CodeStream](/docs/apm/agents/ruby-agent/features/ruby-codestream-integration)). If you're using VS Code, you must also have either the [Ruby](https://marketplace.visualstudio.com/items?itemName=rebornix.Ruby) or [Ruby Solargraph](https://marketplace.visualstudio.com/items?itemName=castwide.solargraph) extension installed with the language server enabled. +* **Ruby:** Requires Ruby agent version 8.10.0 or higher. Code-level metrics are only available for Rails applications and Ruby methods with manual traces ([learn more about Ruby methods and CodeStream](/docs/apm/agents/ruby-agent/features/ruby-codestream-integration)). If you're using VS Code, you must also have the [Ruby LSP](https://marketplace.visualstudio.com/items?itemName=Shopify.ruby-lsp) extension installedd. You can turn CodeLenses off by going to the CodeStream section of your IDE's settings and unchecking the **CodeStream: Show Golden Signals In Editor** setting. From 2b25fa2235c63df6df0f4e15e45115775a018cb1 Mon Sep 17 00:00:00 2001 From: cehme <135249189+cehme@users.noreply.github.com> Date: Mon, 28 Oct 2024 11:38:07 -0400 Subject: [PATCH 14/22] docs: typo in funnels doc --- .../using-nrql/funnels-evaluate-data-series-related-events.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/nrql/using-nrql/funnels-evaluate-data-series-related-events.mdx b/src/content/docs/nrql/using-nrql/funnels-evaluate-data-series-related-events.mdx index 59e6457b98c..98b7f2da18e 100644 --- a/src/content/docs/nrql/using-nrql/funnels-evaluate-data-series-related-events.mdx +++ b/src/content/docs/nrql/using-nrql/funnels-evaluate-data-series-related-events.mdx @@ -39,7 +39,7 @@ FROM DATA_TYPE Funnel queries require the [`funnel` function](/docs/query-data/nrql-new-relic-query-language/getting-started/nrql-syntax-components-functions#func-funnel), an [attribute](/docs/using-new-relic/welcome-new-relic/get-started/glossary#attribute) to funnel, and at least two steps: 1. Begin with the anchor step, which always represents 100% of the results. -2. Continue with an additional step or steps that describe the number of users who have also completed additional actions, typically than the 100% from the anchor step. However, it could be 100% if every user who completes action (A) also completes the additional actions you're querying. +2. Continue with an additional step or steps that describe the number of users who have also completed additional actions, typically less than the 100% from the anchor step. However, it could be 100% if every user who completes action (A) also completes the additional actions you're querying. ## Funnel query technical details From 26d3622311ae36186a9b69d2afb3c3c945c0a606 Mon Sep 17 00:00:00 2001 From: David Hersh Date: Mon, 28 Oct 2024 12:04:18 -0400 Subject: [PATCH 15/22] Fix typo --- .../docs/codestream/observability/code-level-metrics.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/codestream/observability/code-level-metrics.mdx b/src/content/docs/codestream/observability/code-level-metrics.mdx index 259fec5b13f..fc471a41610 100644 --- a/src/content/docs/codestream/observability/code-level-metrics.mdx +++ b/src/content/docs/codestream/observability/code-level-metrics.mdx @@ -50,6 +50,6 @@ To see in-editor performance data, your service must meet the requirements liste * **Node.js:** Requires Node.js agent version 10.5.0 or higher. If your codebase include anonymous functions you'll need to either use [change tracking](/docs/change-tracking/change-tracking-introduction/) to send deployment information to New Relic, or you'll need to [send your build SHA via an environment variable](/docs/codestream/observability/error-investigation/#buildsha) in your build pipeline. * **PHP:** Requires PHP agent version 10.6.0 or higher. If you're using VS Code, you must also have the [PHP Intelephense](https://marketplace.visualstudio.com/items?itemName=bmewburn.vscode-intelephense-client) extension installed. * **Python:** Requires Python agent version 7.10.0.175 or higher. Code-level metrics are only available for projects implemented with a [supported Python framework](/docs/apm/agents/python-agent/getting-started/instrumented-python-packages) and for PHP version 7.0 or higher. If you're using VS Code, you must also have the [Python](https://marketplace.visualstudio.com/items?itemName=ms-python.python) extension installed with the language server enabled. -* **Ruby:** Requires Ruby agent version 8.10.0 or higher. Code-level metrics are only available for Rails applications and Ruby methods with manual traces ([learn more about Ruby methods and CodeStream](/docs/apm/agents/ruby-agent/features/ruby-codestream-integration)). If you're using VS Code, you must also have the [Ruby LSP](https://marketplace.visualstudio.com/items?itemName=Shopify.ruby-lsp) extension installedd. +* **Ruby:** Requires Ruby agent version 8.10.0 or higher. Code-level metrics are only available for Rails applications and Ruby methods with manual traces ([learn more about Ruby methods and CodeStream](/docs/apm/agents/ruby-agent/features/ruby-codestream-integration)). If you're using VS Code, you must also have the [Ruby LSP](https://marketplace.visualstudio.com/items?itemName=Shopify.ruby-lsp) extension installed. You can turn CodeLenses off by going to the CodeStream section of your IDE's settings and unchecking the **CodeStream: Show Golden Signals In Editor** setting. From 36ea32e13bdde0a21ee68fb3050b95ff81a011a4 Mon Sep 17 00:00:00 2001 From: Asia Kane <26093145+akane0915@users.noreply.github.com> Date: Mon, 28 Oct 2024 09:29:08 -0700 Subject: [PATCH 16/22] fix(Alerts): Update NRAI attribute information --- .../condition-details/incident-event-attributes.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/alerts/create-alert/condition-details/incident-event-attributes.mdx b/src/content/docs/alerts/create-alert/condition-details/incident-event-attributes.mdx index 3dc5147af14..392a63ac2b5 100644 --- a/src/content/docs/alerts/create-alert/condition-details/incident-event-attributes.mdx +++ b/src/content/docs/alerts/create-alert/condition-details/incident-event-attributes.mdx @@ -167,7 +167,7 @@ All attributes are available for use in a [description](/docs/alerts/new-relic-a The contents of the active condition's `Violation Description` field. - NRQL or infrastructure conditions only. + NRQL or infrastructure conditions only. Not available for use with Alert condition [title template](docs/alerts/create-alert/condition-details/title-template) or [description template](/docs/alerts/create-alert/condition-details/alert-custom-incident-descriptions). @@ -256,7 +256,7 @@ All attributes are available for use in a [description](/docs/alerts/new-relic-a - The unique identifier of the incident. + The unique identifier of the incident. Not available for use with Alert condition [title template](docs/alerts/create-alert/condition-details/title-template) or [description template](/docs/alerts/create-alert/condition-details/alert-custom-incident-descriptions). From 8f390d851bf78eb31e77e0e327edd261a0dc8269 Mon Sep 17 00:00:00 2001 From: Gaurab Manandhar Date: Mon, 28 Oct 2024 22:00:00 +0530 Subject: [PATCH 17/22] chore: update gatsby-theme-newrelic version --- package.json | 2 +- yarn.lock | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/package.json b/package.json index 8b488d66eb5..717e00d3512 100644 --- a/package.json +++ b/package.json @@ -10,7 +10,7 @@ "@emotion/styled": "^11.3.0", "@mdx-js/mdx": "2.0.0-next.8", "@mdx-js/react": "2.0.0-next.8", - "@newrelic/gatsby-theme-newrelic": "9.10.5", + "@newrelic/gatsby-theme-newrelic": "9.10.6", "@splitsoftware/splitio-react": "^1.2.4", "ansi-colors": "^4.1.3", "cockatiel": "^3.0.0-beta.0", diff --git a/yarn.lock b/yarn.lock index 9824fa2f84b..7b95a790ba2 100644 --- a/yarn.lock +++ b/yarn.lock @@ -3616,10 +3616,10 @@ eslint-plugin-promise "^4.2.1" eslint-plugin-react "^7.14.3" -"@newrelic/gatsby-theme-newrelic@9.10.5": - version "9.10.5" - resolved "https://registry.yarnpkg.com/@newrelic/gatsby-theme-newrelic/-/gatsby-theme-newrelic-9.10.5.tgz#ef82ba58fde45e778bdc84488ff161f6c5fd1a36" - integrity sha512-95GD/fWH/i6hYjY89+n9LTtPIE+Cf505tWtCbIjKRZ82szsDtr+nghDbh6anc1M3iK89VYHF6FY15LkuDvGB7g== +"@newrelic/gatsby-theme-newrelic@9.10.6": + version "9.10.6" + resolved "https://registry.yarnpkg.com/@newrelic/gatsby-theme-newrelic/-/gatsby-theme-newrelic-9.10.6.tgz#7e64720873db48050891697644d332965924e279" + integrity sha512-amRd4W+P8vdhsyXAIfP80xFiway7i2wHGfBP8/LoyKZWsFiKbhiKvbuOGyjtOwn4aB51svj6DQwUQuH5NEbFOQ== dependencies: "@segment/analytics-next" "1.63.0" "@wry/equality" "^0.4.0" From 180f30437d273b84ebb326399c65eb1530515cab Mon Sep 17 00:00:00 2001 From: Shawn Kilburn Date: Mon, 28 Oct 2024 09:55:12 -0700 Subject: [PATCH 18/22] fix(Kubernetes): Fixed broken HAProxy link --- .../monitor-services/monitor-services-running-kubernetes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/monitor-services/monitor-services-running-kubernetes.mdx b/src/content/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/monitor-services/monitor-services-running-kubernetes.mdx index 76842665e29..7b9f4eb2125 100644 --- a/src/content/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/monitor-services/monitor-services-running-kubernetes.mdx +++ b/src/content/docs/kubernetes-pixie/kubernetes-integration/advanced-configuration/monitor-services/monitor-services-running-kubernetes.mdx @@ -32,7 +32,7 @@ To monitor services running on Kubernetes, you need: * [Cassandra](/docs/integrations/host-integrations/host-integrations-list/cassandra-monitoring-integration) * [Couchbase](/docs/integrations/host-integrations/host-integrations-list/couchbase-monitoring-integration) * [Elasticsearch](/docs/integrations/host-integrations/host-integrations-list/elasticsearch-monitoring-integration) - * [HAProxy](/docs/integrations/host-integrations/host-integrations-list/haproxy-monitoring-integration) + * [HAProxy](/install/haproxy/) * [HashiCorp Consul](/docs/integrations/host-integrations/host-integrations-list/hashicorp-consul-monitoring-integration) * [JMX](/docs/integrations/host-integrations/host-integrations-list/jmx-monitoring-integration) * [Kafka](/docs/integrations/host-integrations/host-integrations-list/kafka-monitoring-integration) From 2056942af1dba42eb40ec3976f56f35925275d6f Mon Sep 17 00:00:00 2001 From: Shawn Kilburn Date: Mon, 28 Oct 2024 10:02:19 -0700 Subject: [PATCH 19/22] style(.NET): Aligned to style guide --- .../getting-started/net-agent-compatibility-requirements.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 3c8868b3b9b..aea4e3efa7e 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 @@ -591,7 +591,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co Collecting [instance details](/docs/apm/applications-menu/features/analyze-database-instance-level-performance-issues) for supported datastores is enabled by default. To request instance-level information from datastores not currently listed, get support at [support.newrelic.com](https://support.newrelic.com). - If your datastore is not listed here, you can add custom instrumentation using the `RecordDatastoreSegment` method in the [.NET agent API](/docs/apm/agents/net-agent/net-agent-api/net-agent-api/#ITransaction). + If your datastore isn't listed here, you can add custom instrumentation using the `RecordDatastoreSegment` method in the [.NET agent API](/docs/apm/agents/net-agent/net-agent-api/net-agent-api/#ITransaction). Date: Mon, 28 Oct 2024 10:02:37 -0700 Subject: [PATCH 20/22] style(.NET): Aligned to style guide --- .../getting-started/net-agent-compatibility-requirements.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 aea4e3efa7e..3240adf38d1 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 @@ -1556,7 +1556,7 @@ Want to try out our .NET agent? [Create a New Relic account](https://newrelic.co - If your datastore is not listed here, you can add custom instrumentation using the `RecordDatastoreSegment` method in the [.NET agent API](/docs/apm/agents/net-agent/net-agent-api/net-agent-api/#ITransaction). + If your datastore isn't listed here, you can add custom instrumentation using the `RecordDatastoreSegment` method in the [.NET agent API](/docs/apm/agents/net-agent/net-agent-api/net-agent-api/#ITransaction). Date: Mon, 28 Oct 2024 10:45:50 -0700 Subject: [PATCH 21/22] style(NRQL): Slight tweaks to align to our style guide --- src/content/docs/nrql/nrql-syntax-clauses-functions.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/nrql/nrql-syntax-clauses-functions.mdx b/src/content/docs/nrql/nrql-syntax-clauses-functions.mdx index 573f9a6c764..d5a7f68548b 100644 --- a/src/content/docs/nrql/nrql-syntax-clauses-functions.mdx +++ b/src/content/docs/nrql/nrql-syntax-clauses-functions.mdx @@ -1872,7 +1872,7 @@ SELECT histogram(duration, 10, 20) FROM PageView SINCE 1 week ago > Use the `percentage()` function to return the percentage of a target data set that matches some condition. - This function expects exactly two arguments (arguments after the first two will be ignored). The first argument requires an [aggregator function](#functions) against the desired attribute. If the attribute is not numeric, this function returns a value of 100%. The second argument requires a where clause. + This function expects exactly two arguments (arguments after the first two are ignored). The first argument requires an [aggregator function](#functions) against the desired attribute. If the attribute is not numeric, this function returns a value of 100%. The second argument requires a `WHERE` clause. ```sql FROM Transaction From d7aa29deb47f315b7617023f63c33d3886aba779 Mon Sep 17 00:00:00 2001 From: Shawn Kilburn Date: Mon, 28 Oct 2024 10:48:20 -0700 Subject: [PATCH 22/22] style(Alerts): Minor tweaks to align to our style guide --- .../condition-details/incident-event-attributes.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/alerts/create-alert/condition-details/incident-event-attributes.mdx b/src/content/docs/alerts/create-alert/condition-details/incident-event-attributes.mdx index 392a63ac2b5..286c8da95b2 100644 --- a/src/content/docs/alerts/create-alert/condition-details/incident-event-attributes.mdx +++ b/src/content/docs/alerts/create-alert/condition-details/incident-event-attributes.mdx @@ -167,7 +167,7 @@ All attributes are available for use in a [description](/docs/alerts/new-relic-a The contents of the active condition's `Violation Description` field. - NRQL or infrastructure conditions only. Not available for use with Alert condition [title template](docs/alerts/create-alert/condition-details/title-template) or [description template](/docs/alerts/create-alert/condition-details/alert-custom-incident-descriptions). + NRQL or infrastructure conditions only. Not available for use with alert condition [title](docs/alerts/create-alert/condition-details/title-template) or [description templates](/docs/alerts/create-alert/condition-details/alert-custom-incident-descriptions). @@ -256,7 +256,7 @@ All attributes are available for use in a [description](/docs/alerts/new-relic-a - The unique identifier of the incident. Not available for use with Alert condition [title template](docs/alerts/create-alert/condition-details/title-template) or [description template](/docs/alerts/create-alert/condition-details/alert-custom-incident-descriptions). + The unique identifier of the incident. Not available for use with alert condition [title](docs/alerts/create-alert/condition-details/title-template) or [description templates](/docs/alerts/create-alert/condition-details/alert-custom-incident-descriptions).