Container insights high scale mode

Author: bwren

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

@@ -0,0 +1,107 @@
+##---
+title: High scale logs collection in Container Insights (Preview) 
+description: Enable high scale logs collection in Container Insights (Preview).
+ms.custom: devx-track-azurecli
+ms.date: 08/06/2024
+---
+
+# High scale logs collection in Container Insights (Preview) 
+High scale logs mode is a feature in Container Insights enables you to collect container console (stdout & stderr) logs with high throughput from their AKS cluster nodes. This feature is intended for Azure Kubernetes Service 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 and upgraded agent and Azure Monitor pipeline with scale improvements. These changes are all made by Azure Monitor and don't require input or configuration after the feature has been enabled.   
+
+High scale logs collection is suited for environments sending more than 5,000 logs/sec from a single node in their Kubernetes clusters and has been designed and tested for sending up to 50K log/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. 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. 
+
+**Logs per second and per node**
+
+``kql
+ContainerLogV2 
+| where _ResourceId = “<AzureResourceIdoftheAKSCluster>” 
+| summarize count() by bin(TimeGenerated, 1s), Computer 
+| render timechart 
+```
+
+**Log size (in MB) per second per node**
+
+```kusto
+ ContainerLogV2 
+| where _ResourceId = “<AzureResourceIdoftheAKSCluster>” 
+| summarize BillableDataMB = sum(_BilledSize)/1024/1024 by bin(TimeGenerated, 1s), Computer 
+| render timechart 
+```
+
+## Prerequisites 
+
+- 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 firewall requirements for monitoring Kubernetes cluster](./kubernetes-monitoring-firewall.md).
+
+## Limitations 
+
+The following scenarios are not supported during the Preview release. These will be addressed when the feature becomes generally available.
+
+- AKS Clusters with ARM64 nodes 
+- Azure Arc-enabled Kubernetes
+- HTTP proxy with trusted certificate
+- Onboarding through Azure Portal, Azure Policy, Terraform and Bicep 
+- Configuring through **Monitor Settings** from AKS Insights  
+- Automatic migration from existing Container Insights   
+
+## Enabling high scale logs collection
+Use the following steps to enable high scale logs collection 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. 
+
+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 different you need to make for high scale logs is to add the following entry under `agent-settings`: 
+
+    ```yml
+    [agent_settings.high_log_scale] 
+      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. 
+
+### 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.
+
+### [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
+
+```azurecli
+az aks enable-addons -a monitoring -g <resource-group-name> -n <cluster-name> --enable-high-log-scale-mode  
+```
+
+#### 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
+
+```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 following additional parameters to configure high log scale mode with Azure Monitor Private Link Scope Resource ID. 
+
+- `--enable-high-scale-mode`
+- `--ampls-resource-id`
+
+### [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.
+
+## Next steps
+
+