Curate for Monitor duplication

Author: cdpark

articles/container-instances/container-instances-image-security.md

@@ -130,7 +130,7 @@ Monitor your resource activity, like files, network, and other resources that yo
 
 [Azure Monitor](../azure-monitor/overview.md) enables core monitoring for Azure services by allowing the collection of metrics, activity logs, and diagnostic logs. For example, the activity log tells you when new resources are created or modified. 
 
-  Metrics are available that provide performance statistics for different resources and even the operating system inside a virtual machine. You can view this data with one of the explorers in the Azure portal and create alerts based on these metrics. Azure Monitor provides the fastest metrics pipeline (5 minutes down to 1 minute), so you should use it for time-critical alerts and notifications. 
+  Metrics are available that provide performance statistics for different resources and even the operating system inside a virtual machine. You can view this data with one of the explorers in the Azure portal and [create alerts](monitor-azure-container-instances.md#alerts) based on these metrics.
 
 ### Log all container administrative user access for auditing 
 

articles/container-instances/container-instances-log-analytics.md

@@ -150,63 +150,13 @@ ContainerInstanceLog_CL
 
 ## Log schema
 
-> [!NOTE]
-> Some of the columns listed in the following table only exist as part of the schema, and won't have any data emitted in logs. These columns are denoted with a description of 'Empty'.
-
-### ContainerInstanceLog_CL
-
-|Column|Type|Description|
-|-|-|-|
-|Computer|string|Empty|
-|ContainerGroup_s|string|The name of the container group associated with the record|
-|ContainerID_s|string|A unique identifier for the container associated with the record|
-|ContainerImage_s|string|The name of the container image associated with the record|
-|Location_s|string|The location of the resource associated with the record|
-|Message|string|If applicable, the message from the container|
-|OSType_s|string|The name of the operating system the container is based on|
-|RawData|string|Empty|
-|ResourceGroup|string|Name of the resource group that the record is associated with|
-|Source_s|string|Name of the logging component, "LoggingAgent"|
-|SubscriptionId|string|A unique identifier for the subscription that the record is associated with|
-|TimeGenerated|datetime|Timestamp when the event was generated by the Azure service processing the request corresponding the event|
-|Type|string|The name of the table|
-|_ResourceId|string|A unique identifier for the resource that the record is associated with|
-|_SubscriptionId|string|A unique identifier for the subscription that the record is associated with|
-
-### ContainerEvent_CL
-
-|Column|Type|Description|
-|-|-|-|
-|Computer|string|Empty|
-|ContainerGroupInstanceId_g|string|A unique identifier for the container group associated with the record|
-|ContainerGroup_s|string|The name of the container group associated with the record|
-|ContainerName_s|string|The name of the container associated with the record|
-|Count_d|real|How many times the event has occurred since the last poll|
-|FirstTimestamp_t|datetime|The timestamp of the first time the event occurred|
-|Location_s|string|The location of the resource associated with the record|
-|Message|string|If applicable, the message from the container|
-|OSType_s|string|The name of the operating system the container is based on|
-|RawData|string|Empty|
-|Reason_s|string|The current status of the container group|
-|ResourceGroup|string|The name of the resource group that the record is associated with|
-|SubscriptionId|string|A unique identifier for the subscription that the record is associated with|
-|TimeGenerated|datetime|Timestamp when the event was generated by the Azure service processing the request corresponding the event|
-|Type|string|The name of the table|
-|_ResourceId|string|A unique identifier for the resource that the record is associated with|
-|_SubscriptionId|string|A unique identifier for the subscription that the record is associated with|
+To learn about the Azure Monitor legacy schema for Log Analytics, see [Legacy Log Analytics tables](monitor-azure-container-instances-reference.md#legacy-log-analytics-tables).
 
 ## Using Diagnostic Settings
 
-Diagnostic Settings for container groups is a preview feature and it can be enabled through preview features options in Azure portal. Once this feature is enabled for a subscription, Diagnostic Settings can be applied to a container group. Applying Diagnostic Settings causes a container group to restart.
-
-For example, here's how we can use New-AzDiagnosticSetting command to apply a Diagnostic Settings object to a container group.
+The newer tables require use of diagnostic settings to route information to Log Analytics. Diagnostic settings for Container Instances is in public preview and it can be enabled through preview features options in the Azure portal.
 
-```azurepowershell
-$log = @()
-$log += New-AzDiagnosticSettingLogSettingsObject -Enabled $true -Category ContainerInstanceLog -RetentionPolicyDay 7 -RetentionPolicyEnabled $true
- 
-New-AzDiagnosticSetting -Name test-setting -ResourceId <container-group-resource-id> -WorkspaceId <log-analytics-workspace-id> -Log $log
-```
+To learn more, see [Azure Monitor Log Analytics tables](monitor-azure-container-instances-reference.md#azure-monitor-log-analytics-tables).
 
 ## Next steps
 

articles/container-instances/container-instances-monitor.md

@@ -24,13 +24,7 @@ At this time, Azure Monitor metrics are only available for Linux containers.
 
 ## Available metrics
 
-Azure Monitor provides the following [metrics for Azure Container Instances][supported-metrics]. These metrics are available for a container group and individual containers. By default, the metrics are aggregated as averages.
-
-- **CPU Usage** measured in **millicores**. 
-  - One millicore is 1/1000th of a CPU core, so 500 millicores represents usage of 0.5 CPU core.
-- **Memory Usage** in bytes
-- **Network bytes received** per second
-- **Network bytes transmitted** per second 
+Azure Monitor provides metrics for Azure Container Instances. For alist of these metrics, see [Supported metrics for Microsoft.ContainerInstance/containerGroups][supported-metrics]. These metrics are available for a container group and individual containers. By default, the metrics are aggregated as averages.
 
 ## Get metrics - Azure portal
 
@@ -147,4 +141,4 @@ Learn how to create [metric alerts][metric-alert] to get notified when a metric
 [azure-monitoring]: ../azure-monitor/overview.md
 [metric-alert]: ..//azure-monitor/alerts/alerts-metric.md
 [monitor-dimension]: ../azure-monitor/essentials/data-platform-metrics.md#multi-dimensional-metrics
-[supported-metrics]: ../azure-monitor/essentials/metrics-supported.md#microsoftcontainerinstancecontainergroups
+[supported-metrics]: monitor-azure-container-instances-reference#metrics

articles/container-instances/monitor-azure-container-instances-reference.md

@@ -95,7 +95,18 @@ The following *_CL* tables represent the legacy Log Analytics integration. Users
 
 ### Azure Monitor Log Analytics tables
 
-The newer tables require use of a diagnostic setting to route information to Log Analytics. Diagnostic settings for Container Instances in the Azure portal is in public preview. The table names are similar, but without the _CL, and some columns are different. For more information, see [Use diagnostic settings](container-instances-log-analytics.md#using-diagnostic-settings).
+The newer tables require use of a diagnostic setting to route information to Log Analytics. Diagnostic settings for Container Instances in the Azure portal is in public preview. The table names are similar, but without the _CL, and some columns are different.
+
+Once this feature is enabled for a subscription, diagnostic settings can be applied to a container group. Applying diagnostic settings causes a container group to restart.
+
+For example, here's how you can use `New-AzDiagnosticSetting` command to apply a diagnostic settings object to a container group.
+
+```azurepowershell
+$log = @()
+$log += New-AzDiagnosticSettingLogSettingsObject -Enabled $true -Category ContainerInstanceLog -RetentionPolicyDay 7 -RetentionPolicyEnabled $true
+ 
+New-AzDiagnosticSetting -Name test-setting -ResourceId <container-group-resource-id> -WorkspaceId <log-analytics-workspace-id> -Log $log
+```
 
 #### Container Instances
 Microsoft.ContainerInstance/containerGroups

articles/container-instances/monitor-azure-container-instances.md

@@ -41,9 +41,7 @@ Containers generate similar data as other Azure resources, but they require a co
 
 You can use Log Analytics to analyze and query container instance logs, and you can also enable diagnostic settings as a preview feature in the Azure portal. Log Analytics and diagnostic settings have slightly different table schemas to use for queries. Once you enable diagnostic settings, you can use either or both schemas at the same time.
 
-For detailed information and instructions for querying logs, see [Container group and instance logging with Azure Monitor logs](container-instances-log-analytics.md). For more information about diagnostic settings, see [Use diagnostic settings](container-instances-log-analytics.md#using-diagnostic-settings).
-
-For the Azure Monitor logs table schemas for Container Instances, see [Container Instances monitoring data reference](monitor-azure-container-instances-reference.md#azure-monitor-logs-tables).
+For detailed information and instructions for querying logs, see [Container group and instance logging with Azure Monitor logs](container-instances-log-analytics.md). For the Azure Monitor logs table schemas for Container Instances, see [Azure Monitor Logs tables](monitor-azure-container-instances-reference.md#azure-monitor-logs-tables).
 
 [!INCLUDE [horz-monitor-kusto-queries](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-kusto-queries.md)]