You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-diagnostic-events.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,7 +47,7 @@ To send your vault diagnostics data to Log Analytics:
47
47
1. Select **Resource specific** in the toggle, and select the following five events: **CoreAzureBackup**, **AddonAzureBackupJobs**, **AddonAzureBackupPolicy**, **AddonAzureBackupStorage**, and **AddonAzureBackupProtectedInstance**.
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-reports-data-model.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Data model for Azure Backup diagnostics events
3
3
description: This data model is in reference to the Resource Specific Mode of sending diagnostic events to Log Analytics (LA).
4
4
ms.topic: conceptual
5
-
ms.date: 03/31/2023
5
+
ms.date: 04/18/2023
6
6
ms.service: backup
7
7
author: jyothisuri
8
8
ms.author: jsuri
@@ -19,7 +19,7 @@ Recovery Services vaults and Backup vaults send data to a common set of tables t
19
19
- One of the main reasons for this difference is that for Backup vaults, Azure Backup service does a 'flattening' of schemas to reduce the number of joins needed in queries, hence improving query performance. For example, if you are looking to write a query that lists all Backup vault jobs along with the friendly name of the datasource, and friendly name of the vault, you can get all of this information fro the AddonAzureBackupJobs table (without needing to do a join with CoreAzureBackup to get the datasource and vault names). Flattened schemas are currently supported only for Backup vaults and not yet for Recovery Services vaults.
20
20
- Apart from the above, there are also certain scenarios that are currently applicable for Recovery Services vaults only (for example, fields related to DPM workloads). This also leads to some differences in the schema between Backup vaults and Recovery Services vaults.
21
21
22
-
To understand which fields are specific to a particular vault type, and which fields are common across vault types, refer to the **Applicable Resource Types** column provided in the below sections. Refer to the [sample queries](./backup-azure-monitoring-use-azuremonitor.md#sample-kusto-queries) for more guidance on how to write queries on these tabls for Recovery Services vaults and Backup vaults.
22
+
To understand which fields are specific to a particular vault type, and which fields are common across vault types, refer to the **Applicable Resource Types** column provided in the below sections. For more information on how to write queries on these tables for Recovery Services vaults and Backup vaults, see the [sample queries](./backup-azure-monitoring-use-azuremonitor.md#sample-kusto-queries).
23
23
24
24
## CoreAzureBackup
25
25
@@ -114,7 +114,7 @@ This table provides details about alert related fields.
114
114
| BackupManagementType | Text | Recovery Services vault | Provider type for server doing backup job, for example, IaaSVM, FileFolder |
115
115
| CountOfAlertsConsolidated | Number | Recovery Services vault | Number of alerts consolidated if it's a consolidated alert |
116
116
| ProtectedContainerUniqueId | Text | Recovery Services vault | Unique identifier of the protected server associated with the alert |
117
-
| RecommendedAction | Text | Recovery Services vault | Action recommended to resolve the alert |
117
+
| RecommendedAction | Text | Recovery Services vault | Action recommended to resolving the alert |
118
118
| SchemaVersion | Text | Recovery Services vault | Current version of the schema, for example **V2**|
119
119
| State | Text | Recovery Services vault | Current state of the alert object, for example, Active, Deleted |
120
120
| StorageUniqueId | Text | Recovery Services vault | Unique ID used to identify the storage entity |
| DatasourceType | Text | Backup vault | Type of the datasource being backed up, for example, Microsoft.DBforPostgreSQL/servers/databases |
153
153
| BillingGroupType | Text | Backup vault | Type of the billing group, used to denote the unit at which billing information is calculated. For example, in the case of Azure PostgreSQL backup, protected instances and storage consumed are calculated at the server (DatasourceSet) level so the value is DatasourceSet in this scenario |
154
154
| SourceSizeInMBs | Double | Backup vault | Frontend size of the billing group |
155
-
| BillingGroupResourceGroupName | Text | Backup vault | Resource group in which te billing group exists |
155
+
| BillingGroupResourceGroupName | Text | Backup vault | Resource group in which the billing group exists |
156
156
157
157
158
158
## AddonAzureBackupJobs
@@ -167,11 +167,11 @@ This table provides details about job-related fields.
167
167
| AdhocOrScheduledJob | Text | Recovery Services vault, Backup vault | Field to specify if the job is Ad Hoc or Scheduled |
168
168
| BackupItemUniqueId | Text | Recovery Services vault, Backup vault | Unique ID used to identify the backup item related to the storage entity |
169
169
| BackupManagementServerUniqueId | Text | Recovery Services vault | Unique ID used to identify the backup management server related to the storage entity |
170
-
| BackupManagementType | Text | Recovery Services vault | Provider type for performing backup, for example, IaaSVM, FileFolder to which this job belongs to|
170
+
| BackupManagementType | Text | Recovery Services vault | Provider type for performing backup, for example, IaaS VM, File-Folder to which this job belongs.|
171
171
| DataTransferredInMB | Number | Recovery Services vault | Data transferred in MB for this job |
172
172
| JobDurationInSecs | Number | Recovery Services vault, Backup vault | Total job duration in seconds |
173
173
| JobFailureCode | Text | Recovery Services vault, Backup vault | Failure Code string because of which job failure happened |
174
-
| JobOperation | Text | Recovery Services vault, Backup vault | Operation for which job is run for example, Backup, Restore, Configure Backup |
174
+
| JobOperation | Text | Recovery Services vault, Backup vault | Operation for which job, is run for example, Backup, Restore, Configure Backup |
175
175
| JobOperationSubType | Text | Recovery Services vault, Backup vault | Sub Type of the Job Operation. For example, 'Log', in the case of Log Backup Job |
176
176
| JobStartDateTime | DateTime | Recovery Services vault, Backup vault | Date and time when job started running |
177
177
| JobStatus | Text | Recovery Services vault, Backup vault | Status of the finished job, for example, Completed, Failed |
@@ -248,7 +248,7 @@ This table provides details about policy-related fields.
248
248
| YearlyRetentionTimes | Text | Recovery Services vault, Backup vault | Date and time when yearly retention is configured |
249
249
| YearlyRetentionWeeksOfTheMonth | Text | Recovery Services vault, Backup vault | Weeks of the month selected for yearly retention |
250
250
| SourceSystem | Text | Recovery Services vault, Backup vault | Source system of the current data - Azure |
251
-
| PolicySubType | Text | Recovery Services vault |Sub-type of the policy, for example, Standard or Enhanced |
251
+
| PolicySubType | Text | Recovery Services vault |Subtype of the policy, for example, Standard or Enhanced |
252
252
| BackupIntervalInHours | Integer | Recovery Services vault, Backup vault | Interval of time between successive backup jobs. Applicable for Azure VM and Azure Disk backup |
253
253
| ScheduleWindowDuration | Integer | Recovery Services vault | Duration of the daily window in which backups can be run. Applicable for enhanced policy for Azure VM backup |
254
254
| ScheduleWindowStartTime | DateTime | Recovery Services vault | Start time of the daily window in which backups can be run. Applicable for enhanced policy for Azure VM backup |
@@ -258,7 +258,7 @@ This table provides details about policy-related fields.
258
258
| IncrementalBackupDaysOfTheWeek | String | Backup vault | Days of the week when incremental backup runs. Currently applicable for Azure Disk backup |
259
259
| IncrementalBackupFrequency | String | Backup vault | Frequency of incremental backup. Currently applicable for Azure Disk backup |
260
260
| IncrementalBackupTimes | String | Backup vault | Time of the day at which incremental backup is taken. Currently applicable for Azure Disk backup ||
261
-
| PolicyId | String | Backup vault | Azure Rsource Manager (ARM) ID of the backup policy |
261
+
| PolicyId | String | Backup vault | Azure Resource Manager (ARM) ID of the backup policy |
262
262
| SnapshotTierDailyRetentionDuration | Integer | Backup vault | Retention duration in days for daily snapshots. Applicable for Azure Blob and Azure Disk backup |
263
263
| SnapshotTierWeeklyRetentionDuration | Integer | Backup vault | Retention duration in weeks for weekly snapshots. Applicable for Azure Blob and Azure Disk backup |
264
264
| SnapshotTierMonthlyRetentionDuration | Integer | Backup vault | Retention duration in months for monthly snapshots. Applicable for Azure Blob and Azure Disk backup |
0 commit comments