fixes

Author: bwren

articles/azure-monitor/containers/container-insights-logs-schema.md

@@ -58,21 +58,24 @@ resources
 ```
 
 ## Kubernetes metadata and logs filtering
-Kubernetes metadata and logs filtering enhances the ContainerLogsV2 schema with additional Kubernetes metadata. The logs filtering feature provides filtering capabilities for both workload and platform  containers. These features give you richer context and improved visibility into your workloads.
+Kubernetes metadata and logs filtering extends the ContainerLogsV2 schema with additional Kubernetes metadata. The logs filtering feature provides filtering capabilities for both workload and platform  containers. These features give you richer context and improved visibility into your workloads.
 
 ### Features
 
 - **Enhanced ContainerLogV2 schema**
-    When Kubernetes Logs Metadata is enabled, it adds a column to `ContainerLogV2` called `KubernetesMetadata` that enhances troubleshooting with simple log queries and removes the need for joining with other tables. The fields in this column include: `PodLabels`, `PodAnnotations`, `PodUid`, `Image`, `ImageID`, `ImageRepo`, `ImageTag`. These fields enhance the troubleshooting experience using log queries without having to join with other tables.
+    When Kubernetes Logs Metadata is enabled, it adds a column to `ContainerLogV2` called `KubernetesMetadata` that enhances troubleshooting with simple log queries and removes the need for joining with other tables. The fields in this column include: `PodLabels`, `PodAnnotations`, `PodUid`, `Image`, `ImageID`, `ImageRepo`, `ImageTag`. These fields enhance the troubleshooting experience using log queries without having to join with other tables. See below for details on enabling the Kubernetes metadata feature.
 - **Log level**
     This feature adds a `LogLevel` column to ContainerLogV2 with the possible values **critical**, **error**, **warning**, **info**, **debug**, **trace**, or **unknown**. This helps you assess application health based on severity level. Adding the Grafana dashboard, you can visualize the log level trends over time and quickly pinpoint affected resources.
 - **Grafana dashboard for visualization**
-    The Grafana dashboard provides a color-coded visualization of the **log level** and also provides insights into Log Volume, Log Rate, Log Records, Logs. You can get time-sensitive analysis, dynamic insights into log level trends over time, and crucial real-time monitoring. The dashboard also provides a detailed breakdown by computer, pod, and container, which empowers in-depth analysis and pinpointed troubleshooting. 
+    The Grafana dashboard provides a color-coded visualization of the **log level** and also provides insights into Log Volume, Log Rate, Log Records, Logs. You can get time-sensitive analysis, dynamic insights into log level trends over time, and crucial real-time monitoring. The dashboard also provides a detailed breakdown by computer, pod, and container, which empowers in-depth analysis and pinpointed troubleshooting. See below for details on installing the Grafana dashboard.
 - **Annotation based log filtering for workloads**
-    Efficient log filtering through pod annotations. This allows you to focus on relevant information without sifting through noise. Annotation-based filtering enables you to exclude log collection for certain pods and containers by annotating the pod, which would help reduce the log analytics cost significantly. See [Annotation-based log filtering](./container-insights-logs-schema.md#annotation-based-log-filtering) for details on configuring annotation based filtering.
+    Efficient log filtering through pod annotations. This allows you to focus on relevant information without sifting through noise. Annotation-based filtering enables you to exclude log collection for certain pods and containers by annotating the pod, which would help reduce the log analytics cost significantly. See [Annotation-based log filtering](./container-insights-data-collection-filter.md#annotation-based-filtering-for-workloads) for details on configuring annotation based filtering.
 - **ConfigMap based log filtering for platform logs (System Kubernetes Namespaces)**
     Platform logs are emitted by containers in the system (or similar restricted) namespaces. By default, all the container logs from the system namespace are excluded to minimize the cost of data in your Log Analytics workspace. In specific troubleshooting scenarios though, container logs of system container play a crucial role. One example is the `coredns` container in the `kube-system` namespace.
 
+    > [!VIDEO https://learn-video.azurefd.net/vod/player?id=15c1c297-9e96-47bf-a31e-76056d026bd1]
+
+
 ### Enable Kubernetes metadata
 
 > [!IMPORTANT]
@@ -93,10 +96,6 @@ After a few minutes, the `KubernetesMetadata` column should be included with any
 :::image type="content" source="./media/container-insights-logging-v2/container-log-v2.png" lightbox="./media/container-insights-logging-v2/container-log-v2.png" alt-text="Screenshot that shows containerlogv2." border="false":::
 
 ### Install Grafana dashboard
-The Kubernetes Logs Metadata Grafana dashboard displays color-coded visualizations of log levels ranging from CRITICAL to UNKNOWN and also reports on Log Volume, Log Rate, Log Records, Logs. You can get time-sensitive analysis, dynamic insights into log level trends over time, and crucial real-time monitoring. It also provides a detailed breakdown by computer, pod, and container, which enables in-depth analysis and pinpointed troubleshooting.​ By visually distinguishing severity levels, you can quickly pinpoint affected resources, view in depth details, and zoom into critical details. 
-
-> [!VIDEO https://learn-video.azurefd.net/vod/player?id=15c1c297-9e96-47bf-a31e-76056d026bd1]
-
 
 > [!IMPORTANT]
 > If you enabled Grafana using the guidance at [Enable monitoring for Kubernetes clusters](./kubernetes-monitoring-enable.md#enable-prometheus-and-grafana) then your Grafana instance should already have access to your Azure Monitor workspace for Prometheus metrics. The Kubernetes Logs Metadata dashboard also requires access to your Log Analytics workspace which contains log data. See [How to modify access permissions to Azure Monitor](../../managed-grafana/how-to-permissions.md) for guidance on granting your Grafana instance the Monitoring Reader role for your Log Analytics workspace.

articles/azure-monitor/includes/waf-containers-cost.md

@@ -24,7 +24,7 @@ ms.date: 03/30/2023
 | Recommendation | Benefit |
 |:---|:---|
 | Enable collection of metrics through the Azure Monitor managed service for Prometheus. Be sure you do not also send Prometheus metrics to a Log Analytics Workspace.  | You can use [Azure Monitor managed service for Prometheus](https://aka.ms/managedpromdocumentation) for scraping Prometheus metrics from your cluster by [enabling Managed Prometheus](../containers/kubernetes-monitoring-enable.md#enable-prometheus-and-grafana). Note that you can configure Container insights to [collect Prometheus metrics in your Log Analytics workspace](../containers/container-insights-prometheus-logs.md), however this is not recommended as this is redundant with the data in Managed Prometheus and will result in additional cost. For details, see [Managed Prometheus pricing](https://azure.microsoft.com/pricing/details/monitor/). |
-| Configure agent to modify data collection in Container insights. |  Analyze the data collected by Container insights as described in [Controlling ingestion to reduce cost](../containers/container-insights-cost.md#control-ingestion-to-reduce-cost) and adjust your configuration to stop collection of data you don't need. |
+| Configure agent to modify data collection in Container insights. |  Analyze the data collected by Container insights as described in [Optimize monitoring costs for Container insights](../containers/container-insights-cost.md) and adjust your configuration to stop collection of data you don't need. |
 | Modify settings for collection of metric data by Container insights. | See [Enable cost optimization settings](../containers/container-insights-cost-config.md) for details on modifying both the frequency that metric data is collected and the namespaces that are collected by  Container insights. |
 | Disable Container insights collection of metric data if you don't use the Container insights experience in the Azure portal. | Container insights collects many of the same metric values as [Managed Prometheus](../containers/kubernetes-monitoring-enable.md#enable-prometheus-and-grafana). You can disable collection of these metrics by configuring Container insights to only collect **Logs and events** as described in [Enable cost optimization settings in Container insights](../containers/container-insights-cost-config.md#enable-cost-settings). This configuration disables the Container insights experience in the Azure portal, but you can use Grafana to visualize Prometheus metrics and Log Analytics to analyze log data collected by Container insights. |
 | If you don't query the container logs table regularly or use it for alerts, configure it as basic logs. | [Convert your Container insights schema to ContainerLogV2](../containers/container-insights-logs-schema.md) which is compatible with Basic logs and can provide significant cost savings as described in [Optimize monitoring costs for Container insights](../containers/container-insights-cost.md#configure-pricing-tiers). |