Skip to content

Commit b3f93f3

Browse files
committed
Improving Acrolinx score
1 parent bdba286 commit b3f93f3

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
@@ -104,7 +104,7 @@ The following section provides information on data collection.
104104

105105
#### Operation: Azure Activity Log collection
106106

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."
108108

109109
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.
110110

@@ -132,7 +132,7 @@ Check the `_LogOperation` table for the agent event:</br>
132132

133133
`_LogOperation | where TimeGenerated >= ago(6h) | where Category == "Agent" | where Operation == "Linux Agent" | distinct _ResourceId`
134134

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.
136136

137137
## Alert rules
138138

@@ -147,7 +147,7 @@ Use the process in [Create, view, and manage log alerts by using Azure Monitor](
147147
| `_LogOperation | where Level == "Error"` | 0 | 5 | 5 |
148148
| `_LogOperation | where Level == "Warning"` | 0 | 1,440 | 1,440 |
149149

150-
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.
151151

152152
To create an alert rule for a specific operation, use a query that includes the **Category** and **Operation** columns.
153153

0 commit comments

Comments
 (0)