WEBVTT

0:00:02.980000 --> 0:00:07.580000
 In this video, I want to take a few minutes
 to talk about a really powerful

0:00:07.580000 --> 0:00:12.940000
 capability within Azure that is given
 to you not quite free, but at a

0:00:12.940000 --> 0:00:18.220000
 very low cost. In fact, mine tends to
 be free every month, but it is based

0:00:18.220000 --> 0:00:21.140000
 on utilization and that
 is log analytics.

0:00:21.140000 --> 0:00:24.040000
 And what we're going to talk about,
 we'll start out talking about what

0:00:24.040000 --> 0:00:26.840000
 log analytics is and I'll kind
 of wipe board that out.

0:00:26.840000 --> 0:00:32.040000
 And then we'll go into looking at log
 analytics data sources, how you

0:00:32.040000 --> 0:00:37.400000
 can configure those, what log analytics
 solutions are and why they matter.

0:00:37.400000 --> 0:00:42.860000
 And then I'm going to get into a demonstration
 of working with log analytics.

0:00:42.860000 --> 0:00:46.120000
 I'm going to use an existing log analytics
 that I've got collecting information

0:00:46.120000 --> 0:00:57.100000
 all the time so that we have
 something to work with.

0:00:57.100000 --> 0:01:04.800000
 And the idea behind log analytics is
 that we start out and I've got these

0:01:04.800000 --> 0:01:09.480000
 resources. And so I've got all these
 different resources within Azure.

0:01:09.480000 --> 0:01:12.720000
 And maybe I've got an
 Azure SQL database.

0:01:12.720000 --> 0:01:20.340000
 And maybe I've got a virtual machine, which
 is a little bit trickier actually.

0:01:20.340000 --> 0:01:29.940000
 And maybe I also have a, let's say, even
 a virtual network, just say Vnet.

0:01:29.940000 --> 0:01:37.880000
 And all of this is capturing some data,
 some diagnostics data, maybe some

0:01:37.880000 --> 0:01:39.900000
 performance data.

0:01:39.900000 --> 0:01:48.080000
 And all that can be kind
 of written out there.

0:01:48.080000 --> 0:01:51.300000
 But it's all separated data.

0:01:51.300000 --> 0:01:57.740000
 Right? And really what log analytics
 is, and log analytics predates what

0:01:57.740000 --> 0:01:59.120000
 is now Azure monitor.

0:01:59.120000 --> 0:02:01.740000
 And Azure monitor actually built
 on top of log analytics.

0:02:01.740000 --> 0:02:04.340000
 They're closely related, but
 not quite the same thing.

0:02:04.340000 --> 0:02:12.080000
 What log analytics does is it really
 gives us a centralized platform for

0:02:12.080000 --> 0:02:15.240000
 collecting and analytics.

0:02:15.240000 --> 0:02:18.600000
 There we go. For collecting
 all this log data.

0:02:18.600000 --> 0:02:23.360000
 So instead of all of these systems
 just reporting their data out, that

0:02:23.360000 --> 0:02:29.640000
 data is now getting reported in into
 what really becomes a data warehouse

0:02:29.640000 --> 0:02:33.880000
 solution. And that's really what, if you're
 a data person, what log analytics

0:02:33.880000 --> 0:02:37.400000
 is. Right? It's got this processor,
 all this data is going to come in.

0:02:37.400000 --> 0:02:40.180000
 It's going to come in through
 an API to the processor.

0:02:40.180000 --> 0:02:43.620000
 And then it's going to get written
 down into the database.

0:02:43.620000 --> 0:02:48.320000
 Now I'm talking about these
 as Azure resources.

0:02:48.320000 --> 0:02:54.700000
 But in reality, I could also have
 virtual machines running anywhere.

0:02:54.700000 --> 0:02:57.840000
 Because the way it works with virtual
 machines is there's actually an

0:02:57.840000 --> 0:03:01.300000
 agent that installs on
 your virtual machine.

0:03:01.300000 --> 0:03:06.900000
 And that agent communicates with and
 sends your data into log analytics,

0:03:06.900000 --> 0:03:09.720000
 which again in turn is going
 to store that data.

0:03:09.720000 --> 0:03:13.200000
 In addition to that, if you're using
 system center operation manager,

0:03:13.200000 --> 0:03:17.520000
 typically referred
 to as COM or SCOM.

0:03:17.520000 --> 0:03:22.800000
 You can also set up system center operations
 manager to report its data

