Skip to content

Commit 0eedc0e

Browse files
authored
Update monitor-workspace.md
1 parent 7edb08d commit 0eedc0e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/azure-monitor/logs/monitor-workspace.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ The following table describes the categories from the _LogOperation function.
4545

4646

4747
### Ingestion
48-
Ingestion operations are issues that occurred during data ingestion including notification about reaching the Azure Log Analytics workspace limits. Error conditions in this category might suggest data loss, so they are particularly important to monitor. The table below provides details on these operations. See [Azure Monitor service limits](../../service-limits.md#log-analytics-workspaces) for service limits for Log Analytics workspaces.
48+
Ingestion operations are issues that occurred during data ingestion including notification about reaching the Azure Log Analytics workspace limits. Error conditions in this category might suggest data loss, so they are particularly important to monitor. The table below provides details on these operations. See [Azure Monitor service limits](../service-limits.md#log-analytics-workspaces) for service limits for Log Analytics workspaces.
4949

5050

5151
#### Operation: Data collection Stopped
@@ -97,7 +97,7 @@ Check the source of the affected data type:
9797
* If the data is being sent thru the HTTP Data Collector API, you will need to change your code\script to split the data before it’s ingested.
9898
* In case it’s a custom log, collected from a Log Analytics agent, then you’ll to change the logging settings of the application\tool to prevent this.
9999
* For any other data type, please raise a support case.
100-
</br>Read more: [Azure Monitor service limits](../../service-limits.md#data-ingestion-volume-rate)
100+
</br>Read more: [Azure Monitor service limits](../service-limits.md#data-ingestion-volume-rate)
101101

102102
### Data Collection
103103
#### Operation: Azure Activity Log Collection
@@ -108,7 +108,7 @@ Recommended Actions:
108108
* If you no longer have access to the subscription mentioned on the warning message:
109109
* If you no longer want to collect logs from this subscription, then please follow the same actions as step 1
110110
* If you still want to collect logs from this subscription, then please follow the same actions as step 1, contact the subscription owner to verify and fix your permissions and re-enable activity log collection
111-
* If you need to enable or re-enable activity log collection, we strongly recommend that you switch to the new collection method that leverages diagnostic settings, as it includes : [Azure Activity log](../../essentials/activity-log.md#send-to-log-analytics-workspace)
111+
* If you need to enable or re-enable activity log collection, we strongly recommend that you switch to the new collection method that leverages diagnostic settings, as it includes : [Azure Activity log](../essentials/activity-log.md#send-to-log-analytics-workspace)
112112

113113
### Agent
114114
#### Operation: Linux Agent

0 commit comments

Comments
 (0)