Merge branch 'develop' into io-redirect

src/content/docs/accounts/original-accounts-billing/original-data-retention/event-data-retention-original-pricing-plan.mdx

@@ -316,6 +316,3 @@ Requirements to use this feature:
 
 For information on managing retention settings with APIs, see the [Manage data retention documentation](/docs/telemetry-data-platform/manage-data/manage-data-retention/#api-examples).
 
-## For more help [#more_help]
-
-For details about the data retention of other products or [integrations](https://newrelic.com/instant-observability/), see that specific documentation.

src/content/docs/agile-handbook/appendices/backlog-review.mdx

@@ -48,6 +48,6 @@ When you review an issue, perform the following checks:
   </ButtonLink>
 </ButtonGroup>
 
-## For more help
-
-We welcome thoughts or questions on our handbook! The easiest way to get in touch is to [file a GitHub issue](https://github.com/newrelic/docs-website/issues/new/choose).
+<Callout variant="tip">
+We welcome thoughts or questions on our handbook! The easiest way to get in touch is to [file a GitHub issue](https://github.com/newrelic/docs-website/issues/new/choose).
+</Callout>

src/content/docs/agile-handbook/appendices/project-scoping-cheatsheet.mdx

@@ -67,6 +67,6 @@ We use this cheatsheet to help us scope projects in a consistent way.
   </ButtonLink>
 </ButtonGroup>
 
-## For more help
-
-We welcome thoughts or questions on our handbook! The easiest way to get in touch is to [file a GitHub issue](https://github.com/newrelic/docs-website/issues/new/choose).
+<Callout variant="tip">
+We welcome thoughts or questions on our handbook! The easiest way to get in touch is to [file a GitHub issue](https://github.com/newrelic/docs-website/issues/new/choose).
+</Callout>

src/content/docs/agile-handbook/appendices/ticket-best-practices.mdx

@@ -157,6 +157,6 @@ When you edit the site, include the Jira issue key (DOC-1234, for example) in yo
   </ButtonLink>
 </ButtonGroup>
 
-## For more help
-
-We welcome thoughts or questions on our handbook! The easiest way to get in touch is to [file a GitHub issue](https://github.com/newrelic/docs-website/issues/new/choose).
+<Callout variant="tip">
+We welcome thoughts or questions on our handbook! The easiest way to get in touch is to [file a GitHub issue](https://github.com/newrelic/docs-website/issues/new/choose).
+</Callout>

src/content/docs/agile-handbook/heroing/managing-the-github-boards.mdx

@@ -125,6 +125,6 @@ When a docs writer creates a pull request, it's their responsibility to merge it
   </ButtonLink>
 </ButtonGroup>
 
-## For more help
-
+<Callout variant="tip">
 We welcome thoughts or questions on our handbook! The easiest way to get in touch is to [file a GitHub issue](https://github.com/newrelic/docs-website/issues/new/choose).
+</Callout>

src/content/docs/agile-handbook/heroing/what-is-a-hero.mdx

@@ -102,6 +102,6 @@ Our tech writers in Barcelona cover the 2nd shift heroing during their regular w
   </ButtonLink>
 </ButtonGroup>
 
-## For more help
-
-We welcome thoughts or questions on our handbook! The easiest way to get in touch is to [file a GitHub issue](https://github.com/newrelic/docs-website/issues/new/choose).
+<Callout variant="tip">
+We welcome thoughts or questions on our handbook! The easiest way to get in touch is to [file a GitHub issue](https://github.com/newrelic/docs-website/issues/new/choose).
+</Callout>

src/content/docs/agile-handbook/key-concepts/agile-roles.mdx

@@ -62,6 +62,6 @@ We should ensure our stakeholders know that we work in two week sprints, so that
   </ButtonLink>
 </ButtonGroup>
 
-## For more help
-
-We welcome thoughts or questions on our handbook! The easiest way to get in touch is to [file a GitHub issue](https://github.com/newrelic/docs-website/issues/new/choose).
+<Callout variant="tip">
+We welcome thoughts or questions on our handbook! The easiest way to get in touch is to [file a GitHub issue](https://github.com/newrelic/docs-website/issues/new/choose).
+</Callout>

src/content/docs/agile-handbook/key-concepts/agile-sprints-profusion-of-terms.mdx

@@ -59,6 +59,6 @@ Each squad is responsible for its own grooming and sprint planning, but the mana
   </ButtonLink>
 </ButtonGroup>
 
-## For more help
-
-We welcome thoughts or questions on our handbook! The easiest way to get in touch is to [file a GitHub issue](https://github.com/newrelic/docs-website/issues/new/choose).
+<Callout variant="tip">
+We welcome thoughts or questions on our handbook! The easiest way to get in touch is to [file a GitHub issue](https://github.com/newrelic/docs-website/issues/new/choose).
+</Callout>

src/content/docs/agile-handbook/key-concepts/key-agile-principles.mdx

@@ -66,6 +66,6 @@ This lets us create win-wins: Rather than a simple "no," a requestor can decide
   </ButtonLink>
 </ButtonGroup>
 
-## For more help
-
+<Callout variant="tip">
 We welcome thoughts or questions on our handbook! The easiest way to get in touch is to [file a GitHub issue](https://github.com/newrelic/docs-website/issues/new/choose).
+</Callout>

src/content/docs/agile-handbook/sprint-mechanics/liaisonships.mdx

@@ -264,6 +264,6 @@ However, a liaison is not the only author on a project. Liaisons should structur
   </ButtonLink>
 </ButtonGroup>
 
-## For more help
-
-We welcome thoughts or questions on our handbook! The easiest way to get in touch is to [file a GitHub issue](https://github.com/newrelic/docs-website/issues/new/choose).
+<Callout variant="tip">
+We welcome thoughts or questions on our handbook! The easiest way to get in touch is to [file a GitHub issue](https://github.com/newrelic/docs-website/issues/new/choose).
+</Callout>

src/content/docs/agile-handbook/sprint-mechanics/meetings-and-ceremonies.mdx

@@ -111,6 +111,6 @@ The goal of the retro is to improve the way we work together. That could be rela
   </ButtonLink>
 </ButtonGroup>
 
-## For more help
-
-We welcome thoughts or questions on our handbook! The easiest way to get in touch is to [file a GitHub issue](https://github.com/newrelic/docs-website/issues/new/choose).
+<Callout variant="tip">
+We welcome thoughts or questions on our handbook! The easiest way to get in touch is to [file a GitHub issue](https://github.com/newrelic/docs-website/issues/new/choose).
+</Callout>

src/content/docs/agile-handbook/sprint-mechanics/planning-poker.mdx

@@ -105,6 +105,6 @@ Because we work in two [squads](/docs/agile-handbook/key-concepts/agile-sprints-
   </ButtonLink>
 </ButtonGroup>
 
-## For more help
-
-We welcome thoughts or questions on our handbook! The easiest way to get in touch is to [file a GitHub issue](https://github.com/newrelic/docs-website/issues/new/choose).
+<Callout variant="tip">
+We welcome thoughts or questions on our handbook! The easiest way to get in touch is to [file a GitHub issue](https://github.com/newrelic/docs-website/issues/new/choose).
+</Callout>

src/content/docs/agile-handbook/sprint-mechanics/sprint-workflow-and-jira-boards.mdx

@@ -97,6 +97,6 @@ For each open ticket assigned to you (or "carry over"), decide if you should:
   </ButtonLink>
 </ButtonGroup>
 
-## For more help
-
-We welcome thoughts or questions on our handbook! The easiest way to get in touch is to [file a GitHub issue](https://github.com/newrelic/docs-website/issues/new/choose).
+<Callout variant="tip">
+We welcome thoughts or questions on our handbook! The easiest way to get in touch is to [file a GitHub issue](https://github.com/newrelic/docs-website/issues/new/choose).
+</Callout>

src/content/docs/alerts-applied-intelligence/applied-intelligence/mlops-integrations/mona-mlops-integration.mdx

@@ -5,6 +5,8 @@ tags:
   - MLOps integrations
   - Mona integrations
 metaDescription: "Send your machine learning model data from Mona to New Relic to understand your model's performance."
+redirects:
+  - /docs/integrations/mlops-integrations/mona-mlops-integration
 ---
 
 ## What is MLOps? [#mlops]

src/content/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/advanced-techniques/alert-custom-violation-descriptions.mdx

@@ -155,14 +155,4 @@ Attention <!channel>
   Note that the Slack convention for channel-wide notifications in Incoming Webhooks is to use a **!** prefix instead of **@**
 
   e.g. **!here** or **!channel**
-</Callout>
-
-## For more help [#more_help]
-
-Recommendations for learning more:
-
-* To learn more about NerdGraph, see [Introduction to NerdGraph](/docs/apis/nerdgraph/get-started/introduction-new-relic-nerdgraph).
-* See the [alerts landing page](/docs/alerts).
-* Browse [New Relic's Explorers Hub](https://discuss.newrelic.com/c/telemetry-data-platform/alerts "Link opens in a new window.") for community discussions about Alerts.
-* [Find additional help or file a support ticket](/docs/accounts-partnerships/getting-started-new-relic/find-help-or-file-support-ticket).
-* Review the [Alerts licenses attributions](/docs/licenses/product-or-service-licenses/new-relic-alerts), [data usage limits](/docs/licenses/license-information/general-usage-licenses/new-relic-data-usage-limits-policies), and [other notices](/docs/licenses/license-information).
+</Callout>

src/content/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/advanced-techniques/scope-alert-thresholds-specific-instances.mdx

@@ -189,8 +189,4 @@ Here is an example of the API request format and JSON response.
     }
     ```
   </Collapser>
-</CollapserGroup>
-
-## For more help [#more_help]
-
-If you need additional help, get support at [support.newrelic.com](https://support.newrelic.com).
+</CollapserGroup>

src/content/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/advanced-techniques/select-product-targets-alert-condition.mdx

@@ -68,12 +68,4 @@ To change the list of selected targeted entities for an existing condition:
 3. Click **Notification channels**.
 4. In the channels list, click a channel to edit it.
 5. Click the trashcan to delete a channel.
-6. Click **Add notification channels** to add a new channel.
-
-## For more help [#more_help]
-
-Additional documentation resources include:
-
-* [Policy workflow](/docs/alerts/new-relic-alerts-beta/configuring-alert-policies/alert-policy-workflow) (basic process to set up your policies)
-* [Identify entities without policies](/docs/alerts/new-relic-alerts/configuring-alert-policies/identify-entities-without-alert-policies) (check whether the entity's color-coded health status indicator is light green with an icon)
-
+6. Click **Add notification channels** to add a new channel.

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

@@ -176,12 +176,4 @@ The following example shows how to disable a condition for an `apm_app_metric` c
      }
    }'
    ```
-4. Update the condition by submitting the edited condition JSON via an Update API request. For this specific condition, you would follow the steps in [Update conditions for APM policies](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#conditions-update). Other product conditions would have other API requests, as detailed in [Update API requests](#update-api-requests).
-
-## For more help [#more_help]
-
-Additional documentation resources include:
-
-* [API calls for alerts](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#alert-entity-conditions) (list of all API calls available)
-* [Using the API Explorer](/docs/apm/apis/api-explorer-v2/using-api-explorer) (using the API Explorer's user interface to get data in and data out of New Relic)
-* [Parts of the API Explorer](/docs/apm/apis/api-explorer-v2/parts-api-explorer) (a quick reference for how to use each section of the API Explorer)
+4. Update the condition by submitting the edited condition JSON via an Update API request. For this specific condition, you would follow the steps in [Update conditions for APM policies](/docs/alerts/new-relic-alerts/rest-api-alerts/rest-api-calls-new-relic-alerts#conditions-update). Other product conditions would have other API requests, as detailed in [Update API requests](#update-api-requests).

src/content/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/understand-technical-concepts/provide-runbook-instructions-alert-activity.mdx

@@ -28,12 +28,4 @@ To edit the runbook URL associated with a condition:
 2. On the **Edit conditions** page, click **Add runbook URL**, then provide the full path for your runbook URL (runbook URL, URL to internal wiki page, etc.), and then save.
 3. Optional: To change or delete an existing runbook URL from the alert condition, click **Remove**.
 
-We'll include your runbook URL in **Incident** details and in email notifications so that personnel will know exactly what to do.
-
-## For more help [#more_help]
-
-Additional documentation resources include:
-
-* [Policy workflow](/docs/alerts/new-relic-alerts-beta/configuring-alert-policies/alert-policy-workflow) (basic process to set up your alert policies)
-* [View or update user email channels](/docs/alerts/new-relic-alerts-beta/managing-notification-channels/view-or-update-user-email-channels) (maintaining the selected account's user emails as notification channels)
-* [Explore the incident history](/docs/alerts/new-relic-alerts-beta/reviewing-alert-incidents/explore-incident-history) (examine details about incidents, take action, and skim for patterns)
+We'll include your runbook URL in **Incident** details and in email notifications so that personnel will know exactly what to do.

src/content/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/understand-technical-concepts/violation-event-attributes.mdx

@@ -147,6 +147,8 @@ All attributes are available for use in a [description](/docs/alerts/new-relic-a
       </td>
       <td>
         The targeted entity's globally unique identifier, if available.
+
+        Available for muting rules.
       </td>
     </tr>
 

src/content/docs/alerts-applied-intelligence/new-relic-alerts/alert-notifications/muting-rules-suppress-notifications.mdx

@@ -43,7 +43,7 @@ Rules can have one of the following statuses:
 
 To create a muting rule, click **+ Add a rule** in the **Muting rules** screen. Enter a name and a description for the muting rule, and select the account to which the rule will apply.
 
-Next, build the violation filter. You can use a subset of [violation event attributes](/docs/alerts/new-relic-alerts/defining-conditions/violation-event-attributes) (specifically `accountId`, `conditionId`, `conditionName`, `nrqlEventType`, `nrqlQuery`, `policyId`, `policyName`, `runbookUrl` (as `conditionRunbookUrl`), `tags.<NAME>`, and `targetName`) and [sub-condition operators](#sub-conditions). Values can be compared against one of your violation attributes, such as an Alerts policy ID or a condition name.
+Next, build the violation filter. You can use a subset of [violation event attributes](/docs/alerts/new-relic-alerts/defining-conditions/violation-event-attributes) (specifically `accountId`, `conditionId`, `conditionName`, `entity.guid`, `nrqlEventType`, `nrqlQuery`, `policyId`, `policyName`, `runbookUrl` (as `conditionRunbookUrl`), `tags.<NAME>`, and `targetName`) and [sub-condition operators](#sub-conditions). Values can be compared against one of your violation attributes, such as an Alerts policy ID or a condition name.
 
 ![Muting rule edit screen](./images/violationfilter.png "Muting rule edit screen")
 

src/content/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/specify-when-alerts-create-incidents.mdx

@@ -151,11 +151,4 @@ Learn more about [incident preference best practices](/docs/new-relic-solutions/
 
 The **By condition and signal** option is the most granular level for creating incident records. Choose this incident preference when you want to closely monitor anything that is occurring anywhere across your infrastructure.
 
-Learn more about [incident preference best practices](/docs/new-relic-solutions/best-practices-guides/alerts-applied-intelligence/alerts-best-practices/#incident-practices).
-
-## For more help [#more_help]
-
-Additional documentation resources include:
-
-* [Alert policy workflow](/docs/alerts/new-relic-alerts-beta/configuring-alert-policies/alert-policy-workflow) (basic process to set up your alert policies, regardless of which New Relic product uses the alert policy)
-* [Explore the incident history](/docs/alerts/new-relic-alerts-beta/reviewing-alert-incidents/explore-incident-history) (examine details about alert policy violations, take action, and skim for patterns)
+Learn more about [incident preference best practices](/docs/new-relic-solutions/best-practices-guides/alerts-applied-intelligence/alerts-best-practices/#incident-practices).

src/content/docs/apis/intro-apis/new-relic-api-keys.mdx

@@ -52,7 +52,7 @@ Our keys can be broken down into two categories:
 
 There are many ways to [get data into New Relic](/docs/telemetry-data-platform/get-started/introduction-new-relic-data-ingest-apis-sdks). Here are the API keys used for data ingest: 
 
-* [License key](#ingest-license-key): our primary ingest key, used for APM ingest, infrastructure monitoring ingest, and our [ingest APIs](/docs/telemetry-data-platform/ingest-apis) and the integrations that use them. 
+* [License key](#ingest-license-key): our primary ingest key, used for APM ingest, infrastructure monitoring ingest, and our [ingest APIs](/docs/data-apis/ingest-apis) and the integrations that use them. 
 * [Browser key](#ingest-browser-key): used for browser monitoring ingest.
 * [Mobile app token](/docs/mobile-monitoring/new-relic-mobile/maintenance/viewing-your-application-token/): used for mobile monitoring ingest. 
 * [Insights insert key](#insights-insert-key): an older key that has been mostly deprecated, it has the same functionality as the license key. **We recommend using the license key instead.**

src/content/docs/apis/rest-api-v2/api-explorer-v2/introduction-new-relics-rest-api-explorer.mdx

@@ -50,6 +50,4 @@ Be aware there are some differences between version 2 and 1:
 
 <Callout variant="tip">
   The New Relic agents use different APIs and are not accessible via the API Explorer.
-</Callout>
-
-## For more help [#more_help]
+</Callout>

src/content/docs/apis/rest-api-v2/application-examples-v2/application-reporting-health-status-v2.mdx

@@ -80,11 +80,3 @@ The reporting status is provided by the `"reporting": true,` line returned as pa
 The [health status](/docs/accounts-partnerships/education/getting-started-new-relic/glossary#health-status) is provided by the `"health_status": "green",` line returned as part of the application status. The color returned in the API matches the app's health status indicators displayed in the UI.
 
 **Exception:** The REST API uses `orange` instead of `yellow`. If the application is not associated with an alert policy, it will show as `unknown`.
-
-## For more help [#more_help]
-
-Additional documentation resources include:
-
-* [Summary data](/docs/apm/apis/api-v2-examples/summary-data-examples) (examples of finding the application status in various ways)
-* [Extracting metric timeslice data](/docs/apis/extracting-metric-data) (time slice averages and policy considerations for data aggregation)
-* [API Explorer examples: Metric data](/docs/apis/api-explorer-examples-metric-data) (an example of how to obtain metric data for your app)

src/content/docs/apis/rest-api-v2/application-examples-v2/average-response-time-examples-v2.mdx

@@ -49,12 +49,4 @@ Your application may have zero queuing time for the time period in question. In
 
 ## Response time [#app_rep_time]
 
-On the [APM **Summary** page](/docs/applications-menu/applications-overview), [Response time](/docs/data-analysis/user-interface-functions/view-your-data/response-time) is the overlaid line within the main chart for your app. To obtain the metric values shown by this line, use the same formula and two commands described above, but remove `summarize=true` from the commands.
-
-## For more help [#more_help]
-
-[Additional documentation resources include:](/docs/data-analysis/user-interface-functions/view-your-data/response-time)
-
-* [Extracting metric timeslice data](/docs/apis/extracting-metric-data) (time slice averages and policy considerations for data aggregation)
-* [Using the API Explorer](/docs/apis/using-the-api-explorer) (using the API Explorer's user interface to get data in and data out of New Relic)
-* [Getting started with the New Relic REST API (v2)](/docs/apm/apis/requirements/getting-started-new-relic-rest-api-v2) (overview of the New Relic REST API, including the structure of an API call)
+On the [APM **Summary** page](/docs/applications-menu/applications-overview), [Response time](/docs/data-analysis/user-interface-functions/view-your-data/response-time) is the overlaid line within the main chart for your app. To obtain the metric values shown by this line, use the same formula and two commands described above, but remove `summarize=true` from the commands.