DCE

Author: bwren

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

@@ -237,7 +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<br>(High scale mode)<sup>1</sup> |
+| Microsoft-ContainerLogV2-HighScale | ContainerLogV2 (High scale mode)<sup>1</sup> |
 | Microsoft-ContainerNodeInventory | ContainerNodeInventory |
 | Microsoft-InsightsMetrics | InsightsMetrics |
 | Microsoft-KubeEvents | KubeEvents |

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

@@ -47,7 +47,9 @@ ContainerLogV2
 ## 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>`.  
+Get 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" :::
 
 The endpoint has a different format depending on the cloud as shown in the following table.
 
@@ -70,7 +72,9 @@ The following scenarios aren't supported during the preview release. These will
 - Automatic migration from existing Container Insights   
 
 ## Enable high scale logs collection
-The following two steps are required to enable high scale mode for your cluster.
+Follow the two steps in the following sections to enable high scale mode for your cluster.
+
+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.