Merge pull request #18733 from newrelic/daily-release/Sep-20-2024-11_51

Daily release/sep 20 2024 11 51

.github/auto_assign.yml

@@ -7,10 +7,10 @@ reviewers:
   - rhetoric101
   - ally-sassman
   - jeff-colucci
-  - bradleycamacho
   - nbaenam
   - cbehera-newrelic
   - akristen
+  - adutta-newrelic
 
 # A number of reviewers added to the pull request
 # Set 0 to add all the reviewers (default: 0)

src/content/docs/alerts/create-alert/condition-details/title-template.mdx

@@ -63,7 +63,7 @@ You can interact with the title template in two ways: through the UI or using Gr
     id="template-ui"
     title="Create a title template in the UI"
   >
-    1. Navigate to the NRQL condition builder. For instructions, see [Alert conditions](docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/alert-conditions/).
+    1. Navigate to the NRQL condition builder. For instructions, see [Alert conditions](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/alert-conditions/).
     2. Create your NRQL condition.
     3. In the final step, **Add details**, enter your title template in the **Title template** field.
     4. Save the condition.

src/content/docs/apm/agents/go-agent/configuration/go-agent-configuration.mdx

@@ -3806,7 +3806,7 @@ Module dependency metrics can be configured in a variety of ways in the Go agent
 
 ## New Relic IAST [#go-IAST]
 
