Okay, what have we learned in this lesson?
Well the first takeaway I have for you is that,
in my opinion, learning Kusto query language is not optional.
First of all, on just about all of the associate and expert cert exams,
you'll see some KQL code.
Now you won't be writing code on any of the Azure exams,
but you'll be asked to interpret code.
I also submit to you that knowing KQL and how to monitor using KQL
increases your value in your career as a Microsoft specialist.
This is because KQL is used not only in Log Analytics,
but within Azure Resource Manager itself,
all of your Azure inventory is surfaced in what's called Resource Graph,
and guess what's used to query Azure Resource Graph,
a variant of KQL.
Your application developers will want to use Application Insights.
Guess what's used to query that?
KQL.
Your security team is going to be using Azure Sentinel.
Guess what, you know all the rest.
I also want to give a shout out to Workbooks.
I submit they can greatly shorten your learning curve in terms of figuring
out what are the most important metrics to watch for,
not only Azure VMs, but also the other workloads that are supported in Insights,
whether it's containers or networks or databases or whatnot.
Now, what if your team needs to monitor Azure virtual networks,
but they aren't yet strong on networking?
First, I would say take heart.
Microsoft Azure support receives the majority of their support tickets
in the networking space because it's so complicated.
Second, I would say,
onboard your Azure virtual networks into the Azure
Networking Insights solution in Azure Monitor.
And third, I would say, you know me well enough,
this is a lead,
watch the next module study and it's called Troubleshooting Windows Server
Hybrid Networking where we'll get deeper into the subject.
Thank you for your participation.
I look forward to seeing you then. Happy studying.