7 hours 58 minutes
Welcome back on this episode, we're gonna take a look at your monitor a little bit more through our demo.
Our objectives include Well, really. Just taking a look at a demo inside the azure portal of how azure monitor is configured and works.
Here we are back in our azure portal. And before we go, look at your monitor. I want to go look at an individual resource. First, let's take a look at one of our virtual machines.
If you look at an individual resource like a virtual machine, you can see under monitoring, we have metrics and logs. Each individual resource inside of Azure should have its own set of metrics and logs. Here are filter is already set to V. M 01 and we can select different metrics such as Dace performance
or our standard percentage CPU.
And this chart will show us the average percentage CPU for this virtual machine over the last several hours. Now, this is the first machine just that I have on for demo purposes, so it doesn't have a lot of activity with it right now. Next, let's go take a look at locks.
This is where we can search the logs for events or other performance data and information that is occurring on the virtual machine. Here. I have a previously saved query that I wanted to rerun just to show you the results that come in
using this quarry window and the Cousteau quarry language, we can generate different information that is being logged on the virtual machine in this example the available megabytes of memory over time. This window up here is where we type in our query. Here, you can see we're pulling from the performance or perf table, and we're applying a couple of filters on it
where the time was generated
greater than one hour ago. And we're looking specifically at the counter name named Available megabytes. Over on the left. You can see other types of tables that we can pull from such a cz event and CeCe log information.
Now that we've looked at that, let's go back and take a look at azure monitor.
I already have it. Favorited, over here on the left.
Here on the overview page, you can see the three pillars we talked about earlier in the slides. When discussing azure monitor, we can take a look at metrics, logs and our alerts and actions. Let's go take a look at metrics.
Now, this page should look really familiar. This is exactly what we just looked at on our individual virtual machine resource. But here we can select
any resource available inside of her as your tenant toe. Look at its metrics.
We can narrow this down by subscription
resource groups and resource type.
Let me select my arm Demo Resource Group. I had previously
and is gonna pull up. All the resource is in this group or weaken view. It's metrics, data,
and again we can go and select percentage CPU.
The main point here is you don't have to go to each individual resource to view its metrics data. You can come right here to add your monitor and select different resource is to view its historical performance data.
And that's the same thing we're going to see over in logs
here inside the log analyzer. What you can do is select one or more resource is to perform log analysis against
here. You can select multiple resource is
and select our Microsoft Azure standard subscription,
and this will allow you to perform law queries against multiple resource is instead of going to each individual resource to perform the law. Query.
Next, let's go take a look at our alerts and action groups
before we create a new alert rule. Let's go in and manage actions
and let's create a new action group.
First, let's give it a name.
Select our subscription and choose the resource group to associate the action group with
and let's go select an action type.
This should be familiar from our slides. We can do something like send an email or an SMS message, activate an automation run book or use a connector to it. I t. S SIM service Such a service. Now for this simple example. Let's just go and select email
here. You can see we can check the box for email and put in the email address that we want to notify.
Unfortunately, it doesn't like my short name has to be less than 12 characters.
Let's save our action group.
Now Let's go back to our main page and create a new alert rule
here. We're going to select the resource that we want to target and monitor
will select our subscription
filter out by which type resource we want to monitor. In this case, I'm going to look at our virtual machines,
and I went to monitor V M 01
Next I can at a condition
again, we're going to stick with our standard percentage CPU,
and we're going to select our threshold for this. I'm going to say greater than 80%.
Now that we have a resource to find in the condition we want to alert on,
we're going to sign an action group for the alert.
Here you can select an existing one or create in action group, since we just created one. Previously in our demo, that's the one I'm going to go on in select.
This means you can reuse action groups across multiple alerts.
Finally, we'll give the alert rule of name
and we'll choose our severity for the alert.
You have options zero through four.
We're gonna go ahead and enable the rule upon creation
that does it for taking a look at your monitor. Let's go back to the slides and wrap this up
That does it for our demo. Wanted to follow up by saying we took a look at your monitor. How did you look at our metric and before some long queries? And finally configure action groups and alerts
coming up next, we're gonna take a deeper dive and to log analytics. See you in the next episode.