Update data-collection-troubleshoot.md

Author: guywi-ms

articles/azure-monitor/logs/data-collection-troubleshoot.md

@@ -2,16 +2,21 @@
 title: Troubleshoot why data is no longer being collected in Azure Monitor
 description: Steps to take if data is no longer being collected in Log Analytics workspace in Azure Monitor.
 ms.topic: conceptual
-ms.date: 07/25/2023
+ms.date: 08/06/2024
 ---
 
 # Troubleshoot why data is no longer being collected in Azure Monitor
-This article provides guidance to detect when data collection in Azure Monitor stops and steps you can take to determine and correct the causes.
+This article explains how to detect when data collection in Azure Monitor stops and details steps you can take to address data collection issues.
 
 > [!IMPORTANT]
 > If you're troubleshooting data collection for a scenario that uses a data collection rule (DCR) such as Azure Monitor agent or Logs ingestion API, see [Monitor and troubleshoot DCR data collection in Azure Monitor](../essentials/data-collection-monitor.md) for additional troubleshooting information.
 
-## Data collection status
+## Data collection stopped because of the Log Analytics workspace daily cap
+
+The [daily cap](daily-cap.md) limits the amount of data that a Log Analytics workspace can collect in a day. When the daily cap is reached, data collection stops until the reset time. You can either wait for collection to automatically restart, or increase the daily data volume limit.
+
+### How to check the data collection status
+
 When data collection in a Log Analytics workspace stops, an event with a type of **Operation** is created in the workspace. Run the following query to check whether you're reaching the daily limit and missing data: 
 
 ```kusto
@@ -22,16 +27,11 @@ When data collection stops, the **OperationStatus** is **Warning**. When data co
 
 To be notified when data collection stops, use the steps described in the [Alert when daily cap is reached](daily-cap.md#alert-when-daily-cap-is-reached) section. To configure an e-mail, webhook, or runbook action for the alert rule, use the steps described in [create an action group](../alerts/action-groups.md). 
 
-## Daily cap was reached
-The [daily cap](daily-cap.md) limits the amount of data that a Log Analytics workspace can collect in a day. If the daily cap is reached, then data collection will stop until the reset time. Either wait for collection to automatically restart, or increase the daily data volume limit.
-
-
-## Legacy free pricing tier
-If your Log Analytics workspace is on the [legacy Free pricing tier](cost-logs.md#legacy-pricing-tiers) and has collected more than 500 MB of data in a day, data collection stops for the rest of the day. Wait until the following day for collection to automatically restart, or change to a paid pricing tier.
-
+## Daily ingestion limitation in the legacy free pricing tier 
+If your Log Analytics workspace is in the [legacy Free pricing tier](cost-logs.md#legacy-pricing-tiers) and has collected more than 500 MB of data in a day, data collection stops for the rest of the day. Wait until the following day for collection to automatically restart, or change to a paid pricing tier.
 
 ## Workspace reached the data ingestion volume rate
-The [default ingestion volume rate limit](../service-limits.md#log-analytics-workspaces)  for data sent from Azure resources using diagnostic settings is approximately 6 GB/min per workspace. This is an approximate value because the actual size can vary between data types, depending on the log length and its compression ratio. This limit doesn't apply to data that's sent from agents or the [Data Collector API](data-collector-api.md). 
+The [default ingestion volume rate limit](../service-limits.md#log-analytics-workspaces) for data sent from Azure resources using diagnostic settings is approximately 6 GB/min per workspace. This is an approximate value because the actual size can vary between data types, depending on the log length and its compression ratio. This limit doesn't apply to data that's sent from agents or the [Data Collector API](data-collector-api.md). 
 
 If you send data at a higher rate to a single workspace, some data is dropped, and an event is sent to the **Operation** table in your workspace every 6 hours while the threshold continues to be exceeded. If your ingestion volume continues to exceed the rate limit or you are expecting to reach it sometime soon, you can request an increase to your workspace by sending an email to [email protected] or by opening a support request. 
 
@@ -51,9 +51,9 @@ Your Azure subscription could be in a suspended state for one of the following r
 - Monthly spending limit reached (such as on an MSDN or Visual Studio subscription)
 
 
-## Limits summary
+## Other Log Analytics workspace limitations
 
-There are additional Log Analytics limits, some of which depend on the Log Analytics pricing tier. These are documented at [Azure subscription and service limits, quotas, and constraints](../service-limits.md#log-analytics-workspaces).
+There are other Log Analytics limits, some of which depend on the Log Analytics pricing tier. These are documented at [Azure subscription and service limits, quotas, and constraints](../service-limits.md#log-analytics-workspaces).
 
 
 ## Next steps