Merge pull request #270580 from bwren/cost

Links to cost optimization articles

Author: prmerger-automator[bot]

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

@@ -11,7 +11,7 @@ ms.reviewer: aul
 This article describes how to configure data collection in Container insights using ConfigMap. [ConfigMaps](https://kubernetes.io/docs/tasks/configure-pod-container/configure-pod-configmap/) are a Kubernetes mechanism that allow you to store non-confidential data such as configuration file or environment variables. 
 
 The ConfigMap is primarily used to configure data collection of the container logs and environment variables of the cluster. You can individually configure the stdout and stderr logs and also enable multiline logging.
-
+l
 Specific configuration you can perform with the ConfigMap includes:
 
 - Enable/disable and namespace filtering for stdout and stderr logs

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

@@ -1,15 +1,15 @@
 ---
-title: Configure Container insights data collection using data collection rule
+title: Configure data collection and cost optimization in Container insights using data collection rule
 description: Describes how you can configure cost optimization and other data collection for Container insights using a data collection rule.
 ms.topic: conceptual
 ms.custom: devx-track-azurecli
 ms.date: 12/19/2023
 ms.reviewer: aul
 ---
 
-# Configure data collection in Container insights using data collection rule
+# Configure data collection and cost optimization in Container insights using data collection rule
 
-This article describes how to configure data collection in Container insights using the [data collection rule (DCR)](../essentials/data-collection-rule-overview.md) for the cluster. A DCR is created when you onboard a cluster to Container insights. This DCR is used by the containerized agent to define data collection for the cluster.
+This article describes how to configure data collection in Container insights using the [data collection rule (DCR)](../essentials/data-collection-rule-overview.md) for your Kubernetes cluster. This includes preset configurations for optimizing your costs. A DCR is created when you onboard a cluster to Container insights. This DCR is used by the containerized agent to define data collection for the cluster.
 
 The DCR is primarily used to configure data collection of performance and inventory data and to configure cost optimization.
 

articles/azure-monitor/containers/kubernetes-monitoring-enable.md

@@ -18,7 +18,11 @@ This article describes how to enable complete monitoring of your Kubernetes clus
 [Using the Azure portal](#enable-full-monitoring-with-azure-portal), you can enable all of the features at the same time. You can also enable them individually by using the Azure CLI, Azure Resource Manager template, Terraform, or Azure Policy. Each of these methods is described in this article.
 
 > [!IMPORTANT]
-> This article describes onboarding using default configuration settings including managed identity authentication. See [Configure agent data collection for Container insights](container-insights-data-collection-configmap.md) and [Customize scraping of Prometheus metrics in Azure Monitor managed service for Prometheus](prometheus-metrics-scrape-configuration.md) to customize your configuration to ensure that you aren't collecting more data than you require. See [Authentication for Container Insights](container-insights-authentication.md) for guidance on migrating from legacy authentication models.
+> Kubernetes clusters generate a lot of log data, which can result in significant costs if you aren't selective about the logs that you collect. Before you enable monitoring for your cluster, see the following articles to ensure that your environment is optimized for cost and that you limit your log collection to only the data that you require:
+> 
+>- [Configure data collection and cost optimization in Container insights using data collection rule](./container-insights-data-collection-dcr.md)<br>Details on customizing log collection once you've enabled monitoring, including using preset cost optimization configurations.
+>- [Best practices for monitoring Kubernetes with Azure Monitor](../best-practices-containers.md)<br>Best practices for monitoring Kubernetes clusters organized by the five pillars of the [Azure Well-Architected Framework](/azure/architecture/framework/), including cost optimization.
+>- [Cost optimization in Azure Monitor](../best-practices-cost.md)<br>Best practices for configuring all features of Azure Monitor to optimize you costs and limit the amount of data that you collect.
 
 ## Supported clusters