Skip to content

Commit f2de461

Browse files
resolving github issue
1 parent 6d39801 commit f2de461

File tree

2 files changed

+23
-3
lines changed

2 files changed

+23
-3
lines changed

articles/backup/backup-azure-monitoring-use-azuremonitor.md

Lines changed: 23 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -24,11 +24,11 @@ In Azure Monitor, you can create your own alerts in a Log Analytics workspace. I
2424
> [!IMPORTANT]
2525
> For information on the cost of creating this query, see [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/).
2626
27-
Select any of the graphs to open the **Logs** section of the Log Analytics workspace. In the **Logs** section, edit the queries and create alerts on them.
27+
Open the **Logs** section of the Log Analytics workspace and write a query your own Logs. When you select **New Alert Rule**, the Azure Monitor alert-creation page opens, as shown in the following image.
2828

29-
![Create an alert in a Log Analytics workspace](media/backup-azure-monitoring-laworkspace/la-azurebackup-customalerts.png)
29+
![Create an alert in a Log Analytics workspace](media/backup-azure-monitoring-laworkspace/custom-alert.png)
3030

31-
When you select **New Alert Rule**, the Azure Monitor alert-creation page opens, as shown in the following image. Here the resource is already marked as the Log Analytics workspace, and action group integration is provided.
31+
Here the resource is already marked as the Log Analytics workspace, and action group integration is provided.
3232

3333
![The Log Analytics alert-creation page](media/backup-azure-monitoring-laworkspace/inkedla-azurebackup-createalert.jpg)
3434

@@ -118,6 +118,26 @@ The default graphs give you Kusto queries for basic scenarios on which you can b
118118
on BackupItemUniqueId
119119
````
120120
121+
- Backup Storage Consumed per Backup Item
122+
123+
````Kusto
124+
CoreAzureBackup
125+
//Get all Backup Items
126+
| where OperationName == "BackupItem"
127+
//Get distinct Backup Items
128+
| distinct BackupItemUniqueId, BackupItemFriendlyName
129+
| join kind=leftouter
130+
(AddonAzureBackupStorage
131+
| where OperationName == "StorageAssociation"
132+
//Get latest record for each Backup Item
133+
| summarize arg_max(TimeGenerated, *) by BackupItemUniqueId
134+
| project BackupItemUniqueId , StorageConsumedInMBs)
135+
on BackupItemUniqueId
136+
| project BackupItemUniqueId , BackupItemFriendlyName , StorageConsumedInMBs
137+
| sort by StorageConsumedInMBs desc
138+
````
139+
140+
121141
### Diagnostic data update frequency
122142
123143
The diagnostic data from the vault is pumped to the Log Analytics workspace with some lag. Every event arrives at the Log Analytics workspace *20 to 30 minutes* after it's pushed from the Recovery Services vault. Here are further details about the lag:
43.1 KB
Loading

0 commit comments

Comments
 (0)