Merge pull request #109152 from MGoedtel/task1701291b

update to the other process explanation

Author: PRMerger14

articles/azure-monitor/faq.md

@@ -499,17 +499,17 @@ This Microsoft FAQ is a list of commonly asked questions about Azure Monitor for
 
 ### What does *Other Processes* represent under the Node view?
 
-**Other processes** is intended to help you clearly understand the root cause of the high CPU usage on your node. This enables you to distinguish usage between containerized processes vs non-containerized processes. 
+**Other processes** is intended to help you clearly understand the root cause of the high resource usage on your node. This enables you to distinguish usage between containerized processes vs non-containerized processes.
 
 What are these **Other Processes**? 
 
 These are non-containerized processes that run on your node.  
 
 How do we calculate this?
 
-**Other Processes** = Total usage from CAdvisor - Usage from containerized process
+**Other Processes** = *Total usage from CAdvisor* - *Usage from containerized process*
 
-The **Other processes** can include: 
+The **Other processes** includes:
 
 - Self-managed or managed Kubernetes non-containerized processes 
 
@@ -519,7 +519,7 @@ The **Other processes** can include:
 
 - System processes running on your node 
 
-- Other non-kubernetes workloads running on node hardware or VM 
+- Other non-Kubernetes workloads running on node hardware or VM 
 
 ### I don't see Image and Name property values populated when I query the ContainerLog table.
 

articles/azure-monitor/insights/container-insights-analyze.md

@@ -2,7 +2,7 @@
 title: Kubernetes monitoring with Azure Monitor for containers | Microsoft Docs
 description: This article describes how you can view and analyze the performance of a Kubernetes cluster with Azure Monitor for containers.
 ms.topic: conceptual
-ms.date: 01/07/2020
+ms.date: 03/26/2020
 ---
 
 # Monitor your Kubernetes cluster performance with Azure Monitor for containers
@@ -52,7 +52,7 @@ The health statuses included are:
 * **Warning**: One or more issues are detected that must be addressed or the health condition could become critical.
 * **Unknown**: If the service wasn't able to make a connection with the node or pod, the status changes to an Unknown state.
 * **Not found**: Either the workspace, the resource group, or subscription that contains the workspace for this solution was deleted.
-* **Unauthorized**: User doesn’t have required permissions to read the data in the workspace.
+* **Unauthorized**: User doesn't have required permissions to read the data in the workspace.
 * **Error**: An error occurred while attempting to read data from the workspace.
 * **Misconfigured**: Azure Monitor for containers wasn't configured correctly in the specified workspace.
 * **No data**: Data hasn't reported to the workspace for the last 30 minutes.
@@ -195,6 +195,20 @@ The information that's presented when you view the **Nodes** tab is described in
 | Controller | Only for containers and pods. It shows which controller it resides in. Not all pods are in a controller, so some might display **N/A**. | 
 | Trend Min %, Avg %, 50th %, 90th %, 95th %, Max % | Bar graph trend represents the average percentile metric percentage of the controller. |
 
+You may notice a workload after expanding a node named **Other process**. It represents non-containerized processes that run on your node, and includes:
+
+* Self-managed or managed Kubernetes non-containerized processes
+
+* Container run-time processes  
+
+* Kubelet  
+
+* System processes running on your node
+
+* Other non-Kubernetes workloads running on node hardware or VM
+
+It is calculated by: *Total usage from CAdvisor* - *Usage from containerized process*.  
+
 In the selector, select **Controllers**.
 
 ![Select Controllers view](./media/container-insights-analyze/containers-controllers-tab.png)