0:03:22.800000 --> 0:03:23.760000
 to log analytics.

0:03:23.760000 --> 0:03:27.760000
 So any data coming into that from your
 on-prem environment can be sent

0:03:27.760000 --> 0:03:30.920000
 in and centralized and
 log analytics as well.

0:03:30.920000 --> 0:03:33.560000
 Now all of this data is coming in.


0:03:33.560000 --> 0:03:35.680000
 And how do we get this data out?

0:03:35.680000 --> 0:03:41.420000
 Well, the way we get this data
 out is by writing queries.

0:03:41.420000 --> 0:03:44.880000
 And log analytics has its
 own query language.

0:03:44.880000 --> 0:03:48.220000
 And I will tell you, the query language
 for log analytics is fairly complex.

0:03:48.220000 --> 0:03:53.000000
 Because if you think about it, the nature
 of data, the nature of log data

0:03:53.000000 --> 0:03:59.800000
 that's coming from SQL or a virtual machine
 or a VNet or from system center

0:03:59.800000 --> 0:04:01.040000
 operation manager.

0:04:01.040000 --> 0:04:04.020000
 That's going to have different data
 structure, different information.

0:04:04.020000 --> 0:04:07.720000
 And it's also collecting both diagnostic
 data as well as performance data.

0:04:07.720000 --> 0:04:11.380000
 So the query language itself can
 actually be fairly complex.

0:04:11.380000 --> 0:04:14.520000
 And we will talk about that query
 language in another video.

0:04:14.520000 --> 0:04:20.860000
 But to simplify your query, and so
 you don't have to learn this fairly

0:04:20.860000 --> 0:04:26.460000
 complex query language, we have
 these things called solutions.

0:04:26.460000 --> 0:04:34.520000
 And really the purpose of a solution
 is to present the information in

0:04:34.520000 --> 0:04:36.660000
 a more digestible format.

0:04:36.660000 --> 0:04:38.840000
 And we'll see examples of that.

0:04:38.840000 --> 0:04:42.820000
 So I can write my own queries, and
 I have an interface for doing that.

0:04:42.820000 --> 0:04:48.900000
 Or I can have solutions that are really
 using that query engine to retrieve

0:04:48.900000 --> 0:04:50.700000
 data and work with data.

0:04:50.700000 --> 0:04:53.540000
 I also have an API.

0:04:53.540000 --> 0:04:59.220000
 So I could have third party apps using
 the API to retrieve information

0:04:59.220000 --> 0:05:02.460000
 and process that information
 out of log analytics.

0:05:02.460000 --> 0:05:06.160000
 But big picture, that's
 what log analytics is.

0:05:06.160000 --> 0:05:09.080000
 Now, let's talk about
 how that works.

0:05:09.080000 --> 0:05:11.100000
 You can see there's kind
 of two sides to this.

0:05:11.100000 --> 0:05:14.820000
 There are sources and
 there are solutions.

0:05:14.820000 --> 0:05:15.860000
 So what do we have there?

0:05:15.860000 --> 0:05:19.940000
 Well, let's start out talking
 about log analytics solutions.

0:05:19.940000 --> 0:05:26.000000
 I've got a screen shot of the workspace
 data sources that are available

0:05:26.000000 --> 0:05:27.400000
 for log analytics.

0:05:27.400000 --> 0:05:28.680000
 And it's pretty straightforward.

0:05:28.680000 --> 0:05:31.760000
 I've got virtual machines, you
 can see storage account logs.

0:05:31.760000 --> 0:05:36.200000
 Although the storage account logs is
 not really the storage account logs.

0:05:36.200000 --> 0:05:40.920000
 It's data that's been sent to storage
 accounts and specifically really

0:05:40.920000 --> 0:05:42.760000
 primarily IIS data.

0:05:42.760000 --> 0:05:45.420000
 So that one gets a little
 bit of an asterisk.

0:05:45.420000 --> 0:05:50.360000
 The activity log and then any other
 Azure resources that you can assign

0:05:50.360000 --> 0:05:52.580000
 directly to a workspace.

0:05:52.580000 --> 0:05:58.100000
 Now, in addition to that, the relatively
 new diagnostic settings really

0:05:58.100000 --> 0:06:03.440000
 means that if I go into Azure monitor,
 and I go to diagnostics, anything

