Skip to content

Commit 7c762ef

Browse files
author
AbhishekMallick-MS
committed
Transferred ASR content to respective location
1 parent 5663958 commit 7c762ef

File tree

4 files changed

+26
-26
lines changed

4 files changed

+26
-26
lines changed

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

Lines changed: 3 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Use diagnostics settings for Recovery Services vaults and Backup vault in
33
description: This article describes how to use the old and new diagnostics events for Azure Backup.
44
ms,service: backup
55
ms.topic: how-to
6-
ms.date: 04/30/2024
6+
ms.date: 12/30/2024
77
author: AbhishekMallick-MS
88
ms.author: v-abhmallick
99
ms.custom: engagement-fy2
@@ -136,28 +136,7 @@ You might choose to have separate diagnostics settings for *Azure Backup Report*
136136
> [!NOTE]
137137
> The toggle for **Azure diagnostics** or **Resource specific** appears only if the user selects **Send to Log Analytics**. To send data to a storage account or an event hub, a user selects the required destination and selects the check boxes for any of the desired events, without any additional inputs. Again, we recommend that you don't choose the legacy event Azure Backup Reporting Data going forward.
138138
139-
140-
141-
## Send Azure Site Recovery events to Log Analytics
142-
143-
Azure Backup and Azure Site Recovery events are sent from the same Recovery Services vault. Azure Site Recovery offers two resource-specific tables - *Azure Site Recovery Jobs* and *Azure Site Recovery Replicated Items Details*. Users must choose resource specific for the two tables mentioned. Choosing the resource-specific mode for Azure Site Recovery events for any other table for site recovery prevents the required data from being sent to the Log Analytics workspace. Azure Site Recovery Jobs is available as both resource specific and legacy table.
144-
145-
![Site Recovery events](./media/backup-azure-diagnostics-events/site-recovery-settings.png)
146-
147-
> [!NOTE]
148-
> When you create a Log Analytics workspace, it does not matter if the Recovery Services vault is located in a different region.
149-
150-
151-
To summarize:
152-
153-
* 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.
154-
* 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.
155-
* 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.
156-
157-
The following image shows an example of a user who has three diagnostics settings for a vault. The first setting, named **Setting1**, sends data from an Azure Backup Reporting Data event to a Log Analytics workspace in Azure diagnostics mode. The second setting, named **Setting2**, sends data from the six new Azure Backup events to a Log Analytics workspace in the resource-specific mode. The third setting, named **Setting3**, sends data from the Azure Site Recovery events to a Log Analytics workspace in Azure diagnostics mode.
158-
159-
![Three settings](./media/backup-azure-diagnostics-events/three-settings-example.png)
160-
161139
## Next steps
162140
163-
[Learn the Log Analytics data model for the diagnostics events](./backup-azure-reports-data-model.md)
141+
- [Learn the Log Analytics data model for the diagnostics events](./backup-azure-reports-data-model.md).
142+
- [Learn how to send Azure Site Recovery events to Log Analytics](../site-recovery/report-site-recovery.md#send-azure-site-recovery-events-to-log-analytics).

articles/site-recovery/report-site-recovery.md

Lines changed: 23 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Configure Azure Site Recovery reports
33
description: This article describes how to configure reports for Azure Site Recovery.
44
ms.service: azure-site-recovery
55
ms.topic: conceptual
6-
ms.date: 05/10/2024
6+
ms.date: 12/30/2024
77
ms.author: ankitadutta
88
author: ankitaduttaMSFT
99
---
@@ -118,6 +118,27 @@ The Power BI template app for reporting, which sources data from an Azure storag
118118

119119
Additionally, the V1 schema for sending diagnostics data to a storage account or an LA Workspace is also being deprecated. If you have created any custom queries or automations using the V1 schema, it is recommended that you update them to use the currently supported V2 schema.
120120

121+
## Send Azure Site Recovery events to Log Analytics
122+
123+
Azure Backup and Azure Site Recovery events are sent from the same Recovery Services vault. Azure Site Recovery offers two resource-specific tables - *Azure Site Recovery Jobs* and *Azure Site Recovery Replicated Items Details*. Users must choose resource specific for the two tables mentioned. Choosing the resource-specific mode for Azure Site Recovery events for any other table for site recovery prevents the required data from being sent to the Log Analytics workspace. Azure Site Recovery Jobs is available as both resource specific and legacy table.
124+
125+
![Screenshot shows the Azure Site Recovery events.](./media/report-site-recovery/site-recovery-settings.png)
126+
127+
> [!NOTE]
128+
> When you create a Log Analytics workspace, it does not matter if the Recovery Services vault is located in a different region.
129+
130+
131+
To summarize:
132+
133+
* 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.
134+
* 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.
135+
* 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.
136+
137+
The following image shows an example of a user who has three diagnostics settings for a vault. The first setting, named **Setting1**, sends data from an Azure Backup Reporting Data event to a Log Analytics workspace in Azure diagnostics mode. The second setting, named **Setting2**, sends data from the six new Azure Backup events to a Log Analytics workspace in the resource-specific mode. The third setting, named **Setting3**, sends data from the Azure Site Recovery events to a Log Analytics workspace in Azure diagnostics mode.
138+
139+
![Screenshot shows a vault with three diagnostic settings.](./media/report-site-recovery/three-settings-example.png)
140+
141+
121142
## Next steps
122143

123-
- [Diagnostics in Backup and Site Recovery](../backup/backup-azure-diagnostic-events.md)
144+
- [Diagnostics in Azure Backup](../backup/backup-azure-diagnostic-events.md)

0 commit comments

Comments
 (0)