Merge pull request #3623 from newrelic/fix-bad-data-dictionary-links

Fix legacy-style data dictionary links

src/content/docs/accounts/new-relic-account-usage/getting-started-usage/insights-subscription-usage.mdx

@@ -36,7 +36,7 @@ For accounts on our [original pricing plan](/docs/accounts/original-accounts-bil
 
 Once per day, an account with an Insights Pro subscription will generate an `NrDailyUsage` [event](https://docs.newrelic.com/docs/telemetry-data-platform/ingest-manage-data/understand-data/new-relic-data-types#events-new-relic) for every [event namespace](#namespace). A `NrDailyUsage` event includes a count of the events under that namespace.
 
-To view the attributes for this event, see the `NrDailyUsage` [entry in the data dictionary](/attribute-dictionary?attribute_name=&events_tids%5B%5D=8891).
+To view the attributes for this event, see the `NrDailyUsage` [entry in the data dictionary](/attribute-dictionary/?event=NrDailyUsage).
 
 ## Usage calculations [#calculation]
 

src/content/docs/accounts/new-relic-account-usage/getting-started-usage/introduction-new-relic-subscription-usage-data.mdx

@@ -41,7 +41,7 @@ For accounts on our [original pricing plan](/docs/accounts/original-accounts-bil
 To view your usage data:
 
 * If you are an account owner or admin, you can access subscription usage data in the New Relic UI.
-* If you are not the account owner or admin, you can query usage data by using the [`NrDailyUsage` event](https://docs.newrelic.com/attribute-dictionary?attribute_name=&events_tids%5B%5D=8891).
+* If you are not the account owner or admin, you can query usage data by using the [`NrDailyUsage` event](/attribute-dictionary/?event=NrDailyUsage).
 
 ## How it works [#about-usage]
 

src/content/docs/agents/c-sdk/instrumentation/instrument-your-app-c-sdk.mdx

@@ -98,7 +98,7 @@ For more information, see the [C SDK installation procedures](/docs/agents/c-sdk
     id="datastore-segments"
     title="Instrument calls to datastores"
   >
-    To monitor calls to datastores, instrument the datastore segments within an instrumented transaction. Datastore segments appear in the **Breakdown** table and **Databases** tab on the [**Transactions** page](/docs/apm/applications-menu/monitoring/transactions-page) in New Relic. You can also view datastore segments as a [`databaseDuration` attribute](https://docs.newrelic.com/attribute-dictionary/transaction/databaseduration) of [APM `Transaction` events](/docs/insights/insights-data-sources/default-events-attributes/apm-default-event-attributes).
+    To monitor calls to datastores, instrument the datastore segments within an instrumented transaction. Datastore segments appear in the **Breakdown** table and **Databases** tab on the [**Transactions** page](/docs/apm/applications-menu/monitoring/transactions-page) in New Relic. You can also view datastore segments as a [`databaseDuration` attribute](/attribute-dictionary/transaction/databaseduration) of [APM `Transaction` events](/docs/insights/insights-data-sources/default-events-attributes/apm-default-event-attributes).
 
     To instrument a datastore segment, wrap the New Relic functions that start and stop instrumentation around the function you want to monitor:
 

src/content/docs/agents/ruby-agent/attributes/enable-disable-attributes-ruby.mdx

@@ -467,7 +467,7 @@ Use the following properties to enable or disable attributes:
 
     Prefix of attributes to exclude from error collection. Allows `*` as wildcard at end.
 
-    To prevent [error.message](https://docs.newrelic.com/attribute-dictionary?attribute_name=error.message) collection, instead use the [strip_exception_messages](https://docs.newrelic.com/docs/agents/ruby-agent/configuration/ruby-agent-configuration#strip_exception_messages-enabled) configuration.
+    To prevent [error.message](/attribute-dictionary?attribute_name=error.message) collection, instead use the [strip_exception_messages](https://docs.newrelic.com/docs/agents/ruby-agent/configuration/ruby-agent-configuration#strip_exception_messages-enabled) configuration.
   </Collapser>
 
   <Collapser

src/content/docs/agents/ruby-agent/configuration/ruby-agent-configuration.mdx

@@ -232,7 +232,7 @@ These settings are available for agent configuration. Some settings depend on yo
       </tbody>
     </table>
 
-  When `true`, the agent captures HTTP request parameters and attaches them to transaction traces, traced errors, and [`TransactionError` events](/attribute-dictionary?attribute_name=&events_tids%5B%5D=8241)
+  When `true`, the agent captures HTTP request parameters and attaches them to transaction traces, traced errors, and [`TransactionError` events](/attribute-dictionary/?event=TransactionError)
 <div class="callout-warning">
 When using the `capture_params` setting, the Ruby agent will not attempt to filter secret information. <b>Recommendation:</b> To filter secret information from request parameters, use the [`attributes.include` setting](/docs/agents/ruby-agent/attributes/enable-disable-attributes-ruby) instead. For more information, see the <a href="/docs/agents/ruby-agent/attributes/ruby-attribute-examples#ex_req_params">Ruby attribute examples</a>.
 </div>

src/content/docs/browser/browser-monitoring/browser-pro-features/ajax-page-identify-time-consuming-calls.mdx

@@ -294,5 +294,5 @@ In addition to the **AJAX** UI, you can also use these resources:
 
 * Help prevent problems from occurring by using [alerts](/docs/alerts-applied-intelligence/new-relic-alerts/get-started/introduction-alerts) and [Applied Intelligence](/docs/alerts-applied-intelligence/new-relic-alerts/get-started/introduction-applied-intelligence) for your key performance indicators.
 * Use [single-page app (SPA) monitoring](/docs/browser/single-page-app-monitoring/get-started/introduction-single-page-app-monitoring). This is valuable for any app that uses AJAX requests to pull content dynamically and create a fluid user experience.
-* [Query your data](/docs/query-your-data/explore-query-data/explore-data/introduction-querying-new-relic-data) in the UI or by API. For example, you can query with [default browser events](/docs/insights/insights-data-sources/default-data/browser-default-events-insights), use [SPA `AjaxRequest`](https://docs.newrelic.com/attribute-dictionary?attribute_name=&events_tids%5B%5D=8317) for geographic and browser data, or get your own [custom data](/docs/telemetry-data-platform/get-data-new-relic/getting-started/introduction-new-relic-data-ingest-apis-sdks) into New Relic.
+* [Query your data](/docs/query-your-data/explore-query-data/explore-data/introduction-querying-new-relic-data) in the UI or by API. For example, you can query with [default browser events](/docs/insights/insights-data-sources/default-data/browser-default-events-insights), use [SPA `AjaxRequest`](/attribute-dictionary/?event=AjaxRequest) for geographic and browser data, or get your own [custom data](/docs/telemetry-data-platform/get-data-new-relic/getting-started/introduction-new-relic-data-ingest-apis-sdks) into New Relic.
 * Visualize and share your data with [charts](/docs/insights/use-insights-ui/manage-dashboards/chart-types) and [dashboards](/docs/query-your-data/explore-query-data/dashboards/introduction-new-relic-one-dashboards).

src/content/docs/browser/browser-monitoring/getting-started/introduction-browser-monitoring.mdx

@@ -45,7 +45,7 @@ These tools (and more!) help your teams optimize your end users' page load exper
 
 Real user data gives insights into actual page performance, but you also need to look into your users' perception of your site's performance. Pages can load content in many different ways, and users control when they interact with that content. This is why some [user-centric performance metrics](/docs/browser/new-relic-browser/page-load-timing-resources/pageviewtiming-async-or-dynamic-page-details) happen outside the standard window onload (page load time) in the browser monitoring agent.
 
-The [`PageViewTiming` event](https://docs.newrelic.com/attribute-dictionary/pageview?attribute_name=&events_tids%5B%5D=10061) provides a more real-time delivery mechanism that does not have a dependency on any other event. Additional metrics include:
+The [`PageViewTiming` event](/attribute-dictionary/?event=PageViewTiming) provides a more real-time delivery mechanism that does not have a dependency on any other event. Additional metrics include:
 
 * First paint, first contentful paint, and largest contentful paint
 * First input delay

src/content/docs/browser/browser-monitoring/page-load-timing-resources/new-relic-cookies-used-browser.mdx

@@ -53,13 +53,13 @@ The default browser agent configuration does not retain any personal data as def
 
         IP address lookup values include:
 
-        * [`countryCode`](https://docs.newrelic.com/attribute-dictionary/pageview/countrycode)
-        * [`regionCode`](https://docs.newrelic.com/attribute-dictionary/pageview/regioncode)
-        * [`city`](https://docs.newrelic.com/attribute-dictionary/pageview/city)
+        * [`countryCode`](/attribute-dictionary/pageview/countrycode)
+        * [`regionCode`](/attribute-dictionary/pageview/regioncode)
+        * [`city`](/attribute-dictionary/pageview/city)
         * `asn (Autonomous System Number)`
         * `asnOrganization (ISP/Business/Institution)`
-        * [`asnLatitude`](https://docs.newrelic.com/attribute-dictionary/pageview/asnlatitude)
-        * [`asnLongitude`](https://docs.newrelic.com/attribute-dictionary/pageview/asnlongitude)
+        * [`asnLatitude`](/attribute-dictionary/pageview/asnlatitude)
+        * [`asnLongitude`](/attribute-dictionary/pageview/asnlongitude)
 
         The mapping process for the IP address lookup value is typically complete within minutes, but in some extreme cases may take up to 24 hours to process. Once the mapping process is complete, New Relic no longer retains the IP address.
       </td>

src/content/docs/browser/new-relic-browser/browser-agent-spa-api/noticeerror-browser-agent-api.mdx

@@ -40,7 +40,7 @@ JavaScript error monitoring must be [enabled](/docs/browser/new-relic-browser/ge
 
 Use this call to notice or log your app's handled or other miscellaneous errors. This is useful when you have caught and handled an error, but you still want to identify it without disrupting your app's operation.
 
-You can also use the API to notice errors that otherwise would be reported without any detail, such as errors that happen during the script initialization or in an inline event handler. The errors will appear in the [**JavaScript errors** page](/docs/browser/new-relic-browser/dashboard-details/javascript-errors-dashboard) along with other errors New Relic normally detects. They will also be recorded as a [`JavaScriptError` event](https://docs.newrelic.com/attribute-dictionary?attribute_name=&events_tids%5B%5D=8327). For example:
+You can also use the API to notice errors that otherwise would be reported without any detail, such as errors that happen during the script initialization or in an inline event handler. The errors will appear in the [**JavaScript errors** page](/docs/browser/new-relic-browser/dashboard-details/javascript-errors-dashboard) along with other errors New Relic normally detects. They will also be recorded as a [`JavaScriptError` event](/attribute-dictionary/?event=JavaScriptError). For example:
 
 ```
 var err = new Error('<var>Report caught error to New Relic</var>');newrelic.noticeError(<var>err</var>);

src/content/docs/browser/new-relic-browser/browser-pro-features/browser-data-distributed-tracing.mdx

@@ -138,7 +138,7 @@ Tips for finding and querying data:
 * You can find end-user-originating traces in any [New Relic One distributed tracing UI](/docs/understand-dependencies/distributed-tracing/ui-data/additional-distributed-tracing-features-new-relic-one).
 * In the distributed tracing UI, end-user spans are indicated with the ![New Relic distributed tracing browser span icon](./images/distributed-tracing-browser-span-icon.png "distributed-tracing-browser-span-icon.png") icon.
 * To see a span's attributes, select [a span in the UI](/docs/apm/distributed-tracing/ui-data/understand-use-distributed-tracing-data#span-details).
-* Spans are reported as [`Span` data](/attribute-dictionary?attribute_name=&events_tids%5B%5D=8337), and can be [queried in New Relic](/docs/using-new-relic/data/understand-data/query-new-relic-data).
+* Spans are reported as [`Span` data](/attribute-dictionary/?event=Span), and can be [queried in New Relic](/docs/using-new-relic/data/understand-data/query-new-relic-data).
 * Query tips:
   * Query by browser app name by setting `browserApp.name` to the browser app name.
   * Query for traces containing at least one browser app span with `browserApp.name is not null`.

src/content/docs/browser/new-relic-browser/guides/guide-using-browser-spa-apis.mdx

@@ -73,7 +73,7 @@ To monitor traces and events, use these methods:
 
     <tr>
       <td>
-        Group [page views](/attribute-dictionary?attribute_name=&events_tids%5B%5D=8302) by setting a page name
+        Group page views by setting a page name
       </td>
 
       <td>
@@ -213,7 +213,7 @@ To track single page applications, use these SPA API methods:
 
     <tr>
       <td>
-        Adjust attributes, such as name and ignored attributes, before the [interaction](//attribute-dictionary?attribute_name=&events_tids%5B%5D=8312) is recorded
+        Adjust attributes, such as name and ignored attributes, before the [interaction](/attribute-dictionary/?event=BrowserInteraction) is recorded
       </td>
 
       <td>

src/content/docs/browser/new-relic-browser/page-load-timing-resources/pageviewtiming-async-or-dynamic-page-details.mdx

@@ -11,7 +11,7 @@ redirects:
   - /docs/browser/new-relic-browser/page-load-timing-resources/pageviewtiming-get-async-page-load-details
 ---
 
-Browser monitoring's [`PageViewTiming` event](https://docs.newrelic.com/attribute-dictionary/pageview?attribute_name=&events_tids%5B%5D=10061) sends each data point as a separate event as soon as it is available. Because we do not restrict the timing, you can receive first paint or first interaction data regardless of when it fires. This document describes why and how to use `PageViewTiming` and its attributes to query data about your site, component loading, and user performance metrics, both from visual and responsiveness standpoints.
+Browser monitoring's [`PageViewTiming` event](/attribute-dictionary/?event=PageViewTiming) sends each data point as a separate event as soon as it is available. Because we do not restrict the timing, you can receive first paint or first interaction data regardless of when it fires. This document describes why and how to use `PageViewTiming` and its attributes to query data about your site, component loading, and user performance metrics, both from visual and responsiveness standpoints.
 
 ## Why use PageViewTiming? [#why-pageviewtiming]
 
@@ -67,7 +67,7 @@ The `BrowserInteraction` and `PageView` events end their reporting when they rec
       </td>
 
       <td>
-        The [`firstPaint`](https://docs.newrelic.com/attribute-dictionary/pageviewtiming/firstpaint) and [`firstContentfulPaint`](https://docs.newrelic.com/attribute-dictionary/pageviewtiming/firstContentfulPaint) attributes already are available with `BrowserInteraction` and `PageView` events. However, they are not always reliably captured before the window onload event fires.
+        The [`firstPaint`](/attribute-dictionary/pageviewtiming/firstpaint) and [`firstContentfulPaint`](/attribute-dictionary/pageviewtiming/firstContentfulPaint) attributes already are available with `BrowserInteraction` and `PageView` events. However, they are not always reliably captured before the window onload event fires.
 
         Using `PageViewTiming` gives you a way to capture these metrics even if they happen after the original page load time. This gives you a better understanding of the correlation between responsiveness of that load event and the visual rendering of your content.
       </td>
@@ -79,7 +79,7 @@ The `BrowserInteraction` and `PageView` events end their reporting when they rec
       </td>
 
       <td>
-        This new metric, available with [agent version 1163](https://docs.newrelic.com/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1163), [`largestContentfulPaint`](https://docs.newrelic.com/attribute-dictionary/pageviewtiming/largestcontentfulpaint), reports the render time of the largest content element visible in the viewport. Google's research found looking at when the largest element was rendered was a more accurate way to measure when the main content of a page is loaded and useful. Details on this metric, including limitations and considerations can be found in the [w3c draft](https://wicg.github.io/largest-contentful-paint/).
+        This new metric, available with [agent version 1163](https://docs.newrelic.com/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes/browser-agent-v1163), [`largestContentfulPaint`](/attribute-dictionary/pageviewtiming/largestcontentfulpaint), reports the render time of the largest content element visible in the viewport. Google's research found looking at when the largest element was rendered was a more accurate way to measure when the main content of a page is loaded and useful. Details on this metric, including limitations and considerations can be found in the [w3c draft](https://wicg.github.io/largest-contentful-paint/).
 
         In addition, we now report the cumulative layout shift (CLS) score attribute with LCP. This attribute is reported as `cumulativeLayoutShift.`
 
@@ -93,7 +93,7 @@ The `BrowserInteraction` and `PageView` events end their reporting when they rec
       </td>
 
       <td>
-        With the addition of [`firstInteraction`](https://docs.newrelic.com/attribute-dictionary/pageviewtiming/firstinteraction) and [`firstInputDelay`](https://docs.newrelic.com/attribute-dictionary/pageviewtiming/firstinputdelay), you can quickly determine the ways that your users are interacting with that visual content. These metrics tell you not only when they interacted, but what type of interaction (mousedown, pointerdown, etc.) and how long it took for them to receive a response from your site.
+        With the addition of [`firstInteraction`](/attribute-dictionary/pageviewtiming/firstinteraction) and [`firstInputDelay`](/attribute-dictionary/pageviewtiming/firstinputdelay), you can quickly determine the ways that your users are interacting with that visual content. These metrics tell you not only when they interacted, but what type of interaction (mousedown, pointerdown, etc.) and how long it took for them to receive a response from your site.
 
         The `firstInputDelay` metric lies in the middle of `FirstContentfulPaint` and Time to Interactive (TTI) metrics, measuring the time between when a first input can be made and when the browser's main thread is able to respond to any interactions.
 

src/content/docs/distributed-tracing/ui-data/span-attributes.mdx

@@ -15,5 +15,5 @@ redirects:
 [Distributed tracing](/docs/introduction-distributed-tracing) creates `Span` data that can be queried in New Relic. Here are ways to learn more about `Span` data:
 
 * To explore your span data, you can use the [query builder](/docs/chart-builder/use-chart-builder/get-started/introduction-chart-builder).
-* To see the default attributes attached to span data, use the [data dictionary](/attribute-dictionary?attribute_name=&events_tids%5B%5D=8337).
+* To see the default attributes attached to span data, use the [data dictionary](/attribute-dictionary/?event=Span).
 * For help with NRQL queries using these attributes, see these [example queries](/docs/apm/distributed-tracing/ui-data/example-insights-queries-distributed-trace-data).

src/content/docs/infrastructure/infrastructure-troubleshooting/troubleshoot-infrastructure/no-data-appears-infrastructure.mdx

@@ -29,7 +29,7 @@ Data should appear in the Infrastructure monitoring UI within a few minutes for
 </Callout>
 
 <Callout variant="important">
-  By default, the infrastructure agent doesn't send [data about the operating system's processes](https://docs.newrelic.com/attribute-dictionary?attribute_name=&events_tids%5B%5D=8412). To enable the sending of process data set [`enable_process_metrics`](https://docs.newrelic.com/docs/infrastructure/install-configure-manage-infrastructure/configuration/infrastructure-configuration-settings#enable-process-metrics) to `true`. To fine-tune which processes you want to monitor, configure [`include_matching_metrics`](https://docs.newrelic.com/docs/infrastructure/install-configure-manage-infrastructure/configuration/infrastructure-configuration-settings#include-matching-metrics).
+  By default, the infrastructure agent doesn't send data about the operating system's processes. To enable the sending of process data set [`enable_process_metrics`](https://docs.newrelic.com/docs/infrastructure/install-configure-manage-infrastructure/configuration/infrastructure-configuration-settings#enable-process-metrics) to `true`. To fine-tune which processes you want to monitor, configure [`include_matching_metrics`](https://docs.newrelic.com/docs/infrastructure/install-configure-manage-infrastructure/configuration/infrastructure-configuration-settings#include-matching-metrics).
 </Callout>
 
 ### Missing infrastructure data [#missing-infra]