Skip to content

Commit 31f9cbc

Browse files
authored
Update alerts-log-api-switch.md
1 parent c67b69c commit 31f9cbc

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-monitor/platform/alerts-log-api-switch.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ The impacts of the switch of preference to scheduledQueryRules API are compiled
4343
The process of moving alert rules from [legacy Log Analytics Alert API](api-alerts.md) does not involve changing your alert definition, query, or configuration in any way. Your alert rules and monitoring are unaffected and the alerts will not stop or be stalled, during or after the switch. The only changes are:
4444

4545
- A change in API preference and access to your rules via a new API.
46-
- A modified alert URI containing the IDs used in the [legacy Log Analytics Alert API](api-alerts.md) in this strcture `<WorkspaceName>|<savedSearchId>|<scheduleId>|<ActionId>`.
46+
- A modified alert URI containing the IDs used in the [legacy Log Analytics Alert API](api-alerts.md) in this structure `<WorkspaceName>|<savedSearchId>|<scheduleId>|<ActionId>`.
4747

4848
> [!NOTE]
4949
> Once a user chooses to switch preference to the new [scheduledQueryRules API](https://docs.microsoft.com/rest/api/monitor/scheduledqueryrules) it is not possible to revert to using of the older [legacy Log Analytics Alert API](api-alerts.md).

0 commit comments

Comments
 (0)