Merge branch 'Deleting-some-dummy-docs-' into clang/update-nav-file-n…

…odes

src/content/docs/alerts-applied-intelligence/new-relic-alerts/get-started/your-first-nrql-condition.mdx

@@ -0,0 +1,84 @@
+---
+title: Write your first NRQL alerts condition
+tags:
+  - Alerts and Applied Intelligence
+  - New Relic Alerts
+  - Alert conditions
+  - NRQL
+metaDescription: How to start writing NRQL alerts conditions with a step-by-step user case.
+---
+
+Use our [New Relic query language (NRQL)](/docs/query-your-data/nrql-new-relic-query-language/get-started/introduction-nrql-new-relics-query-language/) to create alerts conditions with ease.
+
+Your condition describes what you want to be notified about, and only requires two attributes: a query and a threshold. The query defines the data that's important to you, and determines what you want to be notified about. The threshold determines when you’ll be notified.
+
+Follow these steps to write your first alerts condition using a NRQL query and a threshold. Once you're done, you'll have a working alert condition.
+
+## Step 1: Write your query [#step1-nrql]
+
+In this example, a condition is created for each host's CPU utilization (query), which will trigger a notification when the CPU utilization is above 70% (threshold).
+
+You can use a NRQL query to return data about how your environment is performing. Then you can create a condition from that query. Find the [NRQL query builder](/docs/query-your-data/explore-query-data/query-builder/use-advanced-nrql-mode-query-data/) at the top of the UI.
+
+![A screenshot showing where you can find the NRQL query builder button in New Relic One.](./images/find-builder.png 'A screenshot showing where you can find the NRQL query builder button in New Relic One.')
+
+<figcaption>
+  Click the **Query your data** button to open the query builder and start writing a NRQL query. Once you've written a valid query, you can create a condition from it.
+</figcaption>
+
+The condition shows each host’s CPU utilization. Use this NRQL query, or something similar that's relevant to what you're monitoring, to create a condition.
+
+![A screenshot of a NRQL query that finds the average CPU utilization faceted by hostname.](./images/nrql-query.png 'A screenshot of a NRQL query that finds the average CPU utilization faceted by hostname.')
+
+<figcaption>
+  This query finds the average CPU utilization in an environment and then breaks it
+  down (facets) by individual host names.
+</figcaption>
+
+Once you've created a valid NRQL query, click the **Create alert** button.
+
+Learn more about the [NRQL syntax](/docs/query-your-data/nrql-new-relic-query-language/get-started/introduction-nrql-new-relics-query-language/#syntax) to create a variety of queries.
+
+## Step 2: Name and revise your NRQL condition [#step2-nrql]
+
+Give your NRQL condition a name that's meaningful to you. Your query's visualization is shown automatically.
+
+![The query's visualization shows each host’s average CPU utilization.](./images/show-nrql-graph.png 'The query's visualization shows each host’s average CPU utilization.')
+
+<figcaption>
+  The query's visualization shows each host’s average CPU utilization. A critical violation will open if any host’s average CPU utilization is over 70%. A warning threshold is met at 67%.
+
+  Warning thresholds are described below.
+</figcaption>
+
+## Step 3: Set your condition thresholds [#step3-nrql]
+
+Set critical and warning thresholds to determine when you’re notified about your environment's performance. 
+
+In this example, our critical threshold (red) checks for any hosts with CPU utilization over 70% for at least 5 minutes. A warning threshold (yellow) is also added showing when any host's CPU utilization goes over 67% for at least 5 minutes.
+
+![A visualization of the NRQL query with critical and warning threshold lines.](./images/nrql-set-threshold.png 'A visualization of the NRQL query with critical and warning threshold lines.')
+
+<figcaption>
+  Use the **Set your condition thresholds** section to set the critical and warning thresholds for your condition.
+</figcaption>
+
+A critical threshold is required for your alerts condition. [Warning thresholds](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/set-thresholds-alert-condition/#threshold-levels) are optional. 
+
+Warning thresholds don't create an incident or notify you like the critical threshold does. If a critical threshold opens an incident and notifies you, warning threshold violations created after will be included in the report.
+
+## Step 4: Create a policy
+
+Finally, add your condition to an existing policy or create a new one.
+
+![A screenshot of the Policy section for the Create alert form.](./images/nrql-create-policy.png 'A screenshot of the Policy section for the Create alert form.')
+
+<figcaption>
+  When you create a new policy, you can group your violations by policy, condition, or by violation (this creates an incident for each violation). These [incident preferences](/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/specify-when-alerts-create-incidents/) settings determine how frequently you're notified when there's a violation.
+</figcaption>
+
+## What's next? [#nextsteps-nrql]
+
+Now that you've created your first condition, set up your [incident preferences](/docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/specify-when-alerts-create-incidents/) and [notification channels](/docs/alerts-applied-intelligence/new-relic-alerts/alert-notifications/notification-channels-control-where-send-alerts/). 
+
+For a detailed, comprehensive overview of NRQL conditions, see [Create NRQL alert conditions](/docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/create-nrql-alert-conditions/)

src/content/docs/apis/nerdgraph/examples/nerdgraph-cloud-integrations-api-tutorial.mdx

@@ -349,7 +349,7 @@ Mutations are requests that are intended to have side effects, such as creating
   </Collapser>
 
   <Collapser
-    id="link-aws"
+    id="link-aws-cloudwatch"
     title="Link an Amazon AWS account using CloudWatch Metric Streams"
   >
     This mutation links an Amazon AWS account sending data through CloudWatch Metric Streams to your New Relic account.

src/content/docs/browser/single-page-app-monitoring/troubleshooting/missing-route-changes-spa-agent.mdx

@@ -14,7 +14,7 @@ redirects:
 
 You are using the Pro + SPA agent, but you are not seeing all of the `route change` browser interactions you expect.
 
-We are aware that this can be frustrating. Our goal in summer 2020 is to reevaluate the SPA feature functionality, making it simpler and more reliable, starting with the methods we use to detect and capture route changes. Additionally, we plan to add new frameworks and use cases to our testing suite based on your feedback and examples. Likely this work will include new APIs as well as framework-specific plug-ins. Check our [release notes](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes) for the latest updates.
+We are aware that this can be frustrating. Our goal throughout 2021 is to reevaluate the SPA feature functionality, making it simpler and more reliable, starting with the methods we use to detect and capture route changes. Additionally, we plan to add new frameworks and use cases to our testing suite based on your feedback and examples. Likely this work will include new APIs as well as framework-specific plug-ins. Check our [release notes](/docs/release-notes/new-relic-browser-release-notes/browser-agent-release-notes) for the latest updates.
 
 ## Solution
 

src/content/docs/full-stack-observability/instrument-everything/get-started-new-relic-instrumentation/introduction-new-relic-integrations.mdx

@@ -185,8 +185,6 @@ redirects:
   - /docs/plugins/plugins-new-relic/using-plugins/viewing-plugins-dashboards
   - /docs/plugins/plugins-new-relic/using-plugins/viewing-plugin-alerts
   - /docs/plugins/plugins-new-relic/installing-plugins/use-plugin-central-plugin
-  - /docs/plugins
-  - /docs/plugins/new-relic-plugins
   - /docs/plugins/plugin-developer-resources
   - /docs/plugins/plugin-developer-resources/develop-plugins
   - /docs/plugins/plugin-developer-resources/developer-reference

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

@@ -27,6 +27,8 @@ import otherlinux from './images/otherlinux.png'
 
 import windows from './images/windows.png'
 
+import macOSX from './images/mac-osx-logo.png'
+
 New Relic's infrastructure monitoring agent is a [lightweight](/docs/infrastructure/new-relic-infrastructure/getting-started/infrastructure-agent-performance-overhead) executable file that collects [data about your hosts](/docs/infrastructure/manage-your-data/data-instrumentation/default-infrastructure-events). It also forwards data from [infrastructure integrations](/docs/integrations/infrastructure-integrations/get-started/introduction-infrastructure-integrations) to New Relic, as well as [log data](/docs/logs/enable-log-monitoring-new-relic/enable-log-monitoring-new-relic/forward-your-logs-using-infrastructure-agent) for log analytics.
 
 There are multiple ways to install and deploy the infrastructure monitoring agent, depending on your setup and needs. This document describes how the infrastructure monitoring agent works and how to install it.
@@ -79,9 +81,9 @@ If you want to collect data about core services running on your host, you need t
 
 ## Install the infrastructure monitoring agent [#install]
 
-If our guided install doesn't work for your setup, follow the instructions for your Linux, Windows, or other setup.
+If our guided install doesn't work for your setup, follow the instructions for your Linux, Windows, macOS or other setup.
 
-The infrastructure monitoring agent can currently run on many Linux distributions, as well as Windows Server. For more information on where you can run the agent, check the [compatibility and requirements](/docs/infrastructure/infrastructure-monitoring/get-started/compatibility-requirements-infrastructure-agent) page.
+The infrastructure monitoring agent can currently run on many Linux distributions, Windows, and macOS. For more information on where you can run the agent, check the [compatibility and requirements](/docs/infrastructure/infrastructure-monitoring/get-started/compatibility-requirements-infrastructure-agent) page.
 
 ### Linux [#Linux]
 
@@ -165,6 +167,8 @@ The infrastructure monitoring agent can be deployed programmatically using sever
 * <ImageSizing width="32px" height="32px" verticalAlign="middle">![EBS](./images/ebs.png "EBS")</ImageSizing>[Elastic Beanstalk](/docs/infrastructure/install-infrastructure-agent/config-management-tools/install-infrastructure-agent-aws-elastic-beanstalk)
 * <ImageSizing width="32px" height="32px" verticalAlign="middle">![Puppet](./images/puppet-logo.png "Puppet")</ImageSizing> [Puppet](/docs/infrastructure/new-relic-infrastructure/config-management-tools/configure-new-relic-infrastructure-puppet)
 
+Infrastructre can also be [deployed in macOS](/docs/infrastructure/install-infrastructure-agent/macos-installation/install-infrastructure-monitoring-agent-macos/).
+
 ## Check the source code [#source-code]
 
 The infrastructure monitoring agent is open source software. That means you can [browse its source code](https://github.com/newrelic/infrastructure-agent) and [send improvements](https://github.com/newrelic/infrastructure-agent/blob/master/CONTRIBUTING.md), or create your own fork and build it. For more information, see the [README](https://github.com/newrelic/infrastructure-agent/blob/master/README.md).

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

@@ -25,6 +25,7 @@ The infrastructure agent supports these processor architectures:
 * **Linux**: 64-bit for x86 processor architectures (also requires 64-bit package manager and dependencies)
 * **Windows**: both 32 and 64-bit for x86 processor architectures
 * **ARM**: arm64 architecture including [AWS Graviton 2 processor](https://aws.amazon.com/ec2/graviton/) is supported on compatible Linux operating sytems. On-host integrations are also supported (with the exception of the Oracle integration). Built-in log forwarding is not yet available.
+* **macOS** (Beta): 64-bit x86 processor (M1 processor is not officially supported yet). 
 
 ## Operating systems
 
@@ -135,6 +136,16 @@ The infrastructure agent supports these operating systems up to their manufactur
         Windows 10 (only the infrastructure agent is supported).
       </td>
     </tr>
+
+    <tr>
+      <td>
+        <ImageSizing width="32px" height="32px" verticalAlign="middle">![macOS icon](./images/mac-osx-logo.png "macOS")</ImageSizing>[macOS](/docs/infrastructure-install-macos)
+      </td>
+
+      <td>
+        macOS 10.14 (Mohave), 10.15 (Catalina), 11 (Big Sur).
+      </td>
+    </tr>
   </tbody>
 </table>
 
@@ -157,6 +168,7 @@ The infrastructure agent requires these permissions:
 
 * **Linux**: By default, [the agent runs and installs as root](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/installation/install-infrastructure-agent-linux#agent-mode-intro). You can also select [privileged](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/installation/install-infrastructure-agent-linux#install-privileged) or [unprivileged](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/installation/install-infrastructure-agent-linux#install-unprivileged) run modes.
 * **Windows**: The agent must be installed from an Administrator account and requires Administrator privileges to run.
+* **macOS**: The agent can be installed from any user account.
 
 ## Libraries
 

src/content/docs/infrastructure/install-infrastructure-agent/macos-installation/install-infrastructure-monitoring-agent-macos.mdx

@@ -0,0 +1,90 @@
+---
+title: Install the infrastructure monitoring agent for macOS
+tags:
+  - Infrastructure
+  - Install the infrastructure agent
+  - macOS installation
+translate:
+  - jp
+metaDescription: 'Install New Relic infrastructure monitoring agent for macOS using Homebrew.'
+---
+
+import macOS from './images/mac-osx-logo.png'
+
+With New Relic's infrastructure monitoring agent for macOS (Beta), you can monitor key performance metrics on macOS hosts. The agent can run on your own hardware or in cloud systems such as Amazon EC2.
+
+The infrastructure monitoring agent [is compatible](/docs/infrastructure/install-infrastructure-agent/get-started/requirements-infrastructure-agent) with all generally available, Apple supported macOS versions.
+
+<Callout variant="tip">
+  To use infrastructure monitoring and the rest of our [observability platform](https://one.newrelic.com), join the New Relic family! [Sign up](https://newrelic.com/signup) to create your free account in only a few seconds. Then ingest up to 100GB of data for free each month. Forever.
+</Callout>
+
+## Install for macOS (Beta) [#install-macos]
+
+Before installation, be sure to review the [requirements](/docs/infrastructure/new-relic-infrastructure/getting-started/compatibility-requirements-new-relic-infrastructurets). Then, to install the infrastructure monitoring agent for macOS, you can use our [Guided Install](/docs/full-stack-observability/observe-everything/get-started/new-relic-guided-install-overview/), or follow the instructions in this document to complete a basic installation.
+
+## Limitations (Beta) [#limitations]
+
+The following capabilities of the infrastructure agent are not yet available on macOS:
+  * [Process Monitoring](/attribute-dictionary/?event=ProcessSample). 
+  * [Log forwarder](/docs/logs/enable-log-management-new-relic/enable-log-monitoring-new-relic/forward-your-logs-using-infrastructure-agent/).
+  * [On-host integrations](/docs/integrations/host-integrations/get-started/introduction-host-integrations/) (including built-in integrations such as Docker and Flex).
+  * Automated deployment via Configuration Management tools (Chef, Ansible, Puppet).
+
+## Step-by-step instructions [#instructions]
+
+To install the infrastructure monitoring agent, follow the step-by-step instructions:
+
+<CollapserGroup>
+  <Collapser
+    id="homebrew-install"
+    title="Homebrew install"
+  >
+    1. Review the [agent requirements and supported operating systems](/docs/infrastructure/new-relic-infrastructure/getting-started/compatibility-requirements-new-relic-infrastructure).
+    2. Make sure [Homebrew](https://brew.sh/) is installed in the system. 
+    You can check if Homebrew is installed with:
+
+    ```
+      which brew
+    ```
+
+    If it's not installed, you can install it with this command (or check [Homebrew](https://brew.sh/) up-to-date instructions):
+
+    ```
+      /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
+    ```
+
+    3. Create the configuration file and add your [license key](/docs/accounts-partnerships/accounts/account-setup/license-key/):
+
+    ```
+      echo "license_key: YOUR_LICENSE_KEY" | sudo tee -a /usr/local/etc/newrelic-infra/newrelic-infra.yml
+    ```
+
+    4. Then, open the terminal and run the following command:    
+
+    ```
+      brew install newrelic-infra -q
+    ```
+
+    5. Start the infrastructe agent service:
+
+    ```
+      brew services start newrelic-infra-agent
+    ```
+  </Collapser>
+
+</CollapserGroup>
+
+Wait a few minutes, then [view your server in the Infrastructure UI](/docs/infrastructure/new-relic-infrastructure/infrastructure-ui-pages/infrastructure-compute-page-measure-resource-usage). If no data appears after waiting a few minutes, follow the [troubleshooting steps](/docs/infrastructure/new-relic-infrastructure/troubleshooting/no-data-appears-infrastructure).
+
+## What's next? [#configure]
+
+The only required [configuration option](/docs/infrastructure/install-configure-infrastructure/configuration/configure-infrastructure-agent) is the [`license_key`](/docs/Infrastructure-configure-your-agent#conf-license_key) setting, which is created as part of the installation procedures. You may also want to:
+
+* [Add custom attributes](/docs/Infrastructure-configure-your-agent#conf-custom_attributes) to annotate your infrastructure data.
+* [Connect your AWS account](/docs/infrastructure-amazon-aws-ec2-integration#connect) if your servers are hosted on Amazon EC2.
+* Add other [New Relic infrastructure integrations](/docs/infrastructure/integrations-getting-started/getting-started/introduction-infrastructure-integrations) to collect data from external services.
+
+## Update the agent [#update]
+
+To upgrade to the latest version, follow standard procedures to [update the infrastructure monitoring agent](/docs/infrastructure/new-relic-infrastructure/installation/update-infrastructure-agent).

src/content/docs/infrastructure/install-infrastructure-agent/manage-your-agent/infrastructure-agent-behavior.mdx

@@ -55,6 +55,7 @@ There are no automatic updates to agents. To install a new agent version:
 
 * Linux: Manually install agent versions through the appropriate package manager (apt, yum, zypper).
 * Windows: Manually download the `msi` package and install it with `msiexec.exe`.
+* macOS: Manually install agent versions through HomeBrew.
 
 ## Retry behavior [#retry]
 

src/content/docs/infrastructure/install-infrastructure-agent/manage-your-agent/start-stop-restart-infrastructure-agent.mdx

@@ -88,6 +88,24 @@ For [Windows Server](/docs/infrastructure/new-relic-infrastructure/installation/
   (Get-Service newrelic-infra).Status
   ```
 
+## macOS: Start, stop, restart, or check agent status [#macOS]
+
+* Stop or start the agent:
+  ```
+    brew services stop newrelic-infra-agent
+    brew services start newrelic-infra-agent
+  ```
+
+* Restart the agent:
+  ```
+    brew services restart newrelic-infra-agent
+  ```
+* Check status of the agent:
+  ```
+    brew services list
+  ```
+
+
 ## Customize agent logs [#logging]
 
 The infrastructure agent logs to a default location which depends on your platform. You can customize this location with the [`log_file`](/docs/infrastructure/install-configure-infrastructure/configuration/infrastructure-configuration-settings#log-file) setting. You can also [generate verbose logs for troubleshooting](/docs/infrastructure/new-relic-infrastructure/troubleshooting/generating-logs-troubleshooting-infrastructure).