Merge branch 'MicrosoftDocs:main' into main

AarDavMax · web-flow · commit f079d09cb696 · 2024-08-12T22:01:46.000-05:00
diff --git a/articles/automation/automation-tutorial-installed-software.md b/articles/automation/automation-tutorial-installed-software.md
@@ -7,6 +7,7 @@ ms.date: 04/11/2018
 ms.topic: tutorial
 ms.subservice: change-inventory-management
 ms.custom: mvc
+ms.service: azure-automation
 ---
 # Discover what software is installed on your VMs
 
diff --git a/articles/automation/change-tracking/configure-alerts.md b/articles/automation/change-tracking/configure-alerts.md
@@ -5,6 +5,7 @@ services: automation
 ms.subservice: change-inventory-management
 ms.date: 07/22/2024
 ms.topic: conceptual
+ms.service: azure-automation
 ---
 
 # How to create alerts for Change Tracking and Inventory
diff --git a/articles/automation/change-tracking/enable-from-automation-account.md b/articles/automation/change-tracking/enable-from-automation-account.md
@@ -5,6 +5,7 @@ services: automation
 ms.subservice: change-inventory-management
 ms.date: 07/22/2024
 ms.topic: conceptual
+ms.service: azure-automation
 ---
 
 # Enable Change Tracking and Inventory from an Automation account
diff --git a/articles/automation/change-tracking/enable-from-portal.md b/articles/automation/change-tracking/enable-from-portal.md
@@ -5,6 +5,7 @@ services: automation
 ms.subservice: change-inventory-management
 ms.date: 07/22/2024
 ms.topic: conceptual
+ms.service: azure-automation
 ---
 
 # Enable Change Tracking and Inventory from Azure portal
diff --git a/articles/automation/change-tracking/enable-from-runbook.md b/articles/automation/change-tracking/enable-from-runbook.md
@@ -5,6 +5,7 @@ services: automation
 ms.subservice: change-inventory-management
 ms.topic: conceptual
 ms.date: 07/22/2024
+ms.service: azure-automation
 ---
 
 # Enable Change Tracking and Inventory from a runbook
diff --git a/articles/automation/change-tracking/enable-from-vm.md b/articles/automation/change-tracking/enable-from-vm.md
@@ -5,6 +5,7 @@ services: automation
 ms.subservice: change-inventory-management
 ms.date: 07/22/2024
 ms.topic: conceptual
+ms.service: azure-automation
 ---
 
 # Enable Change Tracking and Inventory from an Azure VM
diff --git a/articles/automation/change-tracking/enable-vms-monitoring-agent.md b/articles/automation/change-tracking/enable-vms-monitoring-agent.md
@@ -5,6 +5,7 @@ services: automation
 ms.subservice: change-inventory-management
 ms.date: 06/03/2024
 ms.topic: conceptual
+ms.service: azure-automation
 ---
 
 # Enable Change Tracking and Inventory using Azure Monitoring Agent
diff --git a/articles/automation/change-tracking/extension-version-details.md b/articles/automation/change-tracking/extension-version-details.md
@@ -5,6 +5,7 @@ services: automation
 ms.subservice: change-inventory-management
 ms.date: 05/22/2024
 ms.topic: conceptual
+ms.service: azure-automation
 ---
 
 # Change tracking and inventory extension version details and known issues
diff --git a/articles/automation/change-tracking/guidance-migration-log-analytics-monitoring-agent.md b/articles/automation/change-tracking/guidance-migration-log-analytics-monitoring-agent.md
@@ -8,6 +8,7 @@ ms.topic: conceptual
 ms.date: 05/01/2024
 ms.author: sudhirsneha
 ms.custom:
+ms.service: azure-automation
 ---
 
 # Migration guidance from Change Tracking and inventory using Log Analytics to Change Tracking and inventory using Azure Monitoring Agent version
