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
@@ -104,7 +104,7 @@ The following section provides information on data collection.
104
104
105
105
#### Operation: Azure Activity Log collection
106
106
107
-
"Access to the subscription was lost. Ensure that the \<**subscription id**\> subscription is in the \<**tenant id**\> Azure Active Directory tenant. If the subscription is transferred to another tenant, there is no impact to the services, but information for the tenant could take up to an hour to propagate."
107
+
"Access to the subscription was lost. Ensure that the \<**subscription id**\> subscription is in the \<**tenant id**\> Azure Active Directory tenant. If the subscription is transferred to another tenant, there's no impact to the services, but information for the tenant could take up to an hour to propagate."
108
108
109
109
In some situations, like moving a subscription to a different tenant, the Azure activity logs might stop flowing into the workspace. In those situations, you need to reconnect the subscription following the process described in this article.
110
110
@@ -132,7 +132,7 @@ Check the `_LogOperation` table for the agent event:</br>
132
132
133
133
`_LogOperation | where TimeGenerated >= ago(6h) | where Category == "Agent" | where Operation == "Linux Agent" | distinct _ResourceId`
134
134
135
-
The list will show the resource IDs where the agent has the wrong configuration. To mitigate the issue, reinstall the agents listed.
135
+
The list shows the resource IDs where the agent has the wrong configuration. To mitigate the issue, reinstall the agents listed.
136
136
137
137
## Alert rules
138
138
@@ -147,7 +147,7 @@ Use the process in [Create, view, and manage log alerts by using Azure Monitor](
These alert rules will respond the same to all operations with Error or Warning. As you become more familiar with the operations that are generating alerts, you might want to respond differently for particular operations. For example, you might want to send notifications to different people for particular operations.
150
+
These alert rules respond the same to all operations with Error or Warning. As you become more familiar with the operations that are generating alerts, you might want to respond differently for particular operations. For example, you might want to send notifications to different people for particular operations.
151
151
152
152
To create an alert rule for a specific operation, use a query that includes the **Category** and **Operation** columns.
0 commit comments