1
00:00:01,040 --> 00:00:06,760
So now we're at a cmd console, and if we want to get into PowerShell, we

2
00:00:06,760 --> 00:00:12,600
can simply type PowerShell, and now we can do a get‑command to see what

3
00:00:12,600 --> 00:00:17,740
commands are available on this endpoint. And it's just running through

4
00:00:17,740 --> 00:00:21,400
them all, and I'm going to Ctrl+C to break display, but you see the point

5
00:00:21,400 --> 00:00:27,140
here. We now are able to use PowerShell in the old compiled executables.

6
00:00:27,140 --> 00:00:30,970
We're on the file system of the virtual machine with administrative

7
00:00:30,970 --> 00:00:35,450
privilege, so the idea is that we may hopefully be able to fix up problems.

8
00:00:35,450 --> 00:00:39,480
I mean, with the registry, you can do registry modification

9
00:00:39,480 --> 00:00:42,390
with PowerShell if you need to work with environment variables,

10
00:00:42,390 --> 00:00:48,240
or services, or Windows features, all of that is totally in scope for you.

11
00:00:48,240 --> 00:00:51,860
And then when we're finished with the serial console, we can just close the

12
00:00:51,860 --> 00:00:56,810
window and we're done, all right? Okay, that just about wraps us up. One last

13
00:00:56,810 --> 00:01:02,560
thing I want to do is go over to Azure Monitor, and I show you how to use the

14
00:01:02,560 --> 00:01:09,080
Virtual Machines insight solution elsewhere in the course. This is a workbook

15
00:01:09,080 --> 00:01:14,620
that allows you to dive in and view pre‑created graphics that show you, in

16
00:01:14,620 --> 00:01:20,640
this case, this is a feature called Service Map, which will show dependencies.

17
00:01:20,640 --> 00:01:23,940
We can see running processes on that machine,

18
00:01:23,940 --> 00:01:28,830
we can see inbound client connectivity and their IP addresses,

19
00:01:28,830 --> 00:01:32,040
outbound connectivity to remote machines,

20
00:01:32,040 --> 00:01:32,920
what ports,

21
00:01:32,920 --> 00:01:37,850
what servers this machine is connecting from. Very powerful tool

22
00:01:37,850 --> 00:01:43,630
indeed. The VM Insights also has a number of performance related

23
00:01:43,630 --> 00:01:47,260
metrics that we can look at. As you can see here, we can easily take a

24
00:01:47,260 --> 00:01:52,410
look at the storage of this machine, the OS disk, and the temp disk,

25
00:01:52,410 --> 00:01:58,140
the utilization, we can see our memory, available memory.

26
00:01:58,140 --> 00:02:01,300
All of these are called metrics views, and metrics is

27
00:02:01,300 --> 00:02:06,880
time‑sampled numeric data that, in this case these metrics views

28
00:02:06,880 --> 00:02:11,440
were created for us, they're curated for us by Microsoft based

29
00:02:11,440 --> 00:02:15,640
on working with their customers, what they find to be most helpful.

30
00:02:15,640 --> 00:02:18,910
Now you always can come into Metrics Explorer yourself

31
00:02:18,910 --> 00:02:21,240
if you know what you're looking for.

32
00:02:21,240 --> 00:02:23,680
You can select your scope, what you're looking for.

33
00:02:23,680 --> 00:02:27,690
I think my monitor is in here, so let me select that

34
00:02:27,690 --> 00:02:32,240
monitorvm from the list, and then we can come in and gather

35
00:02:32,240 --> 00:02:34,260
from any of these available metrics.

36
00:02:34,260 --> 00:02:39,500
Now the metrics that are available, Azure always collects baseline

37
00:02:39,500 --> 00:02:43,470
metrics, but if you want to go beyond just the baseline,

38
00:02:43,470 --> 00:02:48,610
you're going to need to enable diagnostic settings for that machine.

39
00:02:48,610 --> 00:02:51,540
Percent CPU, that's a pretty common one.

40
00:02:51,540 --> 00:02:52,130
And again,

41
00:02:52,130 --> 00:02:56,440
just to mention it one more time, the idea is you might realize, whoa,

42
00:02:56,440 --> 00:03:01,040
this machine is pretty constrained CPU‑wise. There, you might think that

43
00:03:01,040 --> 00:03:05,520
you would resize the machine or maybe it's just periodically you wonder

44
00:03:05,520 --> 00:03:07,210
if the machine is being constrained.

45
00:03:07,210 --> 00:03:12,330
You can create an alert rule that will do an evaluation whenever

46
00:03:12,330 --> 00:03:16,520
that metric value exceeds a certain threshold, let's say, that

47
00:03:16,520 --> 00:03:19,840
would trip off the alert and you can configure notifications as

48
00:03:19,840 --> 00:03:27,000
well as code to run automatically in response to that alert firing. Pretty powerful stuff.