diff --git a/articles/automation/change-tracking/manage-change-tracking-monitoring-agent.md b/articles/automation/change-tracking/manage-change-tracking-monitoring-agent.md
@@ -6,6 +6,7 @@ ms.subservice: change-inventory-management
 ms.custom: linux-related-content
 ms.date: 07/17/2023
 ms.topic: conceptual
+ms.service: azure-automation
 ---
 
 # Manage change tracking and inventory using Azure Monitoring Agent
diff --git a/articles/automation/change-tracking/manage-change-tracking.md b/articles/automation/change-tracking/manage-change-tracking.md
@@ -5,6 +5,7 @@ services: automation
 ms.subservice: change-inventory-management
 ms.date: 07/22/2024
 ms.topic: conceptual
+ms.service: azure-automation
 ---
 
 # Manage Change Tracking and Inventory
diff --git a/articles/automation/change-tracking/manage-inventory-vms.md b/articles/automation/change-tracking/manage-inventory-vms.md
@@ -6,6 +6,7 @@ ms.subservice: change-inventory-management
 keywords: inventory, automation, change, tracking
 ms.date: 07/22/2024
 ms.topic: conceptual
+ms.service: azure-automation
 ---
 # Manage inventory collection from VMs
 
diff --git a/articles/automation/change-tracking/manage-scope-configurations.md b/articles/automation/change-tracking/manage-scope-configurations.md
@@ -5,6 +5,7 @@ services: automation
 ms.subservice: change-inventory-management
 ms.date: 07/22/2024
 ms.topic: conceptual
+ms.service: azure-automation
 ---
 
 # Limit Change Tracking and Inventory deployment scope
diff --git a/articles/automation/change-tracking/overview-monitoring-agent.md b/articles/automation/change-tracking/overview-monitoring-agent.md
@@ -5,6 +5,7 @@ services: automation
 ms.subservice: change-inventory-management
 ms.date: 12/14/2023
 ms.topic: conceptual
+ms.service: azure-automation
 ---
 
 # Overview of change tracking and inventory using Azure Monitoring Agent
diff --git a/articles/automation/change-tracking/overview.md b/articles/automation/change-tracking/overview.md
@@ -6,6 +6,7 @@ ms.subservice: change-inventory-management
 ms.date: 08/02/2024
 ms.custom: linux-related-content
 ms.topic: conceptual
+ms.service: azure-automation
 ---
 
 # Change Tracking and Inventory overview
diff --git a/articles/automation/change-tracking/remove-feature.md b/articles/automation/change-tracking/remove-feature.md
@@ -5,6 +5,7 @@ services: automation
 ms.subservice: change-inventory-management
 ms.date: 07/22/2024
 ms.topic: conceptual
+ms.service: azure-automation
 ---
 
 # Remove Change Tracking and Inventory from Automation account
diff --git a/articles/automation/change-tracking/remove-vms-from-change-tracking.md b/articles/automation/change-tracking/remove-vms-from-change-tracking.md
@@ -5,6 +5,7 @@ services: automation
 ms.subservice: change-inventory-management
 ms.topic: conceptual
 ms.date: 07/22/2024
+ms.service: azure-automation
 ---
 
 # Remove machines from Change Tracking and Inventory
diff --git a/articles/automation/index.yml b/articles/automation/index.yml
@@ -5,7 +5,7 @@ metadata:
   title: Azure Automation documentation
   description: Learn how to use Automation to configure and automate operational tasks across a hybrid environment.
   author: SnehaSudhirG
-  ms.service: automation
+  ms.service: azure-automation
   ms.topic: landing-page
   ms.date: 08/30/2022
   ms.author: sudhirsneha
diff --git a/articles/automation/security-controls-policy.md b/articles/automation/security-controls-policy.md
@@ -3,7 +3,7 @@ title: Azure Policy Regulatory Compliance controls for Azure Automation
 description: Lists Azure Policy Regulatory Compliance controls available for Azure Automation. These built-in policy definitions provide common approaches to managing the compliance of your Azure resources.
 ms.date: 05/15/2024
 ms.topic: sample
