final updates

Author: bwren

articles/azure-monitor/containers/container-insights-data-collection-configure.md

@@ -195,7 +195,7 @@ The following table describes the parameters you need to provide values for in e
 | `dataCollectionInterval` | Determines how often the agent collects data.  Valid values are 1m - 30m in 1m intervals The default value is 1m. If the value is outside the allowed range, then it defaults to *1 m*. |
 | `namespaceFilteringModeForDataCollection` | *Include*: Collects only data from the values in the *namespaces* field.<br>*Exclude*: Collects data from all namespaces except for the values in the *namespaces* field.<br>*Off*: Ignores any *namespace* selections and collect data on all namespaces.
 | `namespacesForDataCollection` | Array of comma separated Kubernetes namespaces to collect inventory and perf data based on the _namespaceFilteringMode_.<br>For example, *namespaces = ["kube-system", "default"]* with an _Include_ setting collects only these two namespaces. With an _Exclude_ setting, the agent collects data from all other namespaces except for _kube-system_ and _default_. With an _Off_ setting, the agent collects data from all namespaces including _kube-system_ and _default_. Invalid and unrecognized namespaces are ignored. |
-| `streams` | An array of container insights table streams. See [Stream values in DCR](#stream-values-in-dcr) for a list of the valid streams and their corresponding tables. To enable [high scale mode](./container-insights-high-scale.md) for container logs, use `Microsoft-ContainerLogV2-HighScale`.  |
+| `streams` | An array of container insights table streams. See [Stream values in DCR](#stream-values-in-dcr) for a list of the valid streams and their corresponding tables.<br><br>To enable [high scale mode](./container-insights-high-scale.md) for container logs, use `Microsoft-ContainerLogV2-HighScale`.  |
 | `useAzureMonitorPrivateLinkScope` | Specifies whether to use private link for the cluster connection to Azure Monitor. |
 | `azureMonitorPrivateLinkScopeResourceId` | If private link is used, resource ID of the private link scope.  |
 

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

@@ -6,23 +6,24 @@ 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 AKS cluster nodes. This feature is intended for Azure Kubernetes Service 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 is intended for AKS clusters sending more than 5,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.   
 
-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.  High scale mode impacts only the data collection layer. The rest of the Container insights experience remains the same, with logs being ingested into same `ContainerLogV2` table. Existing queries and alerts continue to work since the same data is being collected.
+High scale mode impacts only the data collection layer. The rest of the Container insights experience remains the same, with logs being ingested into same `ContainerLogV2` table. Existing queries and alerts continue to work since the same data is being collected.
 
 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?
-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 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.
+
 
 **Logs per second and per node**
 
-```kql
+```kusto
 ContainerLogV2 
-| where _ResourceId = "<AzureResourceIdoftheAKSCluster>" 
+| where _ResourceId = "<cluster-resource-id>" 
 | summarize count() by bin(TimeGenerated, 1s), Computer 
 | render timechart 
 ```
@@ -31,7 +32,7 @@ ContainerLogV2
 
 ```kusto
  ContainerLogV2 
-| where _ResourceId = "<AzureResourceIdoftheAKSCluster>"
+| where _ResourceId = "<cluster-resource-id>"
 | summarize BillableDataMB = sum(_BilledSize)/1024/1024 by bin(TimeGenerated, 1s), Computer 
 | render timechart 
 ```
@@ -41,11 +42,24 @@ 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).
-- See [Network and firewall requirements](#network-and-firewall-requirements).
+
+## 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. 
+
+Get the **Logs Ingestion** endpoint from the data collection endpoint (DCE) for the data collection rule (DCR) used by the cluster. The DCR name is in the form `MSCI-<region>-<clusterName>`.  
+
+The endpoint has a different format depending on the cloud as shown in the following table.
+
+| Cloud | Endpoint | Port |
+|:---|:--|:--|
+| Azure Public Cloud | `<dce-name>-<suffix>.<cluster-region-name>-<suffix>.ingest.monitor.azure.com` | 443 |
+| Microsoft Azure operated by 21Vianet cloud | `<dce-name>-<suffix>.<cluster-region-name>-<suffix>.ingest.monitor.azure.cn` | 443 |
+| Azure Government cloud | `<dce-name>-<suffix>.<cluster-region-name>-<suffix>.ingest.monitor.azure.us` | 443 |
+
 
 ## Limitations 
 
-The following scenarios aren't supported during the Preview release. These will be addressed when the feature becomes generally available.
+The following scenarios aren't supported during the preview release. These will be addressed when the feature becomes generally available.
 
 - AKS Clusters with Arm64 nodes 
 - Azure Arc-enabled Kubernetes
@@ -55,10 +69,10 @@ The following scenarios aren't supported during the Preview release. These will
 - Automatic migration from existing Container Insights   
 
 ## Enable high scale logs collection
-Use the following steps to enable high scale logs collection for your cluster.
+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 log scale mode. 
+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`: 
 
@@ -67,57 +81,42 @@ Follow the guidance in [Configure and deploy ConfigMap](./container-insights-dat
   enabled = true 
 ```
 
-After applying this configmap, `ama-logs-*` pods will get restarted automatically and configure the ama-logs daemonset pods to run in high scale log mode. 
+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.
+
+> [!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.
 
-### Enable high scale log 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 log mode. You have the option to perform this configuration using either Azure CLI or an ARM Template.
+> 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.
 
-### [CLI](#tab/cli)
-Use the following Azure CLI commands to enable high scale logs mode for the Monitoring add-on depending on your AKS configuration.
 
-#### Existing AKS cluster
+**Existing AKS cluster**
 
 ```azurecli
 az aks enable-addons -a monitoring -g <resource-group-name> -n <cluster-name> --enable-high-log-scale-mode  
 ```
 
-#### Existing AKS Private cluster
+**Existing AKS Private cluster**
 
 ```azurecli
 az aks enable-addons -a monitoring -g  <resource-group-name> -n <cluster-name> --enable-high-scale-mode --ampls-resource-id /subscriptions/<subscription-id>/resourceGroups/<resource-group-name>/providers/microsoft.insights/privatelinkscopes/<resourceName> 
 ```
 
-#### New AKS cluster
+**New AKS cluster**
 
 ```azurecli
 az aks create -g <cluster-name> -n <cluster-name> enable-addons -a monitoring --enable-high-log-scale-mode  
 ```
 
-#### New AKS Private cluster
-See [Create a private Azure Kubernetes Service (AKS) cluster](/azure/aks/private-clusters?tabs=azure-portal) for details on creating an AKS Private cluster. Use the additional parameters `--enable-high-scale-mode` and `--ampls-resource-id` to configure high log scale mode with Azure Monitor Private Link Scope Resource ID. 
-
-
+**New AKS Private cluster**
 
-### [ARM](#tab/arm)
-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 logs mode, use `Microsoft-ContainerLogV2-HighScale` in the `streams` parameter.
+See [Create a private Azure Kubernetes Service (AKS) cluster](/azure/aks/private-clusters?tabs=azure-portal) for details on creating an AKS Private cluster. Use the additional parameters `--enable-high-scale-mode` and `--ampls-resource-id` to configure high log scale mode with Azure Monitor Private Link Scope Resource ID. 
 
-> [!WARNING]
-> 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.
 
 ---
 
-## Network and firewall requirements
-In addition to the [network firewall requirements](See [Network firewall requirements for monitoring Kubernetes cluster](./kubernetes-monitoring-firewall.md)) for monitoring a Kubernetes cluster, additional configurations are needed for enabling High scale Mode. 
-
-Get the **Logs Ingestion** endpoint from the data collection endpoint (DCE) for the data collection rule (DCR) used by the cluster. The DCR name is in the form `MSCI-<region>-<clusterName>`.  
-
-The endpoint has a different format depending on the cloud as shown in the following table.
-
-| Cloud | Endpoint | Port |
-|:---|:--|:--|
-| Azure Public Cloud | `<dce-name>-<suffix>.<cluster-region-name>-<suffix>.ingest.monitor.azure.com` | 443 |
-| Microsoft Azure operated by 21Vianet cloud | `<dce-name>-<suffix>.<cluster-region-name>-<suffix>.ingest.monitor.azure.cn` | 443 |
-| Azure Government cloud | `<dce-name>-<suffix>.<cluster-region-name>-<suffix>.ingest.monitor.azure.us` | 443 |
 
 
 ## Next steps