0:06:03.440000 --> 0:06:08.380000
 that shows up in the diagnostics tab
 of Azure monitor, I can actually

0:06:08.380000 --> 0:06:14.020000
 set that to forward its diagnostic and
 performance metrics to an instance

0:06:14.020000 --> 0:06:16.120000
 of log analytics.

0:06:16.120000 --> 0:06:18.240000
 I could also send it to
 event hub or to storage.

0:06:18.240000 --> 0:06:23.060000
 So I get this great kind of standardized
 way of sending information to

0:06:23.060000 --> 0:06:27.060000
 log analytics so that I can then compile
 it across resources and do some

0:06:27.060000 --> 0:06:28.620000
 really powerful things with it.

0:06:28.620000 --> 0:06:33.660000
 So those are different sources that I
 have available within log analytics.

0:06:33.660000 --> 0:06:41.860000
 Now, in addition to that, as I mentioned,
 we also have log analytics solutions.

0:06:41.860000 --> 0:06:43.960000
 And here's an example.

0:06:43.960000 --> 0:06:46.520000
 These are actually the log analytics
 solutions that I've got associated

0:06:46.520000 --> 0:06:51.080000
 with my primary log
 analytics workspace.

0:06:51.080000 --> 0:06:53.660000
 And that's what you call when you create
 log analytics, you're creating

0:06:53.660000 --> 0:07:01.140000
 a workspace. And I will tell you that
 I strongly recommend getting the

0:07:01.140000 --> 0:07:05.560000
 Azure activity logs solution for your
 log analytics workspace because

0:07:05.560000 --> 0:07:10.740000
 that's going to give you a great 20
,000 foot view of everything that's

0:07:10.740000 --> 0:07:15.200000
 going on within your log analytics
 environment, which ideally is going

0:07:15.200000 --> 0:07:18.020000
 to be your overall
 system environment.

0:07:18.020000 --> 0:07:19.520000
 But there's other things.

0:07:19.520000 --> 0:07:25.560000
 I've got SQL Server, I've got Key Vault
 Analytics, I've got Network Performance

0:07:25.560000 --> 0:07:29.220000
 Monitor, which I always keep up there
 and I end up deleting the things

0:07:29.220000 --> 0:07:31.220000
 for network security monitor.

0:07:31.220000 --> 0:07:33.140000
 But you have these different
 solutions.

0:07:33.140000 --> 0:07:36.720000
 And what they do is they
 produce this output.

0:07:36.720000 --> 0:07:39.700000
 And right away, this is what
 you get out of the box.

0:07:39.700000 --> 0:07:41.980000
 Now, you can go and do
 very complex things.

0:07:41.980000 --> 0:07:47.740000
 But for me, particularly this Azure
 activity log solution, it makes it

0:07:47.740000 --> 0:07:50.400000
 so easy right out of
 the box to use this.

0:07:50.400000 --> 0:07:55.020000
 And I can see that I've got, for example,
 I can see activity logs by status.

0:07:55.020000 --> 0:08:03.400000
 So I've got, in this case, 92.7 that
 started 92,000 of which, 92.7,000,

0:08:03.400000 --> 0:08:05.300000
 97,000 of which failed.

0:08:05.300000 --> 0:08:06.640000
 That's not good.

0:08:06.640000 --> 0:08:09.020000
 This is in the last seven days.

0:08:09.020000 --> 0:08:10.920000
 I can break those out.

0:08:10.920000 --> 0:08:17.780000
 I can see that the vast majority of
 my activity logs were for this INE

0:08:17.780000 --> 0:08:22.020000
 task e-grid, which I thankfully
 have today fixed.

0:08:22.020000 --> 0:08:26.260000
 I've got Microsoft Storage, which
 is really what all of those were.

0:08:26.260000 --> 0:08:28.160000
 Anyways, you get the idea, right?

0:08:28.160000 --> 0:08:31.720000
 So I can get this great quick view
 of what's going on within data.

0:08:31.720000 --> 0:08:34.180000
 And typically, I can
 drill down into that.

0:08:34.180000 --> 0:08:37.760000
 And so when it comes down
 to it, that's the idea.

0:08:37.760000 --> 0:08:41.720000
 You have this ability to collect data
 across a wide range of sources,

0:08:41.720000 --> 0:08:44.200000
 both within Azure and
 outside of Azure.

0:08:44.200000 --> 0:08:49.760000
 And you have a log language as well,
 a query language, as well as these

