image blur

Author: Ankita Dutta

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

@@ -31,7 +31,7 @@ Azure Backup provides the following diagnostics events. Each event provides deta
 - Azure Backup Operations
 
 
-If you are still using the [legacy event](#legacy-event) AzureBackupReport, we recommend switching to using the events above.
+If you are still using the [legacy event](#legacy-event) Azure Backup Reporting Data, we recommend switching to using the events above.
 
 For more information, see [Data model for Azure Backup diagnostics events](./backup-azure-reports-data-model.md).
 
@@ -50,7 +50,7 @@ To send your vault diagnostics data to Log Analytics:
 1. Go to your *vault*, and select **Diagnostic Settings** > **+ Add diagnostic setting**.
 1. Provide a name to the *Diagnostics setting name*.
 1. Select the **Send to Log Analytics** checkbox, and select a *Log Analytics workspace*.
-1. Select **Resource specific** and select the following six events: **CoreAzureBackup**, **AddonAzureBackupJobs**, **AddonAzureBackupPolicy**, **AddonAzureBackupStorage**, **AzureBackupOperations**, and **AddonAzureBackupProtectedInstance**.
+1. Select **Resource specific** and select the following six events: **Core Azure Backup Data**, **Addon Azure Backup Job Data**, **Addon Azure Backup Policy Data**, and **Addon Azure Backup Protected Instance Data**, **Azure Backup Operations.**
 1. Select **Save**.
 
    :::image type="content" source="./media/backup-azure-configure-backup-reports/recovery-services-vault-diagnostics-settings-inline.png" alt-text="Screenshot shows the recovery services vault diagnostics settings." lightbox="./media/backup-azure-configure-backup-reports/recovery-services-vault-diagnostics-settings-expanded.png":::
@@ -60,7 +60,7 @@ To send your vault diagnostics data to Log Analytics:
 1. Go to your *vault*, and then select **Diagnostic Settings** > **+ Add diagnostic setting**.
 2. Provide a name to the *Diagnostics setting name*.
 3. Select the **Send to Log Analytics** checkbox and select a *Log Analytics workspace*.
-4. Select the following events: **CoreAzureBackup**, **AddonAzureBackupJobs**, **AddonAzureBackupPolicy**, and **AddonAzureBackupProtectedInstance**.
+4. Select the following events: **Core Azure Backup Data**, **Addon Azure Backup Job Data**, **Addon Azure Backup Policy Data**, and **Addon Azure Backup Protected Instance Data**.
 5. Select **Save**.
 
    :::image type="content" source="./media/backup-azure-diagnostics-events/backup-vault-diagnostics-settings.png" alt-text="Screenshot shows the backup vault diagnostics settings.":::   
@@ -69,11 +69,11 @@ To send your vault diagnostics data to Log Analytics:
 After data flows into the Log Analytics workspace, dedicated tables for each of these events are created in your workspace. You can query any of these tables directly. You can also perform joins or unions between these tables if necessary.
 
 > [!IMPORTANT]
-> *AddonAzureBackupAlerts* refers to the alerts being generated by the classic alerts solution. As classic alerts solution is on deprecation path in favour of Azure Monitor-based alers, we recommend you not to select the event *AddonAzureBackupAlerts* when configuring diagnostics settings. To send the fired Azure Monitor-based alerts to a destination of your choice, you can create an alert processing rule and action group that routes these alerts to a logic app, webhook, or runbook that in turn sends these alerts to the required destination.
+> *Addon Azure Backup Alerts* refers to the alerts being generated by the classic alerts solution. As classic alerts solution is on deprecation path in favour of Azure Monitor-based alers, we recommend you not to select the event *Addon Azure Backup Alerts* when configuring diagnostics settings. To send the fired Azure Monitor-based alerts to a destination of your choice, you can create an alert processing rule and action group that routes these alerts to a logic app, webhook, or runbook that in turn sends these alerts to the required destination.
 >
-> For Recovery Services vault, the six events- *CoreAzureBackup*, *AddonAzureBackupJobs*, *AddonAzureBackupPolicy*, *AddonAzureBackupStorage*, *AzureBackupOperations*, and *AddonAzureBackupProtectedInstance* are supported *only* in the *resource-specific* mode for Recovery Services in Backup reports. If you try to send data for these events in the Azure diagnostics mode, no data will appear in Backup reports.
+> For Recovery Services vault, the six events- *Core Azure Backup*, *Addon Azure Backup Jobs*, *Addon Azure Backup Policy*, *Addon Azure Backup Storage*, *Azure Backup Operations*, and *Addon Azure Backup Protected Instance* are supported *only* in the *resource-specific* mode for Recovery Services in Backup reports. If you try to send data for these events in the Azure diagnostics mode, no data will appear in Backup reports.
 >
-> For Backup vaults, since information on the frontend size and backup storage consumed are already included in the *CoreAzureBackup* and *AddonAzureBackupProtectedInstances* events (to aid query performance), the *AddonAzureBackupStorage event* isn't applicable for Backup vault, to avoid creation of redundant tables.
+> For Backup vaults, since information on the frontend size and backup storage consumed are already included in the *Core Azure Backup* and *Addon Azure Backup Protected Instances* events (to aid query performance), the *Addon Azure Backup Storage event* isn't applicable for Backup vault, to avoid creation of redundant tables.
 
 ## Legacy event
 
@@ -124,17 +124,19 @@ Currently, we continue to support the *AzureBackupReport* event for Recovery Ser
 
     ![Workspace query](./media/backup-azure-diagnostics-events/workspace-query.png)
 
-2. Use the [built-in Azure Policy definitions](./azure-policy-configure-diagnostics.md) in Azure Backup to add a new diagnostics setting for all vaults in a specified scope. This policy adds a new diagnostics setting to vaults that either don't have a diagnostics setting or have only a legacy diagnostics setting. This policy can be assigned to an entire subscription or resource group at a time. You must have Owner access to each subscription for which the policy is assigned.
+2. Use the [built-in Azure Policy definitions](./azure-policy-configure-diagnostics.md)  in Azure Backup to add a new diagnostics setting for all vaults in a specified scope. This policy adds a new diagnostics setting to vaults that either don't have a diagnostics setting or have only a legacy diagnostics setting. This policy can be assigned to an entire subscription or resource group at a time. You must have Owner access to each subscription for which the policy is assigned. 
 
-You might choose to have separate diagnostics settings for *AzureBackupReport* and the six new events until you've migrated all of your custom queries to use data from the new tables. The following image shows an example of a vault that has two diagnostic settings. The first setting, named **Setting1**, sends data of an *AzureBackupReport* event to a Log Analytics workspace in Azure diagnostics mode. The second setting, named **Setting2**, sends data of the six new Azure Backup events to a Log Analytics workspace in the resource-specific mode.
+You might choose to have separate diagnostics settings for *Azure Backup Report* and the six new events until you've migrated all of your custom queries to use data from the new tables. The following image shows an example of a vault that has two diagnostic settings. The first setting, named **Setting1**, sends data of an *Azure Backup Report* event to a Log Analytics workspace in Azure diagnostics mode. The second setting, named **Setting2**, sends data of the six new Azure Backup events to a Log Analytics workspace in the resource-specific mode.
 
 ![Two settings](./media/backup-azure-diagnostics-events/two-settings-example.png)
 
 > [!IMPORTANT]
-> The AzureBackupReport event is supported *only* in Azure diagnostics mode. *If you try to send data for this event in the resource-specific mode, no data will flow to the Log Analytics workspace.*
+> The Azure Backup Report event is supported *only* in Azure diagnostics mode. *If you try to send data for this event in the resource-specific mode, no data will flow to the Log Analytics workspace.*
 
 > [!NOTE]
-> 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 AzureBackupReport going forward.
+> 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. 
+
+
 
 ## Send Azure Site Recovery events to Log Analytics