Merge pull request #265251 from austonli/patch-42

V2 docs updates

Author: Stacyrch140

articles/azure-monitor/containers/container-insights-cost.md

@@ -71,7 +71,7 @@ If the majority of your data comes from one of these following tables:
 
 You can adjust your ingestion using the [cost optimization settings](../containers/container-insights-cost-config.md) and/or migrating to the [Prometheus metrics addon](container-insights-prometheus.md)
 
-Otherwise, the majority of your data belongs to the ContainerLog table. and you can follow the steps below to reduce your ContainerLog costs.
+Otherwise, the majority of your data belongs to the ContainerLog table and you can follow the steps below to reduce your ContainerLog costs.
 
 ### Reducing your ContainerLog costs
 
@@ -122,7 +122,7 @@ After you apply one or more of these changes to your ConfigMaps, apply it to you
 
 You can save on data ingestion costs on ContainerLog in your Log Analytics workspace that you primarily use for debugging, troubleshooting, and auditing as Basic Logs. For more information, including the limitations of Basic Logs, see [Configure Basic Logs in Azure Monitor](../logs/basic-logs-configure.md). ContainerLogV2 is the configured version of Basic Logs that Container Insights uses. ContainerLogV2 includes verbose text-based log records.
 
-You must be on the ContainerLogV2 schema to configure Basic Logs. For more information, see [Enable the ContainerLogV2 schema (preview)](container-insights-logs-schema.md).
+You must be on the ContainerLogV2 schema to configure Basic Logs. For more information, see [Enable the ContainerLogV2 schema](container-insights-logs-schema.md).
 
 ### Prometheus metrics scraping
 

articles/azure-monitor/containers/container-insights-experience-v2.md