-[New Relic Interactive Applications Security Testing](https://docs.newrelic.com/docs/iast/introduction/) (IAST) tests your applications for any exploitable vulnerability by replaying the generated HTTP request with vulnerable payloads. You can enable New Relic IAST by updating your Go app code with configurations that are passed to the INIT function. You can also make these configurations through a YAML file or with environment variables.
+[New Relic Interactive Applications Security Testing](/docs/iast/introduction/) (IAST) tests your applications for any exploitable vulnerability by replaying the generated HTTP request with vulnerable payloads. You can enable New Relic IAST by updating your Go app code with configurations that are passed to the INIT function. You can also make these configurations through a YAML file or with environment variables.
 
 Options set using INIT functions take precedence over environment or YAML configurations. That said, we recommend enabling IAST using a YAML file because those configurations will pass to other agents in your environment.
 

src/content/docs/apm/agents/nodejs-agent/api-guides/guide-using-nodejs-agent-api.mdx

@@ -410,6 +410,6 @@ You can also control the browser agent via APM agent API calls. For more informa
 
 ## Extend custom instrumentation [#custom-instrumentation]
 
-For more information about using the custom instrumentation APIs, see [Node.js custom instrumentation](docs/apm/agents/nodejs-agent/extend-your-instrumentation/nodejs-custom-instrumentation/).
+For more information about using the custom instrumentation APIs, see [Node.js custom instrumentation](/docs/apm/agents/nodejs-agent/extend-your-instrumentation/nodejs-custom-instrumentation/).
 
 To add custom instrumentation in ES module applications, please refer to our [ES module](/docs/apm/agents/nodejs-agent/installation-configuration/es-modules) documentation or [example application](https://github.com/newrelic/newrelic-node-examples/tree/4284ee7eab69708238db0a44f97ff7e839e165cf/esm-app) in GitHub.

src/content/docs/apm/agents/ruby-agent/api-guides/ruby-custom-instrumentation.mdx

@@ -99,7 +99,7 @@ def slow_action
 end
 ```
 
-For more information, see [add_method_tracer in the New Relic RubyDoc](https://www.rubydoc.info/gems/newrelic_rpm/NewRelic/Agent/MethodTracer#trace_execution_scoped-instance_method). If you aren't sure if a transaction already exists or need to start a new one, see [instrumenting a section of code](https://docs.newrelic.com/docs/apm/agents/ruby-agent/api-guides/ruby-custom-instrumentation/#in-transaction) under Advanced Custom Instrumentation.
+For more information, see [add_method_tracer in the New Relic RubyDoc](https://www.rubydoc.info/gems/newrelic_rpm/NewRelic/Agent/MethodTracer#trace_execution_scoped-instance_method). If you aren't sure if a transaction already exists or need to start a new one, see [instrumenting a section of code](/docs/apm/agents/ruby-agent/api-guides/ruby-custom-instrumentation/#in-transaction) under Advanced Custom Instrumentation.
 
 ## Naming transactions
 

src/content/docs/apm/agents/ruby-agent/api-guides/sending-handled-errors-new-relic.mdx

@@ -224,7 +224,7 @@ Because the API is intended to be called every time a new user ID has entered sc
 
 ## Version tracking: Use metadata to see what version produced an error [#version-tracking]
 
-[Errors inbox](https://docs.newrelic.com/docs/errors-inbox/version-tracking/) will automatically track which versions of your software are producing errors. Any version data will also display in [CodeStream](/docs/codestream/how-use-codestream/performance-monitoring/#buildsha).
+[Errors inbox](/docs/errors-inbox/version-tracking/) will automatically track which versions of your software are producing errors. Any version data will also display in [CodeStream](/docs/codestream/how-use-codestream/performance-monitoring/#buildsha).
 
 Set one of the following environment variables to help identify which versions of your software produce errors.
 

src/content/docs/browser/new-relic-browser/browser-apis/log.mdx

@@ -41,7 +41,7 @@ For more information, see the [npm browser installation documentation](https://w
 
 ## Description [#log-description]
 
-When you execute this function with a valid message and elective options, the browser agent records the data as a single `log` event.  See the [Logs UI](https://docs.newrelic.com/docs/logs/ui-data/use-logs-ui/) for more information about log events. Any custom attributes supplied to the API call in the `options` argument (`options.customAttributes`) will be appended as top-level attributes on the log event. You can control the `level` of the captured log by supplying a `level` to the `options` argument (`options.level`), which defaults to `info`.
+When you execute this function with a valid message and elective options, the browser agent records the data as a single `log` event.  See the [Logs UI](/docs/logs/ui-data/use-logs-ui/) for more information about log events. Any custom attributes supplied to the API call in the `options` argument (`options.customAttributes`) will be appended as top-level attributes on the log event. You can control the `level` of the captured log by supplying a `level` to the `options` argument (`options.level`), which defaults to `info`.
 
 ## Parameters [#log-parameters]
 

src/content/docs/browser/new-relic-browser/browser-apis/wraplogger.mdx

@@ -41,7 +41,7 @@ For more information, see the [npm browser installation documentation](https://w
 
 ## Description [#wrap-description]
 
-After you provide this method with a valid parent container and child function name, the browser agent will record a new log event every time the wrapped function is invoked. The first argument is passed to the invoked function as the log's message. See the [Logs UI](https://docs.newrelic.com/docs/logs/ui-data/use-logs-ui/) for more information about log events.
+After you provide this method with a valid parent container and child function name, the browser agent will record a new log event every time the wrapped function is invoked. The first argument is passed to the invoked function as the log's message. See the [Logs UI](/docs/logs/ui-data/use-logs-ui/) for more information about log events.
 
 Optional configurations can be passed along with these captured logs with the `options` argument. Any custom attributes supplied to the API call in the `options` argument (`options.customAttributes`) will be appended as top-level attributes on every log event created by this wrapper. You can control the `level` of the captured log by supplying a `level` to the `options` argument (`options.level`), which defaults to `info`. Note that once successfully wrapped, the function's logging detection can't be altered.
 

src/content/docs/browser/single-page-app-monitoring/get-started/browser-spa-v2.mdx

@@ -24,8 +24,8 @@ The updated SPA monitoring experience is designed to eliminate these problems an
 * Focus on key metrics: While reported data remains largely unchanged, the new experience no longer tracks JavaScript execution or callback duration within interactions, streamlining the reported information.
 * Reduced interaction durations: Expect significantly shorter interaction durations, particularly for route changes. Initial page loads will see a slight reduction.
 * API updates:
-    * New optional argument `.interaction({waitForEnd: true})` added to the [`.interaction()`](https://docs.newrelic.com/docs/browser/new-relic-browser/browser-apis/interaction/) function: This allows customization of user interaction end time. The existing `.interaction()` functionality remains unchanged.
-    * Deprecated API: The function [`createTracer`](https://docs.newrelic.com/docs/browser/new-relic-browser/browser-apis/createtracer/): While still functional, the `createTracer` function is deprecated as it no longer keeps interactions open or times callbacks. Note: If you continue to use `createTracer` with the new SPA experience,`BrowserTiming` events will not be created.
+    * New optional argument `.interaction({waitForEnd: true})` added to the [`.interaction()`](/docs/browser/new-relic-browser/browser-apis/interaction/) function: This allows customization of user interaction end time. The existing `.interaction()` functionality remains unchanged.
+    * Deprecated API: The function [`createTracer`](/docs/browser/new-relic-browser/browser-apis/createtracer/): While still functional, the `createTracer` function is deprecated as it no longer keeps interactions open or times callbacks. Note: If you continue to use `createTracer` with the new SPA experience,`BrowserTiming` events will not be created.
 
 ## Try out the new browser SPA monitoring experience [#enable-feature]
 
@@ -82,7 +82,7 @@ The updated SPA monitoring experience is designed to eliminate these problems an
 
 * `AjaxRequest` association:
     * Potential exclusion from interactions: Ajax requests that initiated near the end of previous interactions might now be excluded due to shortened interaction durations.
-    * Manual extension: If you need a request to be attributed to a specific interaction, use the argument `.interaction({waitForEnd: true})` added to the [`.interaction()`](https://docs.newrelic.com/docs/browser/new-relic-browser/browser-apis/interaction/) function to keep the interaction open until the request fires, then `.end()` the interaction. This will associate the request to the interaction.
+    * Manual extension: If you need a request to be attributed to a specific interaction, use the argument `.interaction({waitForEnd: true})` added to the [`.interaction()`](/docs/browser/new-relic-browser/browser-apis/interaction/) function to keep the interaction open until the request fires, then `.end()` the interaction. This will associate the request to the interaction.
 
 ## Leave feedback [#feedback]
 

src/content/docs/data-apis/manage-data/manage-data-retention.mdx

@@ -17,7 +17,7 @@ freshnessValidatedDate: never
 
 On the <DNT>**Data retention**</DNT> UI page, located in the [data management hub](https://one.newrelic.com/data-management-hub), you can review and manage how long different types of data are stored. You may want shorter retention for some data types in order to protect sensitive information, or you may want longer retention (up to seven years) to be able to see and analyze data and trends over a longer period.
 
-To learn about plans and costs for changing retention, see [Data options: Data Plus and original](https://docs.newrelic.com/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing/#upgrade-data-plus).
+To learn about plans and costs for changing retention, see [Data options: Data Plus and original](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing/#upgrade-data-plus).
 
 ## Extend your data retention for long-term analysis and compliance
 

src/content/docs/distributed-tracing/ui-data/related-trace-entity-signals.mdx

@@ -103,7 +103,7 @@ To ensure you're working with the most relevant distributed tracing insights, he
   * To access insights, adjust the time range to focus on a period within the last week.
 * `No data from your entity`:
   * This message suggests that your service isn't currently reporting distributed tracing data.
-  * To unlock these valuable insights, set up distributed tracing for your service by following the [guided install](https://onenr.io/0OQM6lV3DwG). If you're new to distributed tracing, start by reading the [Distributed tracing: Planning guide](https://docs.newrelic.com/docs/distributed-tracing/concepts/distributed-tracing-planning-guide/).
+  * To unlock these valuable insights, set up distributed tracing for your service by following the [guided install](https://onenr.io/0OQM6lV3DwG). If you're new to distributed tracing, start by reading the [Distributed tracing: Planning guide](/docs/distributed-tracing/concepts/distributed-tracing-planning-guide/).
 * `No data from related entities`;
   * This message indicates your service is reporting data but its dependencies aren't.
   * By [enabling distributed tracing for your services](https://onenr.io/0OQM6lV3DwG), your dependencies should also be automatically enabled.

src/content/docs/errors-inbox/browser-tab.mdx

@@ -106,7 +106,7 @@ Here are some reasons you don't see a stack trace for an error:
 
 * You've captured the error before the New Relic agent sees it.
 
-* If the error occurs during multiple [harvest cycles](http://[cycle](docs.newrelic.com/docs/using-new-relic/welcome-new-relic/get-started/glossary#harvest-cycle)) in the same user visit, only error events reported during the first harvest cycle will have a stack trace recorded.
+* If the error occurs during multiple [harvest cycles](/docs/new-relic-solutions/get-started/glossary/#harvest-cycle) in the same user visit, only error events reported during the first harvest cycle will have a stack trace recorded.
 
 ### Solutions for reporting stack traces [#solutions]
 

src/content/docs/infrastructure/elastic-container-service-integration/ecs-integration-recommended-alert-conditions.mdx

@@ -16,17 +16,17 @@ New Relic's [ECS integration](/docs/introduction-amazon-ecs-integration) reports
 
 ## Recommended alert conditions [#alerts]
 
-Here are some recommended ECS alert conditions. To add these alerts, go to the [alerts UI](http://alerts.newrelic.com/) and add the following [NRQL alert conditions](/docs/alerts/new-relic-alerts/defining-conditions/create-alert-conditions-nrql-queries) to an existing or new alert policy:
+Here are some recommended ECS alert conditions. To add these alerts, go to the [alerts UI](http://one.newrelic.com/alerts/) and add the following [NRQL alert conditions](/docs/alerts/new-relic-alerts/defining-conditions/create-alert-conditions-nrql-queries) to an existing or new alert policy:
 
 * High CPU usage
 
-  * NRQL: FROM ContainerSample SELECT cpuUsedCoresPercent
+  * NRQL: `FROM ContainerSample SELECT cpuUsedCoresPercent`
   * Critical: > 90% for 5 minutes
 * High memory usage
 
-  * NRQL: FROM ContainerSample SELECT memoryUsageBytes / memorySizeLimitBytes
+  * NRQL: `FROM ContainerSample SELECT memoryUsageBytes / memorySizeLimitBytes`
   * Critical: > 80% for 5 minutes
 * Restart count
 
-  * NRQL: FROM ContainerSample SELECT max(restartCount) - min(restartCount)
+  * NRQL: `FROM ContainerSample SELECT max(restartCount) - min(restartCount)`
   * Critical: > 5 for 5 minutes

src/content/docs/infrastructure/host-integrations/host-integrations-list/temporal-cloud-integration.mdx

@@ -36,13 +36,13 @@ Our Temporal Cloud integration monitors the performance of your Temporal Cloud d
       title="Note"
       variant="tip"
     >
-      Flex requires a [New Relic account](https://docs.newrelic.com/docs/accounts/accounts-billing/account-setup/create-your-new-relic-account) and is compatible with the following operating systems/platforms:
+      Flex requires a [New Relic account](/docs/accounts/accounts-billing/account-setup/create-your-new-relic-account) and is compatible with the following operating systems/platforms:
 
       1. Linux
       2. Windows
       3. Kubernetes
 
-         For more information on compatible distros and versions, see the [Infrastructure agent compatibility page](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/getting-started/compatibility-requirements-new-relic-infrastructure).
+         For more information on compatible distros and versions, see the [Infrastructure agent compatibility page](/docs/infrastructure/new-relic-infrastructure/getting-started/compatibility-requirements-new-relic-infrastructure).
     </Callout>
 
     1. Create file with named `nri-flex-temporal-cloud-config.yml` in this path:
@@ -311,7 +311,7 @@ Our Temporal Cloud integration monitors the performance of your Temporal Cloud d
     3. In the search bar, type **Temporal Cloud**.
     4. The Temporal Cloud dashboard should appear. Click on it to install it.
 
-    Your Temporal Cloud dashboard is considered a custom dashboard and can be found in the Dashboards UI. For docs on using and editing dashboards, see [our dashboard docs](https://docs.newrelic.com/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/).
+    Your Temporal Cloud dashboard is considered a custom dashboard and can be found in the Dashboards UI. For docs on using and editing dashboards, see [our dashboard docs](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/).
 
     Here is a NRQL query to check the Temporal Cloud frontend service requests count:
 

src/content/docs/infrastructure/host-integrations/host-integrations-list/temporal-monitoring-integration.mdx

@@ -251,7 +251,7 @@ Our Temporal integration monitors the performance of your Temporal data, helping
     3. In the search bar, type **Temporal**.
     4. When the Temporal dashboard appears, click to install it.
 
-    Your Temporal dashboard is considered a custom dashboard and can be found in the Dashboards UI. For docs on using and editing dashboards, see [our dashboard docs](https://docs.newrelic.com/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/).
+    Your Temporal dashboard is considered a custom dashboard and can be found in the Dashboards UI. For docs on using and editing dashboards, see [our dashboard docs](/docs/query-your-data/explore-query-data/dashboards/introduction-dashboards/).
 
     Here is a NRQL query to check the Temporal request latency sum:
 

src/content/docs/infrastructure/install-infrastructure-agent/get-started/requirements-infrastructure-agent.mdx

@@ -82,7 +82,7 @@ The infrastructure agent supports these operating systems up to their manufactur
       </td>
 
       <td>
-        See [container monitoring requirements](docs/infrastructure/install-infrastructure-agent/linux-installation/container-instrumentation-infrastructure-monitoring/#requirements)
+        See [container monitoring requirements](/docs/infrastructure/install-infrastructure-agent/linux-installation/container-instrumentation-infrastructure-monitoring/#requirements)
       </td>
     </tr>
 

src/content/docs/infrastructure/manage-your-data/data-instrumentation/default-infrastructure-monitoring-data.mdx

@@ -96,7 +96,7 @@ Select an event name in the following table to see its attributes.
       </td>
 
       <td>
-        `StorageSample` represents a single storage device associated with a server. Each sample gathers descriptive information about the device, the type of file system it uses, and its current usage and capacity. We take a snapshot of this data every 20 seconds for each mounted file system and package it into a `StorageSample` event, which is then sent to New Relic. This data appears on the [<DNT>**Storage**</DNT> UI page](/docs/infrastructure/infrastructure-ui-pages/infra-hosts-ui-page#storage).
+        `StorageSample` represents a single storage device that contains partitions currently mounted on the server. Each sample gathers descriptive information about the device, the type of file system it uses, and its current usage and capacity. We take a snapshot of this data every 20 seconds for each mounted file system and package it into a `StorageSample` event, which is then sent to New Relic. This data appears on the [<DNT>**Storage**</DNT> UI page](/docs/infrastructure/infrastructure-ui-pages/infra-hosts-ui-page#storage).
 
         <Callout variant="important">
           If your server uses disks with file systems other than the supported file systems in the following table, `StorageSample` events will not be generated for those disks.

src/content/docs/infrastructure/new-relic-infrastructure/infrastructure-alert-conditions/rest-api-calls-new-relic-infrastructure-alerts.mdx

@@ -248,7 +248,7 @@ To update an infrastructure condition, use this basic cURL command. To indicate
     id=""
     title="Example update (PUT) a condition"
   >
-    ```
+    ```sh
     curl -X PUT 'https://infra-api.newrelic.com/v2/alerts/conditions/condition-id' \
          -H "Api-Key:$API_KEY" -i -H 'Content-Type: application/json' \
          -d '{"data":{DATA object details}}'