1
00:00:00,740 --> 00:00:03,240
Monitor Azure File Sync.

2
00:00:03,240 --> 00:00:04,710
Well, there is no surprise, I think,

3
00:00:04,710 --> 00:00:07,670
that when we're talking about an Azure Resource Manager service,

4
00:00:07,670 --> 00:00:11,130
like AFS, we have native integration with Azure Monitor,

5
00:00:11,130 --> 00:00:13,610
and here we're seeing a screenshot from one of my friends,

6
00:00:13,610 --> 00:00:15,880
a Microsoft engineer named Billy York.

7
00:00:15,880 --> 00:00:20,120
He created a workbook that you can actually download from his GitHub repo.

8
00:00:20,120 --> 00:00:24,040
You can see the attribution URL in the lower left corner of this slide,

9
00:00:24,040 --> 00:00:26,540
and I also, in the exercise files,

10
00:00:26,540 --> 00:00:29,980
point you to the repo and a nice blog post Billy wrote up.

11
00:00:29,980 --> 00:00:33,600
What he's doing here is just using the Azure Monitor workbook

12
00:00:33,600 --> 00:00:38,640
interface to create visualizations that pull useful event

13
00:00:38,640 --> 00:00:41,440
messages for the Azure File Sync service.

14
00:00:41,440 --> 00:00:45,010
Remember that in Azure Monitor, you have two types of diagnostics data,

15
00:00:45,010 --> 00:00:47,830
metrics, which is time series numeric data,

16
00:00:47,830 --> 00:00:50,890
and alerts, which you can raise on metric thresholds.

17
00:00:50,890 --> 00:00:53,920
I'm hoping that you're also using Azure Log Analytics,

18
00:00:53,920 --> 00:00:57,030
which can ingest your Azure File Sync event logs on your

19
00:00:57,030 --> 00:01:00,580
registered server and also capture data from the Azure File

20
00:01:00,580 --> 00:01:02,180
Sync sync group in the cloud.

21
00:01:02,180 --> 00:01:06,430
You can use the Kusto query language to report on that information and

22
00:01:06,430 --> 00:01:12,000
create Azure alerts based on those Kusto queries. Again, I'll show you how that works in the demo.