Coming up, we take a look at Azure Monitor
that gives you built in platform monitoring for all of the visibility into the performance,
health and state of your Azure resources.
We'll show you how it works,
how to create alerts and enable deeper insights and analytics
with your preferred monitoring system to perform troubleshooting.
When you are managing cloud-based services,
it's important to have visibility into anything
that can impact app availability, performance, or other SLA's.
Azure Monitor is a service that provides a single source for monitoring Azure resources.
With it, you can visualize,
query, route, archive
and take action on the metrics and logs coming from resources in Azure.
These insights can be visualized within the Azure dashboard
giving you an end-to-end monitoring experience
for infrastructure metrics.
For your most important resources such as virtual machine and web servers.
Application telemetry,
such as response time and application dependencies.
And aggregated view of operational insights,
such as missing patches and change activity.
And last but not least,
Security Health and recommendations.
The azure dashboard is shareable and entirely customizable.
In this case, I have pinned the charts and tiles that are important to me.
Let's look at how Azure monitor works.
At the heart of Azure monitor
is a telemetry pipeline that connects to your Azure services.
And there are over 30 services that you can pull data from now.
And the list keeps growing.
Azure Monitor is collecting metrics,
logs, health and service events from these services.
This allows for a consistent monitoring experience inside the Azure portal.
You can unlock deeper insights by routing the raw telemetry
to Azure log analytics.
All of this can be visualized
in a single Azure dashboard as I just showed.
And of course you can consume the telemetry into your preferred monitoring solution
with our REST API's.
To get Azure Monitor working for you,
back in the Azure portal,
I navigate to this monitor icon.
I can explore all the raw telemetry from my Azure services
such as activity log,
which gives me information about events such as when we're shut down or deployment failure.
If I want more information I can always look at diagnostic logs.
I can move over to metrics,
which shows me all the performance telemetry from my servers and apps.
In this case, I have picked a virtual machine
and I can chart CPU utilization.
You will also notice that we have alerts here.
This is an important part of monitoring.
as it allows you to get notified
and take action against a specific event.
You can set alerts on your metrics
to check on the health and performance of your resources.
And new for general availability,
we've also enabled alerts on activity logs.
Here I have pre-populated
and allowed to flag deployment failures.
I can also determine how I want to be notified
via SMS, email, or trigger a web report right to your incident management system.
Next, let me show you how you can enable deeper insights
and analytics with a preferred monitoring system.
For this, let's go back to diagnostic logs.
One of the services that I want deeper insights on
is my logic app.
By going to the diagnostic settings,
I can choose the end point that I want to route the raw telemetry data to.
Here I can route it to Azure Log Analytics, which is part of OMS.
I can also choose to stream the telemetry to my event hubs,
or archive it in my storage account.
Lastly, let's also take a quick look at how Azure Monitor helps you triage an event.
For example, here I am looking at the metric
for my vm.
I can see unusual behavior.
Now if I look at resource help,
I see that the vm is available and running fine.
I can investigate further
by going over to activity log.
Here I can see that there has been a restart event
from John from my team.
Now I can follow up with John to learn more.
This was just a quick tour of Azure Monitor.
This is just the start of things to come.
You will see us continue to enrich metrics alerting and logging experiences.
Try it for yourself in the Azure portal.
And please give us your feedback.
Thanks for watching.
Microsoft Mechanics
www.microsoft.com/mechanics