Hey friends, debugging network issues
across layers can be complicated.
Network Insights gives you a comprehensive
view of health and metrics for all
your deployed network resources without
requiring any additional configuration.
Dalan Mendonca is here to show me
how it works, today on Azure Friday.
Hey friends, I'm Scott Hanselman.
It's Azure Friday. I'm here with Dalan, who's
going to talk about Network Insights.
How are you? I'm good, Scott.
How are you? I'm lovely and I'm thrilled
to talk to you because I'm going to learn
new things about the unified network
monitoring experience available on Azure.
So what's the problem?
What is the problem that people who
have complicated networks that need
to troubleshoot and monitor in Azure?
So when you think about network monitoring,
customers are faced
with a plethora of tools and solutions
that we need to look at to find out
where the exact root causes.
So, if I may share my slides, you please.
So, when customers look at their
network monitoring toolchain,
they have a plethora of tools
at their disposal.
Things customers are interested
in our health monitoring.
How?
What is the health of my resource?
The metrics,
the alerts for that they have Azure Monitor,
their various networking resource
page with the window and find
out metrics or look at logs.
Next up for customers who are
interested in end to end connectivity.
This pace of installing agents and you know
starting tests across your hybrid network.
You have connection monitor and you have
traffic for traffic monitoring where
typically customers want to know what
what is what is hogging up my bandwidth.
They want to store logs
or audit and compliance.
There we have network energy flow logs
and traffic analytics and finally we
have a whole set of tools for checking
the state of your networks AIB flow
verify which is to verify any user
configured correctly or packet captures to.
Check is a check the state of your network
troubleshooting now walking across all
these tools can become a real pain,
especially when you're
debugging a live site issue.
You have to jump jump from tool to tool.
You know your scramble across
a variety of toolchains.
Nick for this when you between the
face this problem we built network
insights as a single network monitoring
hub where customers can come in so one
stops can find a one stop shop solution
for your phone network monitoring.
Now what now?
What does network insights
bring to the table?
In networking sites,
customers get a single health metric,
another console.
They don't have to look
in five different places,
you know to find alerts now
networking sizes available out of
the box with zero configuration.
Customers are wary of installing
agents to get signals,
but networking sites is available
without any agent or configuration.
It's ready to go from day one.
Customers can now search for resource
properties and associate resources.
What does that mean now?
For example,
the performance of your load
balancer is not just dependent
on the load balancer itself,
it the load balancer is connected
to a back end.
PMS or VM at the front and
it has a public IP.
If any of these resources faces an issue,
your load balancer performance
be affected in networking sites.
Fees made a way for you to drill
down from an alert to the load
balancer and to the connected
resources and find out the exact
tool stores and this is enabled by
what we call the dependencies view.
As you can see on screen it shows
all the connected resources and the
under the hood view of the resource.
One of the things that I notice
that that's so significant is this
idea of no agent configuration.
I think a lot of people are assuming
they have to install things,
but this is the magic of software
based networking, isn't it?
You've been able to enable this network
insights for everyone automatically,
so I don't have to push any buttons,
install anything or check any
boxes to make this happen.
Yes, so networking sites not only
incorporates outbox signals from,
you will get health metrics,
alerts for networking resources,
but of course there are customers who also
want to do configuration based monitoring.
They want to log their traffic
they want to set up alerts they
want to specifically monitor
connectivity from point A to point B.
Network Insights also incorporates
those signals into one place,
so if you want to select board box solutions,
you have it ready.
If you want to set up advanced
elementary tests that are
custom bespoke to your network,
those two are aggregated
and available inside.
So networking sites very cool.
So what does it look like
in the Azure portal?
Let's begin with the demo.
So what we're seeing on screen is the
networking sites tab in Azure monitor.
It's available right inside as you
want and not a new experience,
not a new thing. You have to learn.
What you're seeing on the screen
and what you can see here is two
different three different tabs here.
Network, health, connectivity in traffic.
So let's talk about the network Health app,
which is available out of the
box without any configuration.
As you can see here,
this is a healthy Gallery of of all the
networking resources that are available.
You have application gateways,
yarn, VPN connections,
exercise circuits and more.
So right away I can add a glance,
know what is the head of my network as I
can see here some of these bars are green.
I can see all my network application
gateways are performing well.
On the other hand, I can see that some
of my extra circuits are showing right.
There's a health issue there,
so this allows me quickly to start
thinking about hey where my where
my problem be and start drilling
down and looking for issues.
Now the first thing or customer
will do when they come here is
that the water debug further.
So let's see if I click
on application gateway.
I suspect an issue there.
So I get this drill down of all of all the
application gateways that are in my network.
Oh, sure,
immediately I can see this entire
list application Gateways.
I can see critical metrics right up front.
So for an application gateway you
typically want to know your throughput
response status on the backends
failed failed requests if any,
and the unhealthy host count
from the back end.
So right at my fingertips,
I have these metrics available now.
It just doesn't stop there.
If you want to plug in application gateway,
you can click on this icon on the left
which opens up the dependencies you know.
What is the dependency view?
I've fixed the dependency view.
Now this dependency view isn't
under the hood.
Look at a particular resource.
No,
no,
this is the dependence of you for an
application gateway called Canary Net
3 update at the front end you can
see the front end IP configuration.
You can see the listeners,
the contract,
the rules and finally you can see
the back end VM Xen VMS connected.
So it's not just about the resource,
it's also the reset it's connected to
and that you need to look at when you
want to bug resource and all of these.
All of these are available here now
right away in the visualization I can
see how my back end VM's are unhealthy.
Julie tells me in a very
visual and intuitive fashion,
but hey,
this is where the problem is and I
can debug it so I can click through
repair that VM and then my application
gateway will be healthy again.
So we are building these topologies
for variety all resources
similarly, we have example would be now that
application get it was a single resource.
We've also built similar
topologies for virtual bands,
which is a resource of cross connect
connectivity across regions and clouds.
So you can see here how 1V1 is represented
by multiple firewall virtual hubs.
You have your connections,
you have your on Prem sites and in
this case all of them are healthy.
So this allows me to add a glance,
know what is the help of.
Not just resources, but also the
various resources connected to it.
Now, along with this function,
apologies that we presented.
If so, I want to know the root
cause I have at my disposal metric
workbooks that we pre built and
made available to customers.
Damn it, now normally these
metrics are available to customers,
but they have to write queries,
have to configure dashboards and
author author workbooks by themselves.
So we've got a step ahead and
made it accessible for them.
Then forget go so right here in
the application gateway workbook
you can see there's the status
of the application gateway.
You can see unhealthy holes at the back end.
You can look at throughput,
current connections,
CPU regulations,
all typical metrics at someone
who's debugging application
gateway would be interested in.
We've provided information about every
metric and group metrics by various tags.
So you have performance,
latency,
traffic back in building.
Yeah, sure, so this notion
of unhealthy is unhealthy,
something that is understood.
It's just that it's unavailable. Is it?
Mr Ping. What is unhealthy in the
context of some of these network devices?
So, uh, if you source defines its
health differently, but they remote
what is called resource health check.
In the case in the case of VMS,
I think it's more closer to
whether the VM is responding,
provision well or it's not responding to,
you know into Args.
OK, cool, thank you.
So you have a variety of resources
available and metrics available.
You can group and ready for you to go
and you with zero conflict you have
this deep look where you can explore
the all of these metrics and find
out the root cause of any issue and
without without learning how to set
up your dashboards or any metrics at all.
Going forward.
We also have,
so the next tab in networking
sites is the connectivity to.
As I mentioned,
one of four customers who are looking
over looking for connection connectivity,
connection configuration based
monitoring where they want to
set up agents they want to test.
Set up this across the network
and check connectivity in reality
that data is typically available
in connection monitor,
but we've aggregated that and shown it here.
What you're seeing on screen is a
set of tests whether sources are
virtual machines and the destinations
are virtual machines or URLs.
I've already filtered it so this
allows me to view all the tests.
And and their status is you can
immediately see the reachability status.
What test is running,
which port is it talking to?
An instant plan so I can see
what is the state of my network?
How is connectivity across it?
Should there be an issue here?
I will immediately see my test turning red.
I can click through and explore further.
What does that look like?
So have you explored these? Yeah.
So this is the data from connection monitor.
We're getting the checks fail
percentage getting which what was
the source and the destination of
this particular connectivity test.
And if I click through on it,
I can see it's it helps me debug
the issue as I can see here,
it tells me the exact NSG rule that
was causing this connectivity issue.
So right away I can pinpoint to a
particular root cause and understand
why my connectivity is frustrating.
So that is the experience
on the connectivity tab.
I need we have the traffic down
the traffic tab is oriented around
helping customers understand
their traffic monitoring coverage.
So two of our solutions are
for traffic monitoring.
Our energy flow logs and traffic
analytics in the day so you can see
where you have enabled traffic politics.
Direct monitoring which is by enabling
energy flows in traffic analytics.
And if you want you can drill
down to any particular region,
see your list of energies and enable
or disabled traffic monitoring on them.
This is a single glance.
You understand your traffic
monitoring coverage.
How did people do this? Before that,
they just run their own runbooks,
create their own runbooks,
run around in multiple places for
different places to find this information.
So, uh, the data,
so every tab that we're talking about
here in networking sites is actually an
independent product and experience in itself.
So if I just start with network health,
it's available.
It's available as signal,
which you can set alerts on if you want to.
If you the metrics are available,
but they are available only after
you query that you have to go
specifically to every resource,
write a query or configure some
charts and pin them to a dashboard,
and then they're available.
Or you can alternately configure workbooks,
so took a lot of help.
You have to.
Cool that learning curve and
then discover these metrics.
But be sure which are very essential to
your understanding of the resource itself,
so we've so we've gone ahead and created
these people to work for customers to
quickly discover this automatically.
Now if I talk about connectivity and traffic,
both of these solutions independent.
I existed independently,
but now they were to independence Aleutians.
They were not available in
the context of Azure Monitor.
They were not aggregated together,
so we're bringing all of that
experience together in networking site.
So any power, any issue of your network,
any part, facing troubles, any signal.
Is going to be aggregated here?
Wow, that's fantastic.
So this is 1 centralized console
for network monitoring.
For troubleshooting I really was
impressed with the creation of those.
Top apologies.
I don't have to draw those diagrams.
Those are created for me by
looking at my own network.
Yep, so that apologies really
enable you to visually give up.
So instead of you know.
So typically the flow that would happen
before this is that if I go back to the
example of the load balancer would be OK.
You'll get an alert saying my load balancers,
unhealthy debug it, and we're looking
at your flows through it and it's OK.
It looks fine. We could the issue
be or it must be one of them back.
It could be one of them.
Back in VMS is or would be my friend
and I be now I'll branch out and I'll be
debugging both of those and come back.
So we've tried to streamline that process.
Show all of this together.
Show all of them connected together.
An should help right away and so so that
you don't have to do all this manual
debugging and you can just visually
and very intuitively understand.
Find the root cause of fantastic
so this is available today.
I have this like I can hang up
the phone with you right now.
Go to Azure and I'm going to discover this.
I've already got this available and
customers can start monitoring right away.
Absolutely.
It's available G8 since December 2020.
It's available right away in the
portal and zero configuration needed.
Just click through and you're
and you're done.
That's fantastic and this is going to
be continually updated with new views
and new signals and new insights.
And I understand that if you click on
feedback it goes to real human beings
like yourself and the team does.
Read the feedback and is always
improving network insights.
Absolutely.
The two things I'd like to call up a
call out here is that we didn't want
to create another tool that tries to
become the tools that solves all tools.
This networking sites is available
right inside Azure Monitor.
It's the Network Insights tab
over there and you can switch
context seamlessly from application
monitoring so application monitoring,
debugging to network monitoring,
so no need to learn.
This works with the workbooks
framework that's already existing
for Azure Monitor in general.
And yes,
we will be continuously adding
new technologies and new signals.
And that's where you want customer feedback.
Any gaps that you highlight any
monitoring signals that you want,
or any feedback for the tool.
We'd like to hear from you.
And yeah, we're all yes, fantastic.
This is great.
Thank you so much for spending time
with me today. Thank you so much Scott.
This great talking to you.
Alright,
I am learning all about the great
new unified network monitoring
experience network insights inside
Azure Monitor today on Azure Friday.
Hey,
thanks for watching this episode of
Azure Friday. Now I need you to like it.
Comment on it, tell your friends, retweet it.
Watch more Azure Friday.