updates

Author: bwren

articles/azure-monitor/containers/container-insights-high-scale.md

@@ -6,7 +6,7 @@ ms.date: 08/06/2024
 ---
 
 # High scale logs collection in Container Insights (Preview) 
-High scale mode is a feature in Container Insights that enables you to collect container console (stdout & stderr) logs with high throughput from your Azure Kubernetes Service (AKS) cluster nodes. This feature is intended for AKS clusters sending more than 5,000 logs/sec per node.
+High scale mode is a feature in Container Insights that enables you to collect container console (stdout & stderr) logs with high throughput from your Azure Kubernetes Service (AKS) cluster nodes. This feature enables you to collect up to 50,000 logs/sec per node.
 
 ## Overview
 When high scale mode is enabled, Container Insights performs multiple configuration changes resulting in a higher overall throughput. This includes using an upgraded agent and Azure Monitor data pipeline with scale improvements. These changes are all made in the background by Azure Monitor and don't require input or configuration after the feature is enabled.   
@@ -16,7 +16,7 @@ High scale mode impacts only the data collection layer. The rest of the Containe
 To achieve the maximum supported logs throughput, you should use high-end VM SKUs with 16 CPU cores or more for your AKS cluster nodes. Using low end VM SKUs will impact your logs throughput.  
 
 ## Does my cluster qualify?
-High scale logs collection is suited for environments sending more than 5,000 logs/sec per node in their Kubernetes clusters and has been designed and tested for sending up to 50,000 logs/sec per node. Use the following [log queries](../logs/log-query-overview.md) to determine whether your cluster is suitable for high scale logs collection.
+High scale logs collection is suited for environments sending more than 2,000 logs/sec (or 2 MB/sec) per node in their Kubernetes clusters and has been designed and tested for sending up to 50,000 logs/sec per node. Use the following [log queries](../logs/log-query-overview.md) to determine whether your cluster is suitable for high scale logs collection.
 
 
 **Logs per second and per node**
@@ -42,6 +42,7 @@ ContainerLogV2
 - Azure CLI version 2.63.0 or higher.
 - AKS-preview CLI extension version must be 7.0.0b4 or higher if an aks-preview CLI extension is installed.
 - Cluster schema must be [configured for ContainerLogV2](./container-insights-logs-schema.md#enable-the-containerlogv2-schema).
+- If the default resource limits (CPU and memory) on ama-logs daemon set container doesn't meet your log scale requirements, please contact the Microsoft support channel to increase the resource limits of your ama-logs container.
 
 ## Network firewall requirements
 In addition to the [network firewall requirements](./kubernetes-monitoring-firewall.md) for monitoring a Kubernetes cluster, additional configurations are needed for enabling High scale Mode. 
@@ -74,7 +75,7 @@ The following two steps are required to enable high scale mode for your cluster.
 ### Update configmap
 The first step is to update configmap for the cluster to instruct the container insights ama-logs deamonset pods to run in high scale mode. 
 
-Follow the guidance in [Configure and deploy ConfigMap](./container-insights-data-collection-configmap.md#configure-and-deploy-configmap) to download and update ConfigMap for the cluster. The only change you need to make for high scale logs is to add the following entry under `agent-settings`: 
+Follow the guidance in [Configure and deploy ConfigMap](./container-insights-data-collection-configmap.md#configure-and-deploy-configmap) to download and update ConfigMap for the cluster. The only change you need to make for high scale logs is to enable `agent_settings.high_log_scale` under `agent-settings` as in the following: 
 
 ```yml
 [agent_settings.high_log_scale] 
@@ -84,12 +85,10 @@ Follow the guidance in [Configure and deploy ConfigMap](./container-insights-dat
 After applying this configmap, `ama-logs-*` pods will get restarted automatically and configure the ama-logs daemonset pods to run in high scale mode. 
 
 ### Enable high scale mode for Monitoring add-on
-Once the ama-logs pods are running in high log scale mode, you can enable the Monitoring Add-on with high scale mode. Use the following Azure CLI commands to enable high scale logs mode for the Monitoring add-on depending on your AKS configuration.
+Enable the Monitoring Add-on with high scale mode using the following Azure CLI commands to enable high scale logs mode for the Monitoring add-on depending on your AKS configuration.
 
 > [!NOTE]
-> Instead of CLI, you can use an ARM template to enable high scale mode for the Monitoring add-on. See [Enable Container insights](./kubernetes-monitoring-enable.md?tabs=arm#enable-container-insights) for guidance on enabling Container Insights using an ARM template. To enable high scale mode, use `Microsoft-ContainerLogV2-HighScale` in the `streams` parameter.
->
-> Don't use both `Microsoft-ContainerLogV2` and `Microsoft-ContainerLogV2-HighScale` in the `streams` parameter. This will result in logs being collected in the standard mode.
+> Instead of CLI, you can use an ARM template to enable high scale mode for the Monitoring add-on. See [Enable Container insights](./kubernetes-monitoring-enable.md?tabs=arm#enable-container-insights) for guidance on enabling Container Insights using an ARM template. To enable high scale mode, use `Microsoft-ContainerLogV2-HighScale` instead of `Microsoft-ContainerLogV2` in the `streams` parameter as described in [Configure DCR with ARM templates](./container-insights-data-collection-configure.md?tabs=arm#configure-dcr-with-arm-templates).
 
 
 **Existing AKS cluster**
@@ -118,7 +117,7 @@ See [Create a private Azure Kubernetes Service (AKS) cluster](/azure/aks/private
 If Container insights is already enabled for your cluster, then you need to disable it and then re-enable it with high scale mode.
 
 - Since high scale mode uses a different data pipeline, you must ensure that pipeline endpoints are not blocked by a firewall or other network connections.
-- High scale mode uses a different DCR for data collection. If you've created any DCRs that use *Microsoft.ContainerLogV2*, you must replace this with *Microsoft.ContainerLogV2-HighScale* or data will be duplicated. 
+- High scale mode requires a data collection endpoint (DCE) for ingestion in addition to the standard DCR for data collection. If you've created any DCRs that use `Microsoft.ContainerLogV2`, you must replace this with `Microsoft.ContainerLogV2-HighScale` or data will be duplicated. You should also create a DCE ingestion and link it to the DCR if the DCR isn't already using one. Refer to Container Insights onboarding through Azure Resource Manager for reference for the dependencies. 
 
 
 ## Next steps