Skip to content

Commit 5e504f8

Browse files
authored
Update backup-azure-diagnostic-events.md
1 parent 5ed8840 commit 5e504f8

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/backup/backup-azure-diagnostic-events.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -109,7 +109,7 @@ Azure Backup and Azure Site Recovery events are sent from the same Recovery Serv
109109
110110
To summarize:
111111
112-
* If you already have Log Analytics diagnostics set up with Azure diagnostics and have written custom queries on top of it, keep that setting *intact* until you migrate your queries to use data from the new events.
112+
* If you already have Log Analytics diagnostics set up with Azure Diagnostics and have written custom queries on top of it, keep that setting *intact* until you migrate your queries to use data from the new events.
113113
* If you also want to onboard onto new tables, as we recommend, create a **new** diagnostics setting, select **Resource specific**, and select the six new events.
114114
* If you're currently sending Azure Site Recovery events to Log Analytics, *do not* choose the resource-specific mode for these events. Otherwise, data for these events won't flow into your Log Analytics workspace. Instead, create an additional diagnostic setting, select **Azure diagnostics**, and select the relevant Azure Site Recovery events.
115115

0 commit comments

Comments
 (0)