Due to a divergence in table data between Azure Stack Edge and Data Box Gateway, I had to pull the table data out for metics out the include file into a new bookmarked section for both device monitor topics. Both *-monitor files has duplicate content for two of the tables but ASE has an additional table listing Edge compute metrics, whereas DBG does not.

priestlg · priestlg · commit 051a1ebb8172 · 2020-05-19T17:07:26.000-07:00
diff --git a/articles/databox-online/azure-stack-edge-monitor.md b/articles/databox-online/azure-stack-edge-monitor.md
@@ -40,6 +40,39 @@ Take the following steps in the local web UI to view the hardware status of your
 
 [!INCLUDE [Supported OS for clients connected to device](../../includes/data-box-edge-gateway-view-metrics.md)]
 
+### Metrics on your device
+
+This section describes the monitoring metrics on your device. The metrics can be:
+
+* Capacity metrics. The capacity metrics are related to the capacity of the device.
+
+* Transaction metrics. The transaction metrics are related to the read and write operations to Azure Storage.
+
+* Edge compute metrics. The Edge compute metrics are related to the usage of the Edge compute on your device.
+
+A full list of the metrics is shown in the following table:
+
+|Capacity metrics                     |Description  |
+|-------------------------------------|-------------|
+|**Available capacity**               | Refers to the size of the data that can be written to the device. In other words, this is the capacity that can be made available on the device. <br></br>You can free up the device capacity by deleting the local copy of files that have a copy on both the device as well as the cloud.        |
+|**Total capacity**                   | Refers to the total bytes on the device to write data to. This is also referred to as the total size of the local cache. <br></br> You can now increase the capacity of an existing virtual device by adding a data disk. Add a data disk through the hypervisor management for the VM and then restart your VM. The local storage pool of the Gateway device will expand to accommodate the newly added data disk. <br></br>For more information, go to [Add a hard drive for Hyper-V virtual machine](https://www.youtube.com/watch?v=EWdqUw9tTe4). |
+
+|Transaction metrics              | Description         |
+|-------------------------------------|---------|
+|**Cloud bytes uploaded (device)**    | Sum of all the bytes uploaded across all the shares on your device        |
+|**Cloud bytes uploaded (share)**     | Bytes uploaded per share. This can be: <br></br> Avg, which is the (Sum of all the bytes uploaded per share / Number of shares),  <br></br>Max, which is the maximum number of bytes uploaded from a share <br></br>Min, which is the minimum number of bytes uploaded from a share      |
+|**Cloud download throughput (share)**| Bytes downloaded per share. This can be: <br></br> Avg, which is the (Sum of all bytes read or downloaded to a share / Number of shares) <br></br> Max, which is the maximum number of bytes downloaded from a share<br></br> and Min, which is the minimum number of bytes downloaded from a share  |
+|**Cloud read throughput**            | Sum of all the bytes read from the cloud across all the shares on your device     |
+|**Cloud upload throughput**          | Sum of all the bytes written to the cloud across all the shares on your device     |
+|**Cloud upload throughput (share)**  | Sum of all bytes written to the cloud from a share / # of shares is average, max, and min per share      |
+|**Read throughput (network)**           | Includes the system network throughput for all the bytes read from the cloud. This view can include data that is not restricted to shares. <br></br>Splitting will show the traffic over all the network adapters on the device. This includes adapters that are not connected or enabled.      |
+|**Write throughput (network)**       | Includes the system network throughput for all the bytes written to the cloud. This view can include data that is not restricted to shares. <br></br>Splitting will show the traffic over all the network adapters on the device. This includes adapters that are not connected or enabled.          |
+
+| Edge compute metrics              | Description         |
+|-------------------------------------|---------|
+|**Edge compute - memory usage**      |           |
+|**Edge compute - percentage CPU**    |         |
+
 ## Manage alerts
 
 [!INCLUDE [Supported OS for clients connected to device](../../includes/data-box-edge-gateway-manage-alerts.md)]
diff --git a/articles/databox-online/data-box-gateway-monitor.md b/articles/databox-online/data-box-gateway-monitor.md
@@ -30,6 +30,32 @@ In this article, you learn how to:
 
 [!INCLUDE [Supported OS for clients connected to device](../../includes/data-box-edge-gateway-view-metrics.md)]
 
+### Metrics on your device
+
+This section describes the monitoring metrics on your device. The metrics can be:
+
+* Capacity metrics. The capacity metrics are related to the capacity of the device.
+
+* Transaction metrics. The transaction metrics are related to the read and write operations to Azure Storage.
+
+A full list of the metrics is shown in the following table:
+
+|Capacity metrics                     |Description  |
+|-------------------------------------|-------------|
+|**Available capacity**               | Refers to the size of the data that can be written to the device. In other words, this is the capacity that can be made available on the device. <br></br>You can free up the device capacity by deleting the local copy of files that have a copy on both the device as well as the cloud.        |
+|**Total capacity**                   | Refers to the total bytes on the device to write data to. This is also referred to as the total size of the local cache. <br></br> You can now increase the capacity of an existing virtual device by adding a data disk. Add a data disk through the hypervisor management for the VM and then restart your VM. The local storage pool of the Gateway device will expand to accommodate the newly added data disk. <br></br>For more information, go to [Add a hard drive for Hyper-V virtual machine](https://www.youtube.com/watch?v=EWdqUw9tTe4). |
+
+|Transaction metrics              | Description         |
+|-------------------------------------|---------|
+|**Cloud bytes uploaded (device)**    | Sum of all the bytes uploaded across all the shares on your device        |
+|**Cloud bytes uploaded (share)**     | Bytes uploaded per share. This can be: <br></br> Avg, which is the (Sum of all the bytes uploaded per share / Number of shares),  <br></br>Max, which is the maximum number of bytes uploaded from a share <br></br>Min, which is the minimum number of bytes uploaded from a share      |
+|**Cloud download throughput (share)**| Bytes downloaded per share. This can be: <br></br> Avg, which is the (Sum of all bytes read or downloaded to a share / Number of shares) <br></br> Max, which is the maximum number of bytes downloaded from a share<br></br> and Min, which is the minimum number of bytes downloaded from a share  |
+|**Cloud read throughput**            | Sum of all the bytes read from the cloud across all the shares on your device     |
+|**Cloud upload throughput**          | Sum of all the bytes written to the cloud across all the shares on your device     |
+|**Cloud upload throughput (share)**  | Sum of all bytes written to the cloud from a share / # of shares is average, max, and min per share      |
+|**Read throughput (network)**           | Includes the system network throughput for all the bytes read from the cloud. This view can include data that is not restricted to shares. <br></br>Splitting will show the traffic over all the network adapters on the device. This includes adapters that are not connected or enabled.      |
+|**Write throughput (network)**       | Includes the system network throughput for all the bytes written to the cloud. This view can include data that is not restricted to shares. <br></br>Splitting will show the traffic over all the network adapters on the device. This includes adapters that are not connected or enabled.          |
+
 ## Manage alerts
 
 [!INCLUDE [Supported OS for clients connected to device](../../includes/data-box-edge-gateway-manage-alerts.md)]
diff --git a/includes/data-box-edge-gateway-view-metrics.md b/includes/data-box-edge-gateway-view-metrics.md
@@ -22,25 +22,7 @@ Take the following steps in the Azure portal to create a chart for selected devi
 
     ![Choose another resource](media/data-box-edge-gateway-view-metrics/view-metrics-3.png)
 
-3. From the dropdown list, select a metric to monitor your device. The metrics can be **Capacity metrics** or **Transaction metrics**. The capacity metrics are related to the capacity of the device. The transaction metrics are related to the read and write operations to Azure Storage.
-
-    |Capacity metrics                     |Description  |
-    |-------------------------------------|-------------|
-    |**Available capacity**               | Refers to the size of the data that can be written to the device. In other words, this is the capacity that can be made available on the device. <br></br>You can free up the device capacity by deleting the local copy of files that have a copy on both the device as well as the cloud.        |
-    |**Total capacity**                   | Refers to the total bytes on the device to write data to. This is also referred to as the total size of the local cache. <br></br> You can now increase the capacity of an existing virtual device by adding a data disk. Add a data disk through the hypervisor management for the VM and then restart your VM. The local storage pool of the Gateway device will expand to accommodate the newly added data disk. <br></br>For more information, go to [Add a hard drive for Hyper-V virtual machine](https://www.youtube.com/watch?v=EWdqUw9tTe4). |
-    
-    |Transaction metrics              | Description         |
-    |-------------------------------------|---------|
-    |**Cloud bytes uploaded (device)**    | Sum of all the bytes uploaded across all the shares on your device        |
-    |**Cloud bytes uploaded (share)**     | Bytes uploaded per share. This can be: <br></br> Avg, which is the (Sum of all the bytes uploaded per share / Number of shares),  <br></br>Max, which is the maximum number of bytes uploaded from a share <br></br>Min, which is the minimum number of bytes uploaded from a share      |
-    |**Cloud download throughput (share)**| Bytes downloaded per share. This can be: <br></br> Avg, which is the (Sum of all bytes read or downloaded to a share / Number of shares) <br></br> Max, which is the maximum number of bytes downloaded from a share<br></br> and Min, which is the minimum number of bytes downloaded from a share  |
-    |**Cloud read throughput**            | Sum of all the bytes read from the cloud across all the shares on your device     |
-    |**Cloud upload throughput**          | Sum of all the bytes written to the cloud across all the shares on your device     |
-    |**Cloud upload throughput (share)**  | Sum of all bytes written to the cloud from a share / # of shares is average, max, and min per share      |
-    |**Read throughput (network)**           | Includes the system network throughput for all the bytes read from the cloud. This view can include data that is not restricted to shares. <br></br>Splitting will show the traffic over all the network adapters on the device. This includes adapters that are not connected or enabled.      |
-    |**Write throughput (network)**       | Includes the system network throughput for all the bytes written to the cloud. This view can include data that is not restricted to shares. <br></br>Splitting will show the traffic over all the network adapters on the device. This includes adapters that are not connected or enabled.          |
-    |**Edge compute - memory usage**      |           |
-    |**Edge compute - percentage CPU**    |         |
+3. From the dropdown list, select a metric to monitor your device. The metrics can be **Capacity metrics**, **Transaction metrics**, or **Edge compute metrics**. The capacity metrics are related to the capacity of the device. The transaction metrics are related to the read and write operations to Azure Storage. For a full list of these metrics, see [Metrics on your device](#metrics-on-your-device).
 
 4. When a metric is selected from the dropdown list, aggregation can also be defined. Aggregation refers to the actual value aggregated over a specified span of time. The aggregated values can be average, minimum, or the maximum value. Select the Aggregation from Avg, Max, or Min.
 