0:08:49.760000 --> 0:08:54.640000
 pre-built solutions that really help
 you to analyze and use that data.

0:08:54.640000 --> 0:08:59.120000
 And what I want to do now is I want to
 go ahead and I want to take a look,

0:08:59.120000 --> 0:09:00.940000
 really take a tour through
 log analytics.

0:09:00.940000 --> 0:09:04.560000
 So let's jump into log analytics.

0:09:04.560000 --> 0:09:13.280000
 Now, I have this from a previous demo
 on monitor, but we'll jump off of

0:09:13.280000 --> 0:09:17.420000
 that. And what I'm going to do is if
 I wanted to create a resource, if

0:09:17.420000 --> 0:09:21.140000
 I wanted to create a log analytics
 workspace, I could do that.

0:09:21.140000 --> 0:09:27.580000
 And I just type in log, log analytics, create,
 and it's pretty straightforward.

0:09:27.580000 --> 0:09:30.800000
 I'm not even going to
 bother creating this.

0:09:30.800000 --> 0:09:32.880000
 There's really nothing
 that special.

0:09:32.880000 --> 0:09:35.300000
 And even the pricing tier, which looks
 like there's something to do there,

0:09:35.300000 --> 0:09:38.680000
 there's only one pricing tier you can
 select now, at least at the time

0:09:38.680000 --> 0:09:40.320000
 of this recording.

0:09:40.320000 --> 0:09:42.760000
 So I can create a log
 analytics workspace.

0:09:42.760000 --> 0:09:45.220000
 Pretty simple. No big deal.

0:09:45.220000 --> 0:09:51.900000
 But I can also then go and take
 a look at my log analytics.

0:09:51.900000 --> 0:09:55.600000
 And I've got a few of these and I'm going
 to go into my primary log analytics

0:09:55.600000 --> 0:09:58.000000
 so we can take a tour of it.

0:09:58.000000 --> 0:10:02.380000
 In fact, let's get everything
 out of the way.

0:10:02.380000 --> 0:10:03.940000
 I'll put this up a little bit.

0:10:03.940000 --> 0:10:05.500000
 Not too much. There we go.

0:10:05.500000 --> 0:10:10.980000
 All right. Now, log analytics in and
 of itself, I go in to the activity

0:10:10.980000 --> 0:10:14.180000
 log. It looks like, okay, I don't
 have anything to show here.

0:10:14.180000 --> 0:10:18.020000
 This one's kind of interesting because
 this actually just goes and looks

0:10:18.020000 --> 0:10:20.660000
 at the resource group that
 has your log analytics.

0:10:20.660000 --> 0:10:27.100000
 And if I take that off, it's going
 to give me all of my logs, in this

0:10:27.100000 --> 0:10:29.200000
 case, over the last six hours.

0:10:29.200000 --> 0:10:33.440000
 So this is giving me not just the log
 analytics for this workspace, but

0:10:33.440000 --> 0:10:36.640000
 everything that is connected
 to this workspace.

0:10:36.640000 --> 0:10:42.640000
 The rest of the portions up here, access
 control, I am locks, being able

0:10:42.640000 --> 0:10:44.000000
 to export the template.

0:10:44.000000 --> 0:10:45.620000
 Those are all pretty standard.

0:10:45.620000 --> 0:10:48.020000
 Now, I'm going to get back
 to advanced settings.

0:10:48.020000 --> 0:10:53.180000
 But before I do, come down here
 to workspace data sources.

0:10:53.180000 --> 0:10:56.140000
 And I can view virtual machines.

0:10:56.140000 --> 0:10:59.580000
 And these are all of the virtual machines
 that are currently in my system

0:10:59.580000 --> 0:11:03.340000
 and whether or not they have been
 connected to this workspace.

0:11:03.340000 --> 0:11:09.300000
 It's actually pretty simple to connect
 and click on that and I can click

0:11:09.300000 --> 0:11:13.380000
 connect. Now, when I connect, what that's
 going to do is actually install

0:11:13.380000 --> 0:11:18.540000
 an extension that links that virtual
 machine up and it puts an agent on

0:11:18.540000 --> 0:11:23.820000
 that virtual machine and starts writing
 its log data into this log analytics

0:11:23.820000 --> 0:11:27.260000
 workspace. I can also set
 up storage account logs.

0:11:27.260000 --> 0:11:31.400000
 Now, I mentioned with storage account
 logs, it sounds like you can actually

