updated articles per Eng feedback

Author: MGoedtel

articles/azure-monitor/insights/container-insights-azure-redhat4-setup.md

@@ -2,7 +2,7 @@
 title: Configure Azure Red Hat OpenShift v4.x with Azure Monitor for containers | Microsoft Docs
 description: This article describes how to configure monitoring of a Kubernetes cluster with Azure Monitor hosted on Azure Red Hat OpenShift version 4 and higher.
 ms.topic: conceptual
-ms.date: 04/16/2020
+ms.date: 04/22/2020
 ---
 
 # Configure Azure Red Hat OpenShift v4.x with Azure Monitor for containers
@@ -26,10 +26,14 @@ Azure Monitor for containers supports monitoring Azure Red Hat OpenShift v4.x as
 
 ## Prerequisites
 
+- Azure CLI version 2.0.72 or greater
+
 - [Helm 3](https://helm.sh/docs/intro/install/) CLI tool
 
 - [Bash version 4](https://www.gnu.org/software/bash/)
 
+- [Kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/) command-line tool
+
 - To enable and access the features in Azure Monitor for containers, at a minimum you need to be a member of the Azure *Contributor* role in the Azure subscription, and a member of the [*Log Analytics Contributor*](../platform/manage-access.md#manage-access-using-azure-permissions) role of the Log Analytics workspace configured with Azure Monitor for containers.
 
 - To view the monitoring data, you are a member of the [*Log Analytics reader*](../platform/manage-access.md#manage-access-using-azure-permissions) role permission with the Log Analytics workspace configured with Azure Monitor for containers.
@@ -48,50 +52,55 @@ Perform the following steps to enable monitoring of an Azure Red Hat OpenShift v
 
     `curl -LO https://raw.githubusercontent.com/microsoft/OMS-docker/ci_feature/docs/aroV4/onboarding_azuremonitor_for_containers.sh.`
 
-
 3. To identify the **kube-context** of your cluster, after successful `oc login` on to your cluster, run the command `kubectl config current-context` and copy the value.
 
-4. The following step enables monitoring of your cluster using the bash script you downloaded earlier. To integrate with an existing Log Analytics workspace, perform the following steps to first identify the full resource ID of your Log Analytics workspace required for the `workspaceResourceId` parameter, and then run the command to enable the monitoring add-on against the specified workspace. If you don't have a workspace to specify, you can skip to step 5 and let the script create a new workspace for you.
+### Integrate with an existing workspace
 
-    1. List all the subscriptions that you have access to using the following command:
+The following step enables monitoring of your cluster using the bash script you downloaded earlier. To integrate with an existing Log Analytics workspace, perform the following steps to first identify the full resource ID of your Log Analytics workspace required for the `workspaceResourceId` parameter, and then run the command to enable the monitoring add-on against the specified workspace. If you don't have a workspace to specify, you can skip to step 5 and let the script create a new workspace for you.
 
-        ```azurecli
-        az account list --all -o table
-        ```
+1. List all the subscriptions that you have access to using the following command:
 
-        The output will resemble the following:
+    ```azurecli
+    az account list --all -o table
+    ```
 
-        ```azurecli
-        Name                                  CloudName    SubscriptionId                        State    IsDefault
-        ------------------------------------  -----------  ------------------------------------  -------  -----------
-        Microsoft Azure                       AzureCloud   68627f8c-91fO-4905-z48q-b032a81f8vy0  Enabled  True
-        ```
+    The output will resemble the following:
 
-        Copy the value for **SubscriptionId**.
+    ```azurecli
+    Name                                  CloudName    SubscriptionId                        State    IsDefault
+    ------------------------------------  -----------  ------------------------------------  -------  -----------
+    Microsoft Azure                       AzureCloud   68627f8c-91fO-4905-z48q-b032a81f8vy0  Enabled  True
+    ```
 
-    2. Switch to the subscription hosting the Log Analytics workspace using the following command:
+    Copy the value for **SubscriptionId**.
 
-        ```azurecli
-        az account set -s <subscriptionId of the workspace>
-        ```
+2. Switch to the subscription hosting the Log Analytics workspace using the following command:
 
-    3. The following example displays the list of workspaces in your subscriptions in the default JSON format.
+    ```azurecli
+    az account set -s <subscriptionId of the workspace>
+    ```
+
+3. The following example displays the list of workspaces in your subscriptions in the default JSON format.
 
-        ```
-        az resource list --resource-type Microsoft.OperationalInsights/workspaces -o json
-        ```
+    ```
+    az resource list --resource-type Microsoft.OperationalInsights/workspaces -o json
+    ```
 
-        In the output, find the workspace name, and then copy the full resource ID of that Log Analytics workspace under the field **ID**.
+    In the output, find the workspace name, and then copy the full resource ID of that Log Analytics workspace under the field **ID**.
 
-    4. Run the following command to enable monitoring, replacing the value for the `workspaceResourceId` parameter: 
+4. Run the following command to enable monitoring, replacing the value for the `workspaceResourceId` parameter: 
 
-        `bash onboarding_azuremonitor_for_containers.sh <kube-context> <azureAroV4ResourceId> <LogAnayticsWorkspaceResourceId>`
+    `bash onboarding_azuremonitor_for_containers.sh <kube-context> <azureAroV4ResourceId> <LogAnayticsWorkspaceResourceId>`
 
-        Example:
+    Example:
+
+    `bash onboarding_azuremonitor_for_containers.sh MyK8sTestCluster /subscriptions/57ac26cf-a9f0-4908-b300-9a4e9a0fb205/resourceGroups/test-aro-v4-rg/providers/Microsoft.RedHatOpenShift/OpenShiftClusters/test-aro-v4  /subscriptions/57ac26cf-a9f0-4908-b300-9a4e9a0fb205/resourcegroups/test-la-workspace-rg/providers/microsoft.operationalinsights/workspaces/test-la-workspace`
+
+After you've enabled monitoring, it might take about 15 minutes before you can view health metrics for the cluster.
 
-        `bash onboarding_azuremonitor_for_containers.sh MyK8sTestCluster /subscriptions/57ac26cf-a9f0-4908-b300-9a4e9a0fb205/resourceGroups/test-aro-v4-rg/providers/Microsoft.RedHatOpenShift/OpenShiftClusters/test-aro-v4  /subscriptions/57ac26cf-a9f0-4908-b300-9a4e9a0fb205/resourcegroups/test-la-workspace-rg/providers/microsoft.operationalinsights/workspaces/test-la-workspace`
+### Integrate with default workspace
 
-5. The following step enables monitoring of your Azure Red Hat OpenShift v4.x cluster using the bash script you downloaded. In this example, you are not required to per-create or specify an existing workspace. This command simplifies the process for you by creating a default workspace in the default resource group of the cluster subscription if one does not already exist in the region. The default workspace created resembles the format of *DefaultWorkspace-\<GUID>-\<Region>*.  
+The following step enables monitoring of your Azure Red Hat OpenShift v4.x cluster using the bash script you downloaded. In this example, you are not required to per-create or specify an existing workspace. This command simplifies the process for you by creating a default workspace in the default resource group of the cluster subscription if one does not already exist in the region. The default workspace created resembles the format of *DefaultWorkspace-\<GUID>-\<Region>*.  
 
     `bash onboarding_azuremonitor_for_containers.sh <kube-context> <azureAroV4ResourceId>`
 

articles/azure-monitor/insights/container-insights-hybrid-setup.md

@@ -2,7 +2,7 @@
 title: Configure Hybrid Kubernetes clusters with Azure Monitor for containers | Microsoft Docs
 description: This article describes how you can configure Azure Monitor for containers to monitor Kubernetes clusters hosted on Azure Stack or other environment.
 ms.topic: conceptual
-ms.date: 04/17/2020
+ms.date: 04/22/2020
 ---
 
 # Configure hybrid Kubernetes clusters with Azure Monitor for containers
@@ -23,7 +23,7 @@ The following is officially supported with Azure Monitor for containers.
 
 * Versions of Kubernetes and support policy are the same as versions of [AKS supported](../../aks/supported-kubernetes-versions.md).
 
-* Container Runtime: Docker, Moby, and CRI-O
+* Container Runtime: Docker, Moby, and CRI compatible runtimes such CRI-O and ContainerD.
 
 * Linux OS release for master and worked nodes: Ubuntu (18.04 LTS and 16.04 LTS), and Red Hat Enterprise Linux CoreOS 43.81.
 

articles/azure-monitor/insights/container-insights-prometheus-integration.md

@@ -2,7 +2,7 @@
 title: Configure Azure Monitor for containers Prometheus Integration | Microsoft Docs
 description: This article describes how you can configure the Azure Monitor for containers agent to scrape metrics from Prometheus with your Kubernetes cluster.
 ms.topic: conceptual
-ms.date: 04/21/2020
+ms.date: 04/22/2020
 ---
 
 # Configure scraping of Prometheus metrics with Azure Monitor for containers
@@ -24,10 +24,6 @@ Scraping of Prometheus metrics is supported with Kubernetes clusters hosted on:
 - Azure Red Hat OpenShift version 3.x
 - Azure Red Hat OpenShift and Red Hat OpenShift version 4.x
 
-
-
-
->
 ### Prometheus scraping settings
 
 Active scraping of metrics from Prometheus is performed from one of two perspectives:
@@ -66,7 +62,7 @@ Perform the following steps to configure your ConfigMap configuration file for t
 
 * Azure Kubernetes Service (AKS)
 * Azure Stack or on-premises
-* Azure Red Hat OpenShift version 4.x
+* Azure Red Hat OpenShift version 4.x and Red Hat OpenShift version 4.x
 
 1. [Download](https://github.com/microsoft/OMS-docker/blob/ci_feature_prod/Kubernetes/container-azm-ms-agentconfig.yaml) the template ConfigMap yaml file and save it as container-azm-ms-agentconfig.yaml.