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-diagnostics-mode-data-model.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -458,7 +458,9 @@ Below are a few samples to help you write queries on Azure Backup data that resi
458
458
## V1 schema vs V2 schema
459
459
Earlier, diagnostics data for Azure Backup Agent and Azure VM backup was sent to Azure Diagnostics table in a schema referred to as ***V1 schema***. Subsequently, new columns were added to support other scenarios and workloads, and diagnostics data was pushed in a new schema referred to as ***V2 schema***.
460
460
461
-
For reasons of backward-compatibility, diagnostics data for Azure Backup Agent and Azure VM backup is currently sent to Azure Diagnostics table in both V1 and V2 schema (with V1 schema now on a deprecation path). You can identify which records in Log Analytics are of V1 schema by filtering records for SchemaVersion_s=="V1" in your log queries.
461
+
For reasons of backward-compatibility, diagnostics data for Azure Backup Agent and Azure VM backup is currently sent to Azure Diagnostics table in both V1 and V2 schema (with V1 schema now on a deprecation path). You can identify which records in Log Analytics are of V1 schema by filtering records for SchemaVersion_s=="V1" in your log queries.
462
+
463
+
Refer to the third column 'Description' in the [data model]((https://docs.microsoft.com/azure/backup/backup-azure-diagnostics-mode-data-model#using-azure-backup-data-model)) described above to identify which columns belong to V1 schema only.
Copy file name to clipboardExpand all lines: articles/backup/backup-azure-monitoring-use-azuremonitor.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,6 +40,9 @@ The defining characteristic of an alert is its triggering condition. Select **Co
40
40
41
41
If necessary, you can edit the Kusto query. Choose a threshold, period, and frequency. The threshold determines when the alert will be raised. The period is the window of time in which the query is run. For example, if the threshold is greater than 0, the period is 5 minutes, and the frequency is 5 minutes, then the rule runs the query every 5 minutes, reviewing the previous 5 minutes. If the number of results is greater than 0, you're notified through the selected action group.
42
42
43
+
> [!NOTE]
44
+
> To run the alert rule once a day, across all the events/logs that were created on the given day, change the value of both 'period' and 'frequency' to 1440, i.e., 24 hours.
45
+
43
46
#### Alert action groups
44
47
45
48
Use an action group to specify a notification channel. To see the available notification mechanisms, under **Action groups**, select **Create New**.
@@ -59,6 +62,7 @@ The default graphs give you Kusto queries for basic scenarios on which you can b
59
62
````Kusto
60
63
AddonAzureBackupJobs
61
64
| where JobOperation=="Backup"
65
+
| summarize arg_max(TimeGenerated,*) by JobUniqueId
62
66
| where JobStatus=="Completed"
63
67
````
64
68
@@ -67,6 +71,7 @@ The default graphs give you Kusto queries for basic scenarios on which you can b
67
71
````Kusto
68
72
AddonAzureBackupJobs
69
73
| where JobOperation=="Backup"
74
+
| summarize arg_max(TimeGenerated,*) by JobUniqueId
70
75
| where JobStatus=="Failed"
71
76
````
72
77
@@ -75,6 +80,7 @@ The default graphs give you Kusto queries for basic scenarios on which you can b
75
80
````Kusto
76
81
AddonAzureBackupJobs
77
82
| where JobOperation=="Backup"
83
+
| summarize arg_max(TimeGenerated,*) by JobUniqueId
78
84
| where JobStatus=="Completed"
79
85
| join kind=inner
80
86
(
@@ -91,6 +97,7 @@ The default graphs give you Kusto queries for basic scenarios on which you can b
91
97
````Kusto
92
98
AddonAzureBackupJobs
93
99
| where JobOperation=="Backup" and JobOperationSubType=="Log"
100
+
| summarize arg_max(TimeGenerated,*) by JobUniqueId
94
101
| where JobStatus=="Completed"
95
102
| join kind=inner
96
103
(
@@ -107,6 +114,7 @@ The default graphs give you Kusto queries for basic scenarios on which you can b
107
114
````Kusto
108
115
AddonAzureBackupJobs
109
116
| where JobOperation=="Backup"
117
+
| summarize arg_max(TimeGenerated,*) by JobUniqueId
Copy file name to clipboardExpand all lines: articles/backup/configure-reports.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,11 +16,12 @@ Today, Azure Backup provides a reporting solution that uses [Azure Monitor logs]
16
16
17
17
## Supported scenarios
18
18
19
-
- Backup reports are supported for Azure VMs, SQL in Azure VMs, SAP HANA/ASE in Azure VMs, Microsoft Azure Recovery Services (MARS) agent, Microsoft Azure Backup Server (MABS), and System Center Data Protection Manager (DPM). Data for Azure File Share backup is currently not visible in Backup Reports.
19
+
- Backup reports are supported for Azure VMs, SQL in Azure VMs, SAP HANA in Azure VMs, Microsoft Azure Recovery Services (MARS) agent, Microsoft Azure Backup Server (MABS), and System Center Data Protection Manager (DPM). Data for Azure File Share backup is currently not visible in Backup Reports.
20
20
- For DPM workloads, Backup reports are supported for DPM Version 5.1.363.0 and above and Agent Version 2.0.9127.0 and above.
21
21
- For MABS workloads, Backup reports are supported for MABS Version 13.0.415.0 and above and Agent Version 2.0.9170.0 and above.
22
22
- Backup reports can be viewed across all backup items, vaults, subscriptions, and regions as long as their data is being sent to a Log Analytics workspace that the user has access to. To view reports for a set of vaults, you only need to have reader access to the Log Analytics workspace to which the vaults are sending their data. You don't need to have access to the individual vaults.
23
23
- If you're an [Azure Lighthouse](https://docs.microsoft.com/azure/lighthouse/) user with delegated access to your customers' subscriptions, you can use these reports with Azure Lighthouse to view reports across all your tenants.
24
+
- Currently, data can be viewed in Backup Reports across a maximum of 100 Log Analytics Workspaces (across tenants).
24
25
- Data for log backup jobs currently isn't displayed in the reports.
25
26
26
27
## Get started
@@ -75,6 +76,9 @@ The report contains various tabs:
> For DPM workloads, users might see a slight difference (of the order of 20 MB per DPM server) between the usage values shown in the reports as compared to the aggregate usage value as shown in the Recovery services vault overview tab. This difference is accounted for by the fact that every DPM server being registered for backup has an associated 'metadata' datasource which is not surfaced as an artifact for reporting.
81
+
78
82
-**Jobs**: Use this tab to view long-running trends on jobs, such as the number of failed jobs per day and the top causes of job failure. You can view this information at both an aggregate level and at a Backup-item level. Select a particular Backup item in a grid to view detailed information on each job that was triggered on that Backup item in the selected time range.
@@ -121,7 +125,7 @@ The widgets in the Backup report are powered by Kusto queries, which run on the
121
125
122
126
- The earlier Power BI template app for reporting, which sourced data from an Azure storage account, is on a deprecation path. We recommend that you start sending vault diagnostic data to Log Analytics to view reports.
123
127
124
-
-*In addition, the [V1 schema](https://docs.microsoft.com/azure/backup/backup-azure-diagnostics-mode-data-model#v1-schema-vs-v2-schema) of sending diagnostics data to a storage account or an LA Workspace is also on a deprecation path. This means that if you have written any custom queries or automations based on the V1 schema, you are advised to update these queries to use the currently supported V2 schema.
128
+
- In addition, the [V1 schema](https://docs.microsoft.com/azure/backup/backup-azure-diagnostics-mode-data-model#v1-schema-vs-v2-schema) of sending diagnostics data to a storage account or an LA Workspace is also on a deprecation path. This means that if you have written any custom queries or automations based on the V1 schema, you are advised to update these queries to use the currently supported V2 schema.
0 commit comments