0:11:31.400000 --> 0:11:33.200000
 set up logging for the
 storage account itself.

0:11:33.200000 --> 0:11:37.860000
 You can't. What the storage account
 log allows you to do is take data

0:11:37.860000 --> 0:11:46.020000
 that was captured to a storage account
 and then write that data, for example,

0:11:46.020000 --> 0:11:49.460000
 IIS logs into log analytics.

0:11:49.460000 --> 0:11:51.780000
 And you can see the different
 data types.

0:11:51.780000 --> 0:11:56.700000
 So if I have selected to write, for
 example, virtual machine logging to

0:11:56.700000 --> 0:12:00.220000
 a storage account, I can then pick that
 data up out of the storage account

0:12:00.220000 --> 0:12:03.020000
 and forwarded to log analytics.

0:12:03.020000 --> 0:12:05.860000
 So I don't want to make too big a deal
 of that, but that can be a little

0:12:05.860000 --> 0:12:09.460000
 bit misleading. When you see sources
 and you see storage accounts, you

0:12:09.460000 --> 0:12:11.440000
 think that might be for the
 storage account itself.

0:12:11.440000 --> 0:12:16.040000
 It's not. It's actually really fairly
 difficult to get storage account

0:12:16.040000 --> 0:12:18.280000
 logging into log analytics
 right now.

0:12:18.280000 --> 0:12:25.460000
 You have to do some logic app development
 or API development to do that.

0:12:25.460000 --> 0:12:27.300000
 Now, Azure Activity Log.

0:12:27.300000 --> 0:12:33.960000
 This is showing me all of my connected
 subscriptions and are all of my

0:12:33.960000 --> 0:12:37.180000
 subscriptions that are currently available
 that are currently tied to

0:12:37.180000 --> 0:12:41.820000
 my Azure AD tenant and whether
 or not they are connected.

0:12:41.820000 --> 0:12:44.640000
 What that does is it
 writes activity logs.

0:12:44.640000 --> 0:12:48.820000
 Simple as that. So my I need demonstrations,
 I need development and I

0:12:48.820000 --> 0:12:49.980000
 need production.

0:12:49.980000 --> 0:12:55.280000
 All of those are writing activity information
 into this log analytics

0:12:55.280000 --> 0:13:01.340000
 workspace. Now, I can also
 go to Azure resources.

0:13:01.340000 --> 0:13:06.260000
 Now, this used to be its own interface,
 but that's actually been moved

0:13:06.260000 --> 0:13:09.900000
 over to Azure Monitor.

0:13:09.900000 --> 0:13:17.300000
 And this is the analytics for Azure Monitor
 and I can just determine what

0:13:17.300000 --> 0:13:20.000000
 I want to write.

0:13:20.000000 --> 0:13:23.940000
 So, for example, I've got an network
 interface and I can add standard

0:13:23.940000 --> 0:13:29.180000
 diagnostic settings, including the ability
 to send this to a log analytics

0:13:29.180000 --> 0:13:31.640000
 workspace and what it
 is I want to send.

0:13:31.640000 --> 0:13:35.720000
 I'm not going to set this up because
 that is going to go away and then

0:13:35.720000 --> 0:13:40.060000
 it will just be clogging up and
 cluttering up my diagnostics.

0:13:40.060000 --> 0:13:45.800000
 But what's more important is you see
 that you have the ability and we'll

0:13:45.800000 --> 0:13:53.740000
 just refresh that to connect a wide
 range of resources into your Azure

0:13:53.740000 --> 0:14:01.780000
 log analytics. Now, I mentioned that
 there's also the advanced settings

0:14:01.780000 --> 0:14:04.500000
 and I'm going to go into that and there's
 a couple of reasons why this

0:14:04.500000 --> 0:14:09.420000
 is important. This is important for
 one reason because if I go to the

0:14:09.420000 --> 0:14:13.940000
 connected sources, what this will allow
 me to do is actually install the

0:14:13.940000 --> 0:14:17.800000
 agent on any windows
 or Linux computer.

0:14:17.800000 --> 0:14:22.640000
 And I can do this for machines that are
 in Azure as well as machines that

0:14:22.640000 --> 0:14:26.660000
 are not. And so I can just download
 the agent and that's literally just

0:14:26.660000 --> 0:14:30.020000
 a download and it downloads
 this setup file.