-ms.service: automation
+ms.service: azure-automation
 ms.custom: subject-policy-compliancecontrols
 ---
 
diff --git a/articles/automation/troubleshoot/change-tracking.md b/articles/automation/troubleshoot/change-tracking.md
@@ -6,6 +6,7 @@ ms.subservice: change-inventory-management
 ms.custom: linux-related-content
 ms.date: 02/15/2021
 ms.topic: troubleshooting
+ms.service: azure-automation
 ---
 
 # Troubleshoot Change Tracking and Inventory issues
diff --git a/articles/azure-monitor/containers/container-insights-data-collection-configure.md b/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. |
+| `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.  |
 
@@ -237,6 +237,7 @@ When you specify the tables to collect using CLI or ARM, you specify a stream na
 | Microsoft-ContainerInventory | ContainerInventory |
 | Microsoft-ContainerLog | ContainerLog |
 | Microsoft-ContainerLogV2 | ContainerLogV2 |
+| Microsoft-ContainerLogV2-HighScale | ContainerLogV2 (High scale mode)<sup>1</sup> |
 | Microsoft-ContainerNodeInventory | ContainerNodeInventory |
 | Microsoft-InsightsMetrics | InsightsMetrics |
 | Microsoft-KubeEvents | KubeEvents |
@@ -247,6 +248,9 @@ When you specify the tables to collect using CLI or ARM, you specify a stream na
 | Microsoft-KubeServices | KubeServices |
 | Microsoft-Perf | Perf |
 
+<sup>1</sup> You shouldn't use both Microsoft-ContainerLogV2 and Microsoft-ContainerLogV2-HighScale in the same DCR. This will result in duplicate data.
+
+
 ## Share DCR with multiple clusters
 When you enable Container insights on a Kubernetes cluster, a new DCR is created for that cluster, and the DCR for each cluster can be modified independently. If you have multiple clusters with custom monitoring configurations, you may want to share a single DCR with multiple clusters. You can then make changes to a single DCR that are automatically implemented for any clusters associated with it.
 
diff --git a/articles/azure-monitor/containers/container-insights-high-scale.md b/articles/azure-monitor/containers/container-insights-high-scale.md
@@ -0,0 +1,128 @@
+---
+title: High scale logs collection in Container Insights (Preview) 
+description: Enable high scale logs collection in Container Insights (Preview).
+ms.topic: conceptual
+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 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.   
+
+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?
+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**
+
+```kusto
+ContainerLogV2 
+| where _ResourceId = "<cluster-resource-id>" 
+| summarize count() by bin(TimeGenerated, 1s), Computer 
+| render timechart 
+```
+
+**Log size (in MB) per second per node**
+
+```kusto
+ ContainerLogV2 
+| where _ResourceId = "<cluster-resource-id>"
+| 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).
+- 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 in the following table are needed for enabling high scale mode depending on your cloud. 
+
+| 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 |
+
+The endpoint is the **Logs Ingestion** endpoint from the data collection endpoint (DCE) for the data collection rule (DCR) used by the cluster. This DCE is created when you enable high scale mode for the cluster and will start with the prefix `MSCI-ingest`.
+
+:::image type="content" source="media/container-insights-high-scale/logs-ingestion-endpoint.png" alt-text="Screenshot of logs ingestion endpoint for DCE." lightbox="media/container-insights-high-scale/logs-ingestion-endpoint.png" :::
+
+
+## Limitations 
+
+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
+- HTTP proxy with trusted certificate
+- Onboarding through Azure portal, Azure Policy, Terraform and Bicep 
+- Configuring through **Monitor Settings** in the AKS Insights portal experience  
+- Automatic migration from existing Container Insights   
+
+## Enable high scale logs collection
+Follow the two steps in the following sections to enable high scale mode for your cluster.
+
+> [!NOTE]
+> High log scale mode requires a [data collection endpoint (DCE)](../essentials/data-collection-endpoint-overview.md) for ingestion. An ingestion DCE is created with the prefix `MSCI-ingest` for each cluster when you onboard them. If Azure Monitor private link scope is configured, then there will also be configuration DCE created with the prefix `MSCI-config`. 
+
+### 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 enable `agent_settings.high_log_scale` under `agent-settings` as in the following: 
+
+```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 mode. 
+
+### Enable high scale mode for Monitoring add-on
+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` 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**
+
+```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 additional parameters `--enable-high-scale-mode` and `--ampls-resource-id` to configure high log scale mode with Azure Monitor Private Link Scope Resource ID. 
+
+## Migration
+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 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 for 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
+- Share any feedback or issues with High Scale mode at [https://aka.ms/cihsfeedback](https://aka.ms/cihsfeedback).
+
diff --git a/articles/azure-monitor/containers/media/container-insights-high-scale/logs-ingestion-endpoint.png b/articles/azure-monitor/containers/media/container-insights-high-scale/logs-ingestion-endpoint.png
diff --git a/articles/azure-monitor/toc.yml b/articles/azure-monitor/toc.yml
@@ -452,6 +452,8 @@ items:
         href: containers/container-insights-data-collection-filter.md
       - name: Container log schema
         href: containers/container-insights-logs-schema.md
+      - name: High scale
+        href: containers/container-insights-high-scale.md      
       - name: Data transformations
         displayName: Container insights
         href: containers/container-insights-transformations.md
diff --git a/articles/event-grid/ensure-tags-exists-on-new-virtual-machines.md b/articles/event-grid/ensure-tags-exists-on-new-virtual-machines.md
@@ -4,7 +4,7 @@ description: Learn how to automatically add a tag when a new VM is created and s
 keywords: automation, runbook, teams, event grid, virtual machine, VM
 author: eamonoreilly
 
-ms.service: automation
+ms.service: azure-automation
 ms.topic: tutorial
 ms.date: 07/07/2020
 ms.author: eamono
diff --git a/articles/search/search-limits-quotas-capacity.md b/articles/search/search-limits-quotas-capacity.md
@@ -40,7 +40,7 @@ Maximum limits on storage, workloads, and quantities of indexes and other object
 |----------|------|--------|----|----|----|------------|----|----|
 | Maximum indexes |3 |5 or 15 |50 |200 |200 |1000 per partition or 3000 per service |10 |10 |
 | Maximum simple fields per index&nbsp;<sup>2</sup> |1000 |100 |1000 |1000 |1000 |1000 |1000 |1000 |
-| Maximum dimensions per vector field | 3072 |3072 |3072 |3072 |3072 |3072 |3072 |3072 |
+| Maximum dimensions per vector field | 4098|4098|4098|4098|4098|4098|4098|4098|
 | Maximum complex collections per index |40 |40 |40 |40 |40 |40 |40 |40 |
 | Maximum elements across all complex collections per document&nbsp;<sup>3</sup> |3000 |3000 |3000 |3000 |3000 |3000 |3000 |3000 |
 | Maximum depth of complex fields |10 |10 |10 |10 |10 |10 |10 |10 |
diff --git a/docfx.json b/docfx.json
@@ -1218,7 +1218,7 @@
         "articles/app-service/**/*.md": "app-service",
         "articles/app-service-mobile/**/*.md": "app-service-mobile",
         "articles/app-spaces/**/*.md": "app-spaces",
-        "articles/automation/**/*.md": "automation",
+        "articles/automation/**/*.md": "azure-automation",
         "articles/azure-arc/**/*.md": "azure-arc",
         "articles/azure-functions/**/*.md": "azure-functions",
         "articles/azure-fluid-relay/**/*.md": "azure-fluid",
diff --git a/includes/azure-automation-service-limits.md b/includes/azure-automation-service-limits.md
@@ -3,7 +3,7 @@ title: "include file"
 description: "include file"
 services: automation
 author: mgoedtel
-ms.service: automation
+ms.service: azure-automation
 ms.topic: "include"
 ms.date: 02/23/2024
 ms.author: magoedte