@@ -0,0 +1,160 @@
+---
+title: Switch to use Container Insights with managed Prometheus | Microsoft Docs
+description: This article describes how you can replace your Container Insights visualizations to use Prometheus metrics.
+ms.topic: conceptual
+ms.date: 05/15/2024
+ms.reviewer: aul
+---
+
+# Switch to using managed Prometheus visualizations for Container Insights (preview)
+
+Container Insights currently uses data from Log Analytics to power the visualizations in the Azure portal. However, with the release of managed Prometheus, this new format of metrics collection is cheaper and more efficient. Container Insights now offers the ability to visualize using only managed Prometheus data. This article helps you with the setup to start using managed Prometheus as your primary Container Insights visualization tool.
+
+> [!Note]
+> This feature is currently in public preview. For additional information, please read the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms).
+
+## Prerequisites
+
+To view your Container Insights data using Prometheus, ensure the following steps are complete.
+
+* Azure Kubernetes Service (AKS) [configured with managed Prometheus](./kubernetes-monitoring-enable.md#existing-cluster-prometheus-only)
+* User has `Reader` permission or higher on the associated [Azure Monitor workspace](../essentials/azure-monitor-workspace-overview.md)
+* Ad block is disabled or set to allow `monitor.azure.com` traffic
+* For Windows clusters, [enable Windows metric collection](./kubernetes-monitoring-enable.md#enable-windows-metrics-collection-preview)
+
+## Accessing Prometheus based Container Insights
+
+Because Azure Monitor supports various levels of customization, your cluster may currently have logs based Container Insights, managed Prometheus, or some other combination.
+
+> [!Note]
+> Managed Prometheus visualizations for Container Insights use recording rules to improve chart performance, learn more about [what rules are configured](./prometheus-metrics-scrape-default.md#prometheus-visualization-recording-rules).
+
+### [No Prometheus or logs based Container Insights enabled](#tab/unmonitored)
+
+1. Open the Azure portal and navigate to your desired AKS cluster.
+
+2. Choose the `Insights` menu item from the menu, displaying a splash screen indicating no monitoring enabled.
+
+![Screenshot of unmonitoring cluster.](media/container-insights-experience-v2/splash-screen-nothing-enabled.png)
+
+3. Select the `Configure monitoring` button to open up the monitoring configuration blade.
+
+4. Underneath the advanced settings blade, choose `Logs and events` from the Cost presets dropdown.
+
+5. To finish the setup, click the `Configure` button.
+
+6. Once the onboarding deployment completes, you should be able to see the Insights experience using Prometheus as the data source, indicated by the toolbar dropdown showing `Managed Prometheus visualizations (Preview)`.
+
+![Screenshot of AKS cluster with Prometheus based Container Insights.](media/container-insights-experience-v2/container-insights-prom-full.png)
+
+### [Logs based Container Insights enabled](#tab/LA)
+
+1. Open the Azure portal and navigate to your desired AKS cluster.
+
+2. Choose the `Insights` menu item from the menu, which displays a banner at the top to configure managed Prometheus.
+
+3. Using the banner, select the `Configure` button to complete onboarding to managed Prometheus or deploy the requisite recording rules.
+
+![Screenshot of AKS cluster with Prometheus banner.](media/container-insights-experience-v2/container-insights-logs-prom-banner.png)
+
+If the banner was previously dismissed, you can instead use the dropdown in the toolbar that says `Log Analytics visualizations (Classic)`, and select the `Managed Prometheus visualizations (Preview)` option, which opens up a pop-up to complete onboarding.
+
+![Screenshot of AKS cluster with toggle dropdown.](media/container-insights-experience-v2/container-insights-logs-dropdown.png)
+
+4. Once the monitoring deployment is complete, the Insights blade should switch to using Prometheus as the data source, indicated by the toolbar dropdown showing `Managed Prometheus visualizations (Preview)`.
+
+![Screenshot of AKS cluster with Prometheus based Container Insights.](media/container-insights-experience-v2/container-insights-prom-full.png)
+
+
+### [Prometheus enabled and logs based Container Insights not enabled or with custom settings applied](#tab/Prom)
+
+1. Open the Azure portal and navigate to your desired AKS cluster.
+
+2. Choose the `Insights` menu item from the menu, which displays a banner for enabling Prometheus recording rules.
+
+![Screenshot of AKS cluster with Prometheus based Container Insights.](media/container-insights-experience-v2/container-insights-splash-screen-prom-only.png)
+
+3. Click `Enable` to deploy the recording rules.
+
+4. Once the monitoring deployment is complete, the Insights blade should switch to using Prometheus as the data source, indicated by the toolbar dropdown showing `Managed Prometheus visualizations (Preview)`.
+
+> [!Note]
+> Some charts will only have partial data for the default time range until sufficient time has elapsed for the recording rules to collect data.
+
+![Screenshot of AKS cluster with Prometheus based Container Insights, with recording rule banner.](media/container-insights-experience-v2/container-insights-prom-recording-rules-loading.png)
+
+---
+
+## Optional steps
+
+While the above steps are sufficient, for the full visualization experience, a few optional steps can be completed.
+
+### Node and Pod labels collection 
+
+By default the labels for nodes and pods aren't available, but can be collected through re-enabling the addon. Node labels are required for filtering data by node pools.
+
+1. If the managed Prometheus addon is currently deployed, we must first disable it
+
+```azurecli
+az aks update --disable-azure-monitor-metrics -n <clusterName> -g <resourceGroup>
+```
+
+2. Then, re-enable the addon with the flag `--ksm-metric-labels-allow-list`
+    
+```azurecli
+az aks update -n <clusterName> -g <resourceGroup> --enable-azure-monitor-metrics --ksm-metric-labels-allow-list "nodes=[*], pods=[*]" --azure-monitor-workspace-resource-id <amw-id
+```
+
+### Disable Log Analytics data collection
+
+If you're currently using the logs based Container Insights experience, then you can choose to stop ingesting metrics to Log Analytics to save on billing. Once you confirm the Prometheus backed Container Insights experience is sufficient for your purposes, complete the steps to stop metrics ingestion to Log Analytics.
+
+1. Navigate to the monitoring settings for your clusters by following the instructions on how to configure your [Container Insights data collection rule](./container-insights-data-collection-dcr.md#configure-data-collection)
+
+2. From the Cost presets dropdown, select "Logs and Events" and save to configure.
+
+> [!Note]
+> Disabling the Log Analytics metrics also disables the visualization dropdown in the toolbar. Revert to using one of the standard cost presets in the `Monitoring Settings` blade to re-enable the Log Analytics visualizations.
+
+## Known limitations and issues
+
+As this feature is currently in preview, there are several, known limitations, the following features aren't supported
+
+* Environment variable details
+* Filtering data by individual services
+* Live data viewing on the Cluster tab
+* Workbooks reports data
+* Node memory working set and RSS metrics
+* Partial or no data available in the multi-cluster view based on Container Insights DCR settings
+
+## Troubleshooting
+
+When using the Prometheus based Container Insights experience, you may encounter the following errors.
+
+### The charts are stuck in a loading state
+
+This issue occurs if the network traffic for the Azure Monitor workspace is blocked. The root cause of this is typically related to network policies, such as ad blocking software. To resolve this issue, disable the ad block or allowlist `monitor.azure.com` traffic and reload the page.
+
+### Unable to access Data Collection Rule
+
+This error occurs when the user doesn't have permissions to view the associated Prometheus data collection rule for the cluster or the data collection rule may have been deleted. To resolve this error, grant access to the Prometheus data collection rule or reconfigure managed Prometheus using the `Monitoring Settings` button in the toolbar.
+
+### Unable to access Azure Monitor workspace
+
+This error occurs when the user doesn't have permissions to view the associated Azure Monitor workspace for the cluster or the Azure Monitor workspace may have been deleted. To resolve this error, grant access to the Azure Monitor workspace or reconfigure managed Prometheus by deleting and [redeploying the addon](./kubernetes-monitoring-enable.md#enable-prometheus-and-grafana).
+
+### The data could not be retrieved
+
+This error typically occurs when querying large volumes of data and may be resolved by reducing the time range to a shorter window or filtering for fewer objects.
+
+### Data configuration error
+
+This error occurs when the recording rules may have been modified or deleted. Use the `Reconfigure` button to patch the recording rules and try again.
+
+### Access denied
+
+This occurs when the user's portal token expires or doesn't have permissions to view the associated Azure Monitor workspace for the cluster. This can typically be resolved by refreshing the browser session or logging in again.
+
+### An unknown error occurred
+
+If this error message persists, then contact support to open up a ticket.