0:14:30.020000 --> 0:14:33.600000
 I'm not going to run it on this machine
 because this is a Windows 10 desktop.

0:14:33.600000 --> 0:14:35.120000
 It wouldn't work.

0:14:35.120000 --> 0:14:37.420000
 And then when you run through and
 install, it's pretty simple.

0:14:37.420000 --> 0:14:38.900000
 It's just an installation.

0:14:38.900000 --> 0:14:42.060000
 It's going to ask for a workspace ID,
 which is right here and it's going

0:14:42.060000 --> 0:14:46.800000
 to ask for a connection key so that
 it can connect to and write data to

0:14:46.800000 --> 0:14:49.740000
 your organization.

0:14:49.740000 --> 0:14:53.060000
 So I can do that for Windows
 Server and for Linux Server.

0:14:53.060000 --> 0:14:57.960000
 Now, Azure Storage, that really is
 no different than what I showed you

0:14:57.960000 --> 0:15:00.620000
 in the other environment.

0:15:00.620000 --> 0:15:06.280000
 So I can pull those directly from the
 log analytics now and system center.

0:15:06.280000 --> 0:15:10.440000
 If you're using system center operations
 manager, this will show you how

0:15:10.440000 --> 0:15:16.100000
 you can connect your management groups
 into the Azure environment.

0:15:16.100000 --> 0:15:18.720000
 I can set up the data
 that I'm collecting.

0:15:18.720000 --> 0:15:22.000000
 And again, this should look pretty familiar
 to what we just saw for storage.

0:15:22.000000 --> 0:15:24.820000
 So this is saying, okay, here's the
 information that I want to collect

0:15:24.820000 --> 0:15:26.540000
 off of virtual machines.

0:15:26.540000 --> 0:15:34.260000
 And then you can also set up groups
 that just allow you to manage for

0:15:34.260000 --> 0:15:36.580000
 groups for the purpose
 of search queries.

0:15:36.580000 --> 0:15:40.660000
 So if you've got a set of virtual machines,
 for example, that you want

0:15:40.660000 --> 0:15:45.580000
 to be really kind of queried as a group
 or potentially queried as a group,

0:15:45.580000 --> 0:15:47.480000
 that is computer groups.

0:15:47.480000 --> 0:15:50.300000
 So those are all the data sources.


0:15:50.300000 --> 0:15:52.920000
 Now, what about getting
 information out?

0:15:52.920000 --> 0:15:55.360000
 One way to get information out, and
 we're going to cover this in another

0:15:55.360000 --> 0:15:59.540000
 video, so I'm not going to go deep
 into it, is I have direct access to

0:15:59.540000 --> 0:16:02.080000
 write queries against the log.

0:16:02.080000 --> 0:16:06.500000
 Again, not going to do that right now,
 because what I want to do is focus

0:16:06.500000 --> 0:16:17.960000
 on solutions. And I'm going to pull up
 my summary page for this log analytics.

0:16:17.960000 --> 0:16:23.780000
 And I can see various solutions
 that I've already added.

0:16:23.780000 --> 0:16:26.960000
 And in fact, I can add
 other solutions.

0:16:26.960000 --> 0:16:34.720000
 So let's say that I wanted to go
 with activity log analytics.

0:16:34.720000 --> 0:16:38.140000
 That's a really cool add in
 that I said everybody needs.

0:16:38.140000 --> 0:16:39.360000
 And I can create that.

0:16:39.360000 --> 0:16:44.820000
 And what that's going to do is install
 that into my log analytics.

0:16:44.820000 --> 0:16:51.960000
 And so you can go and find and research
 different solutions that are available.

0:16:51.960000 --> 0:16:54.280000
 There's a number of solutions that
 you have their own interface.

0:16:54.280000 --> 0:16:59.640000
 Now it's just a filtered version of
 the standard marketplace interface,

0:16:59.640000 --> 0:17:04.940000
 which is fine. And what you can do for
 any one of these, and you'll notice

0:17:04.940000 --> 0:17:08.860000
 that most of these I really don't have
 anything going on with, but my

0:17:08.860000 --> 0:17:16.580000
 Azure activity logs, if I click that,
 I can see a nice visualization of

0:17:16.580000 --> 0:17:18.160000
 what's going on.

0:17:18.160000 --> 0:17:21.700000
 And as I mentioned right now, I've got
 quite a number of these that have

0:17:21.700000 --> 0:17:25.420000
 failed. I'm starting to climb up
 and get a few more that haven't.

