Merge pull request #275425 from cdpark/horz-monitor-container

User Story 246543: Q&M: Curate 27 SOX Azure Monitor horizontals articles to reduce duplication - Container Instances

Author: v-dirichards

.openpublishing.redirection.json

@@ -1135,6 +1135,11 @@
             "redirect_url": "/azure/container-instances/container-instances-multi-container-group",
             "redirect_document_id": false
         },
+        {
+            "source_path_from_root": "/articles/container-instances/container-instances-monitor.md",
+            "redirect_url": "/azure/container-instances/monitor-azure-container-instances",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/cassandra-managed-instance/compare-cosmosdb-managed-instance.md",
             "redirect_url": "/azure/managed-instance-apache-cassandra/compare-cosmosdb-managed-instance",

articles/container-instances/TOC.yml

@@ -164,7 +164,7 @@
       href: container-instances-update.md
   - name: Monitor and log
     items:
-    - name: Monitor
+    - name: Monitor Container Instances
       href: monitor-azure-container-instances.md
     - name: Monitor CPU and memory usage
       href: container-instances-monitor.md

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
 
@@ -222,7 +172,7 @@ For more information about querying logs and configuring alerts in Azure Monitor
 
 For information about monitoring container instance CPU and memory resources, see:
 
-* [Monitor container resources in Azure Container Instances](container-instances-monitor.md).
+* [Monitor Azure Container Instances](monitor-azure-container-instances.md).
 
 <!-- IMAGES -->
 [log-search-01]: ./media/container-instances-log-analytics/portal-query-01.png

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

@@ -59,7 +59,7 @@ Some features are currently restricted to Linux containers:
 
 * Multiple containers per container group
 * Volume mounting ([Azure Files](container-instances-volume-azure-files.md), [emptyDir](container-instances-volume-emptydir.md), [GitRepo](container-instances-volume-gitrepo.md), [secret](container-instances-volume-secret.md))
-* [Resource usage metrics](container-instances-monitor.md) with Azure Monitor
+* [Resource usage metrics](monitor-azure-container-instances.md#get-metrics) with Azure Monitor
 * [GPU resources](container-instances-gpu.md) (preview)
 
 For Windows container deployments, use images based on common [Windows base images](./container-instances-faq.yml#what-windows-base-os-images-are-supported-).

articles/container-instances/container-instances-overview.md

@@ -98,7 +98,7 @@ This error indicates that due to heavy load in the region in which you are attem
 ## Issues during container group runtime
 ### Container had an isolated restart without explicit user input
 
-There are two broad categories for why a container group may restart without explicit user input. First, containers may experience restarts caused by an application process crash. The ACI service recommends applying observability solutions such as [Application Insights SDK](../azure-monitor/app/app-insights-overview.md), [container group metrics](container-instances-monitor.md), and [container group logs](container-instances-get-logs.md) to determine why the application experienced issues. Second, customers may experience restarts initiated by the ACI infrastructure due to maintenance events. To increase the availability of your application, run multiple container groups behind an ingress component such as an [Application Gateway](../application-gateway/overview.md) or [Traffic Manager](../traffic-manager/traffic-manager-overview.md).
+There are two broad categories for why a container group may restart without explicit user input. First, containers may experience restarts caused by an application process crash. The ACI service recommends applying observability solutions such as [Application Insights SDK](../azure-monitor/app/app-insights-overview.md), [container group metrics](monitor-azure-container-instances.md#get-metrics), and [container group logs](container-instances-get-logs.md) to determine why the application experienced issues. Second, customers may experience restarts initiated by the ACI infrastructure due to maintenance events. To increase the availability of your application, run multiple container groups behind an ingress component such as an [Application Gateway](../application-gateway/overview.md) or [Traffic Manager](../traffic-manager/traffic-manager-overview.md).
 
 ### Container continually exits and restarts (no long-running process)