You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-monitor/logs/monitor-workspace.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,7 +45,7 @@ The following table describes the categories from the _LogOperation function.
45
45
46
46
47
47
### 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.
49
49
50
50
51
51
#### Operation: Data collection Stopped
@@ -97,7 +97,7 @@ Check the source of the affected data type:
97
97
* 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.
98
98
* 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.
99
99
* 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)
101
101
102
102
### Data Collection
103
103
#### Operation: Azure Activity Log Collection
@@ -108,7 +108,7 @@ Recommended Actions:
108
108
* If you no longer have access to the subscription mentioned on the warning message:
109
109
* If you no longer want to collect logs from this subscription, then please follow the same actions as step 1
110
110
* 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)
0 commit comments