0:17:25.420000 --> 0:17:33.000000
 So I have 92,000 that started, 91,000
 that failed, 4,000 that succeeded,

0:17:33.000000 --> 0:17:34.980000
 and five that were canceled.

0:17:34.980000 --> 0:17:36.140000
 And a few were accepted.

0:17:36.140000 --> 0:17:38.720000
 Now, if I go in, let's say I want to
 see what was canceled, because I

0:17:38.720000 --> 0:17:40.360000
 don't want to see the errors.

0:17:40.360000 --> 0:17:43.940000
 What it's going to do is it
 actually generates a query.

0:17:43.940000 --> 0:17:45.320000
 This is an example of a query.

0:17:45.320000 --> 0:17:47.200000
 And it gives me the details.

0:17:47.200000 --> 0:17:53.460000
 And I can say, okay, these are the
 actual requests that were canceled.

0:17:53.460000 --> 0:17:55.920000
 And I can go up and show
 that a little bit bigger.

0:17:55.920000 --> 0:17:58.480000
 And this gives me
 a lot of details.

0:17:58.480000 --> 0:18:02.680000
 For example, I can see that this was
 canceled, why it was canceled and

0:18:02.680000 --> 0:18:07.340000
 drilled down. This operation was preempted
 by a more recent operation.

0:18:07.340000 --> 0:18:09.860000
 I'm not even sure exactly
 what that was.

0:18:09.860000 --> 0:18:13.620000
 Oh, I was trying to
 write an extension.

0:18:13.620000 --> 0:18:16.220000
 I was probably trying to write an extension
 of something that was already

0:18:16.220000 --> 0:18:19.440000
 being deleted if I had to guess.

0:18:19.440000 --> 0:18:22.920000
 But that is what you
 can do with this.

0:18:22.920000 --> 0:18:26.540000
 And then again, I can also say, okay,
 what were all these failures?

0:18:26.540000 --> 0:18:31.200000
 I see I've got 182,000 that are
 associated with this INE task.

0:18:31.200000 --> 0:18:34.800000
 E-grid, this is going to be ugly.

0:18:34.800000 --> 0:18:36.580000
 And all of these, most
 of these errors.

0:18:36.580000 --> 0:18:37.220000
 Not quite all of them.

0:18:37.220000 --> 0:18:38.560000
 Some of them are information.

0:18:38.560000 --> 0:18:43.360000
 But I could jump down
 in and view my errors.

0:18:43.360000 --> 0:18:46.160000
 All right, and so I have this ability
 without having to write what can

0:18:46.160000 --> 0:18:48.100000
 be fairly complex queries.

0:18:48.100000 --> 0:18:52.200000
 I have this ability to just kind of
 jump down and see what's going on

0:18:52.200000 --> 0:18:56.640000
 through a nice standardized
 interface.

0:18:56.640000 --> 0:19:00.680000
 And again, you're not by any stretch
 limited to this, but it does give

0:19:00.680000 --> 0:19:06.000000
 you a nice way of seeing really
 exactly what's going on.

0:19:06.000000 --> 0:19:09.580000
 And I can jump down there, and that
 just gives me the same information

0:19:09.580000 --> 0:19:12.560000
 just in a tabular format.

0:19:12.560000 --> 0:19:17.640000
 So that, at the highest level, is
 really what Log Analytics is.

0:19:17.640000 --> 0:19:21.860000
 So we've talked about the fact that
 you're taking these disparate data

0:19:21.860000 --> 0:19:26.180000
 sources that are writing performance
 data and the writing analytics data

0:19:26.180000 --> 0:19:36.220000
 and diagnostic data.

0:19:36.220000 --> 0:19:39.680000
 And you're really taking all that data
 and you're centralizing it into

0:19:39.680000 --> 0:19:40.780000
 a data warehouse.

0:19:40.780000 --> 0:19:45.060000
 And then you have this ability to use
 various solutions, and you can,

0:19:45.060000 --> 0:19:48.420000
 by the way, create your own solutions
 as well, and you can even sell them.

0:19:48.420000 --> 0:19:52.320000
 But you have these solutions that are
 pulling that data out and really

0:19:52.320000 --> 0:19:56.020000
 making it digestible so you can look
 at it and make decisions and work

0:19:56.020000 --> 0:20:00.240000
 with that information really, if you
 will, on a global scale within your

