Merge branch 'develop' into nb-mobile-sweep

.github/workflows/attribute-dictionary-comment.yml

@@ -0,0 +1,33 @@
+name: Attribute dictionary updates
+
+on:
+  pull_request:
+    branches:
+      - develop
+
+env:
+  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+
+jobs:
+  deny-attribute-dictionary-changes:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v3
+
+      - name: Prevent file change
+        uses: xalvarez/prevent-file-change-action@v1
+        with:
+          githubToken: ${{ secrets.GITHUB_TOKEN }}
+          pattern: .*\attribute-dictionary.json
+          trustedAuthors: nr-opensource-bot
+
+      - name: Comment if JSON file is modified
+        if: failure()
+        uses: thollander/actions-comment-pull-request@v2
+        with:
+          message: |
+            > [!WARNING]
+            > `attribute-dictionary.json` is an autogenerated file.
+            >
+            > Changes to attribute dictionary should be made through [source.datanerd.us/docs-eng/attribute-dictionary](https://source.datanerd.us/docs-eng/attribute-dictionary)

.github/workflows/vale-lint.yml

@@ -27,4 +27,6 @@ jobs:
         uses: thollander/actions-comment-pull-request@v2
         with:
           message: |
-            Our Vale automated writing feedback tool has suggestions for this PR. You can view these suggestions in the *Files changed* tab. If you're not a New Relic docs writer, we'll review any comments and you don't need to take any action (though feel free to make edits if you like!).
+            > [!NOTE]
+
+            > Our Vale automated writing feedback tool has suggestions for this PR. You can view these suggestions in the *Files changed* tab. If you're not a New Relic docs writer, we'll review any comments and you don't need to take any action (though feel free to make edits if you like!).

.github/workflows/verify-mdx.yml

@@ -5,7 +5,6 @@ on:
     branches:
       - develop
       - main
-      - tabatha/docs-freshness
 
 env:
   NODE_OPTIONS: '--max-old-space-size=4096'

CONTRIBUTING.md

@@ -59,7 +59,7 @@ yarn start
 
 Your site is now running at [`http://localhost:8000`](http://localhost:8000)!
 
-The first time you build the site locally, it will take upwards of 20 minutes. This is normal, and will take signifigantly less time afterwards.
+The first time you build the site locally, it will take upwards of 20 minutes. This is normal, and will take significantly less time afterward.
 
 ### Dependencies
 
@@ -287,7 +287,7 @@ if you face issues in contributing.
 
 ### General Install, compile or build issues
 
-Many of the common errors you'll face can be resolve by the following:
+Many of the common errors you'll face can be resolved by the following:
 
 1. Ensure you are using `yarn` not `npm`
 2. Always run `git pull` whenever you intend to create a new working branch

src/content/docs/accounts/accounts-billing/account-setup/downgradecancel-account.mdx

@@ -25,6 +25,7 @@ If you want to stop reporting some data to New Relic without downgrading or canc
 For how to manage data ingest, see [Manage your data](/docs/telemetry-data-platform/get-data-new-relic/manage-data/manage-your-data).
 
 To uninstall agents or integrations, here are some recommended procedures:
+
 * [Remove <InlinePopover type="apm" />, <InlinePopover type="browser" />, and <InlinePopover type="mobile" /> apps](/docs/apm/new-relic-apm/maintenance/remove-applications-new-relic/)
 * [Remove infrastructure agent](/docs/infrastructure/install-infrastructure-agent/update-or-uninstall/uninstall-infrastructure-agent/)
 * For how to disable other New Relic tools, see their specific docs. You can [search New Relic solutions here](https://newrelic.com/instant-observability/).

src/content/docs/accounts/accounts-billing/new-relic-one-pricing-billing/usage-queries-alerts.mdx

@@ -497,5 +497,6 @@ Here are some technical details about how `bytecountestimate()` works:
 
 * There are several types of data that [don't count towards ingest](/docs/accounts/accounts-billing/new-relic-one-pricing-billing/data-ingest-billing/#usage-calculation) but that is returned by the `bytecountestimate()` function. This means that this function sometimes shows **more** data than actually is counted towards your usage. It may rarely show a lower amount but, if it does, it will be only slightly lower. 
 * Some telemetry data reported from an entity shares common attributes (for example, attributes about your New Relic account). We don't count the duplicated attributes towards your ingest, but `bytecountestimate()` does count those attributes. This can sometimes result in a large discrepency between a `bytecountestimate()` query and your actual usage. 
-* Our APM, browser monitoring, and <InlinePopover type="mobile" /> report a type of data known as [metric timeslice data](/docs/data-apis/understand-data/new-relic-data-types/#timeslice-data). This data isn't stored in NRDB like our other data types are, and so trying to use `bytecountestimate()` on this data can result in confusing results. When querying this data, we recommend faceting by application name, and not by the metric name. 
+* Our <InlinePopover type="apm" />, <InlinePopover type="browser" />, and <InlinePopover type="mobile" /> report a type of data known as [metric timeslice data](/docs/data-apis/understand-data/new-relic-data-types/#timeslice-data). This data isn't stored in NRDB like our other data types are, and so trying to use `bytecountestimate()` on this data can result in confusing results. When querying this data, we recommend faceting by application name, and not by the metric name. 
+
 

src/content/docs/accounts/accounts-billing/new-relic-one-user-management/user-management-concepts.mdx

@@ -153,7 +153,7 @@ Here's a table with our standard roles. To better understand these roles, go to
       </td>
 
       <td>
-        Provides read-only access to platform features and provides create, update, and delete access to a subset of features (for example, <InlinePopover type="apm" /> UI, browser monitoring UI, and Synthetics). 
+        Provides access to our platform features (for example, APM UI and <InlinePopover type="browser" /> UI), but lacks permissions to configure those features and lacks organization-level and user management permissions. 
 
         Use the access management UI to view the capabilities included in the standard user role across the platform. 
       </td>

src/content/docs/accounts/accounts-billing/new-relic-one-user-management/user-permissions.mdx

@@ -130,7 +130,7 @@ These permissions pertain to [applied intelligence](/docs/alerts-applied-intelli
     id="browser"
     title="Browser"
   >
-These permissions pertain to [browser monitoring](/docs/browser/browser-monitoring/getting-started/introduction-browser-monitoring): 
+These permissions pertain to [<InlinePopover type="browser" />](/docs/browser/browser-monitoring/getting-started/introduction-browser-monitoring): 
 
 * **Application settings**: relates to browser application settings.
 * **Domain conditions**: relates to [browser domain conditions](/docs/browser/new-relic-browser/configuration/monitor-or-block-specific-domains-subdomains).

src/content/docs/accounts/accounts-billing/new-relic-one-user-management/user-type.mdx

@@ -62,7 +62,7 @@ Here's a brief summary of what each user type gets access to:
   <tbody>
     <tr>
       <td>
-        Basic users are free. Basic users can set up our observability tools, run queries on your data, use custom <InlinePopover type="dashboards" /> (quickstart dashboards up to 7 days), use some basic alerting features, and more. Basic users **can't** use our curated experiences (for example, our <InlinePopover type="apm" /> UI, browser UI, or mobile UI).
+        Basic users are free. Basic users can set up our observability tools, run queries on your data, use custom <InlinePopover type="dashboards" /> (quickstart dashboards up to 7 days), use some basic alerting features, and more. Basic users **can't** use our curated experiences (for example, our <InlinePopover type="apm" /> UI, <InlinePopover type="browser" /> UI, or mobile UI).
 
       </td>
 

src/content/docs/accounts/install-new-relic/partner-based-installation/heroku-install-new-relic-add.mdx

@@ -35,7 +35,7 @@ redirects:
 freshnessValidatedDate: never
 ---
 
-[Heroku](https://devcenter.heroku.com/articles/newrelic) is a Platform as a Service (PaaS) solution for hosting web applications in various agent languages. With New Relic, you can extend Heroku with metrics from our monitoring solutions, like <InlinePopover type="apm" /> and browser monitoring. The New Relic add-on supports Java, Node.js, PHP, Python, and Ruby.
+[Heroku](https://devcenter.heroku.com/articles/newrelic) is a Platform as a Service (PaaS) solution for hosting web applications in various agent languages. With New Relic, you can extend Heroku with metrics from our monitoring solutions, like <InlinePopover type="apm" /> and <InlinePopover type="browser" />. The New Relic add-on supports Java, Node.js, PHP, Python, and Ruby.
 
 ## Install the New Relic add-on [#addon-installation]
 

src/content/docs/accounts/install-new-relic/partner-based-installation/log-install-new-relic-partners.mdx

@@ -50,7 +50,7 @@ These partners require specific login and deployment procedures for you to use y
     id="heroku"
     title="Heroku"
   >
-    [Heroku](https://www.heroku.com/) is a Platform as a Service (PaaS) solution capable of hosting web applications. With the New Relic Heroku add-on, you can extend Heroku with metrics from <InlinePopover type="apm" /> and browser monitoring. The New Relic add-on supports Java, Node.js, PHP, Python, and Ruby. For more information about installing and using New Relic with Heroku, see:
+    [Heroku](https://www.heroku.com/) is a Platform as a Service (PaaS) solution capable of hosting web applications. With the New Relic Heroku add-on, you can extend Heroku with metrics from <InlinePopover type="apm" /> and <InlinePopover type="browser" />. The New Relic add-on supports Java, Node.js, PHP, Python, and Ruby. For more information about installing and using New Relic with Heroku, see:
 
     * [Heroku dev center documentation](https://devcenter.heroku.com/articles/newrelic "Link opens in a new window")
     * [New Relic's documentation for installing Heroku](/docs/accounts-partnerships/partnerships/heroku-new-relic/heroku-installing-new-relic)

src/content/docs/accounts/original-accounts-billing/original-product-based-pricing/original-pricing-plan-queries.mdx

@@ -121,7 +121,7 @@ On May 31, 2023, the usage UI for our original pricing model reaches end-of-life
 
 ## What customers are affected? [#who-is-affected]
 
-This affects New Relic organizations on our [original pricing model](/docs/accounts/original-accounts-billing/original-product-based-pricing/overview-pricing-models/), which is a pricing model where we billed by various products (like APM, Browser monitoring, Infrastructure monitoring, and more).
+This affects New Relic organizations on our [original pricing model](/docs/accounts/original-accounts-billing/original-product-based-pricing/overview-pricing-models/), which is a pricing model where we billed by various products (like <InlinePopover type="apm" />, <InlinePopover type="browser" />, Infrastructure monitoring, and more).
 
 ## What can you do? [#actions]
 

src/content/docs/accounts/original-accounts-billing/original-users-roles/users-roles-original-user-model.mdx

@@ -389,7 +389,7 @@ Here are some more details about some of our add-on manager roles:
     id="browser-manager"
     title="Browser manager"
   >
-    Here is a summary of Admin and Add-on manager permissions with [New Relic Browser](/docs/browser). To allow a User or Restricted User to execute any of these functions in New Relic Browser, assign a Browser add-on manager role.
+    Here is a summary of Admin and Add-on manager permissions with [New Relic <InlinePopover type="browser" />](/docs/browser). To allow a User or Restricted User to execute any of these functions in New Relic Browser, assign a Browser add-on manager role.
 
     Admin and manager permissions for Browser include:
 

src/content/docs/accounts/original-accounts-billing/product-based-pricing/overview-data-retention-components.mdx

@@ -314,7 +314,7 @@ Select a New Relic product to see details about its data retention:
     id="browser"
     title="Browser"
   >
-    For organizations on our [original pricing model](/docs/accounts/original-accounts-billing/product-pricing/product-based-pricing), Browser data is stored depending on your subscription level:
+    For organizations on our [original pricing model](/docs/accounts/original-accounts-billing/product-pricing/product-based-pricing), <InlinePopover type="browser" /> data is stored depending on your subscription level:
 
     <table>
       <thead>

src/content/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/other-condition-types/apm-metric-alert-conditions.mdx

@@ -22,9 +22,9 @@ import accountsExternalCallsQuery from 'images/accounts_screenshot-full_external
 
 import accountsNrqlConditionBuilderModal from 'images/accounts_screenshot-full_nrql-condition-builder-modal.webp'
 
-There are various ways to create alert conditions for New Relic <InlinePopover type="apm" /> and browser monitoring metrics, but we recommend using NRQL. Using a NRQL alert condition provides additional controls, improved detection time, and consistency across all data types.
+There are various ways to create alert conditions for New Relic <InlinePopover type="apm" /> and <InlinePopover type="browser" /> metrics, but we recommend using NRQL. Using a NRQL alert condition provides additional controls, improved detection time, and consistency across all data types.
 
-In 2021, we made it easier to create NRQL alert conditions from charts and queries throughout New Relic. See below an example of how to create an <InlinePopover type="apm" /> external service condition using NRQL.
+In 2021, we made it easier to create NRQL alert conditions from charts and queries throughout New Relic. See below an example of how to create an APM external service condition using NRQL.
 
 Setting up an APM or browser monitoring metric alert condition is a two-part process: First, you need to identify the entity, then you create the NRQL condition.
 

src/content/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/rest-api-alerts/disable-enable-alerts-conditions-using-api.mdx

@@ -45,7 +45,7 @@ The process for disabling or enabling a condition is the same general process fo
      >
        If you don't know the category of the condition you want to change, you must search for it by making API calls using the four condition categories. Here are the different API call formats for the various condition categories.
 
-       * [APM, browser, and <InlinePopover type="mobile" />](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#conditions-list)  
+       * [<InlinePopover type="apm" />, <InlinePopover type="browser" />, and <InlinePopover type="mobile" />](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#conditions-list)  
          Conditions available: `apm_app_metric`, `apm_kt_metric`, `browser_metric`, and `mobile_metric`  
          [API Explorer link Get>List](https://rpm.newrelic.com/api/explore/alerts_conditions/list)
        * [External services](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#ext-conditions-list)  

src/content/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/rest-api-alerts/manage-entities-alerts-conditions.mdx

@@ -35,7 +35,7 @@ To update the entity list for a condition:
 1. Locate the appropriate [entity ID](/docs/alerts/new-relic-alerts/getting-started/alerts-glossary#alert-entity); for example, [Application ID](/docs/apis/rest-api-v2/requirements/listing-host-instance-application-server-ids) and [browser ID](/docs/apis/rest-api-v2/browser-examples-v2/adding-or-listing-browser-apps-api-v2#specific-browser-app).
 2. [Identify the policy ID by name or type](/docs/apm/apis/alert-examples-v2/listing-policies-api-v2#single_policy).
 3. Get the list of conditions associated with the policy and choose the one you want to modify for the appropriate category:
-   * [APM, browser, and <InlinePopover type="mobile" />](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#conditions)
+   * [<InlinePopover type="apm" />, <InlinePopover type="browser" />, and <InlinePopover type="mobile" />](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#conditions)
    * [External services](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#ext-services-conditions)
    * [Synthetic monitoring](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#synthetics-conditions)
 4. Modify the condition using the [add](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#add-entity) or [remove](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#remove_entity) API requests.