WEBVTT 1 00:00.000 --> 00:03.860 To wrap up this set of videos regarding 40 analyzer and reports, I'd like to 2 00:03.860 --> 00:05.000 propose this scenario. 3 00:05.000 --> 00:06.000 And here it is. 4 00:06.000 --> 00:11.000 An executive has asked to see weekly reports for high bandwidth usage. 5 00:11.000 --> 00:13.000 Now, what exactly is high? 6 00:13.000 --> 00:16.000 We may need some additional context for that. 7 00:16.000 --> 00:19.760 Like is it over a certain threshold or is just the top, you know, you know, 8 00:19.760 --> 00:21.000 sites are being used as far as bandwidth. 9 00:21.000 --> 00:23.000 So we'd want to get some clarification on that. 10 00:23.000 --> 00:27.030 But what they want is that report weekly regarding high bandwidth usage 11 00:27.030 --> 00:30.000 including the categories and websites visited. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 11 00:27.030 --> 00:30.000 including the categories and websites visited. 12 00:30.000 --> 00:34.000 So my question isn't like, you know, exactly which reporter we're going to use 13 00:34.000 --> 00:35.000 or what we're going to create. 14 00:35.000 --> 00:40.000 My question is what approach should we use to make this happen for the exec? 15 00:40.000 --> 00:44.000 So all I can do is go ahead and pause the video now, give that some thought. 16 00:44.000 --> 00:47.180 And then when you have an idea of how we would approach that or some ideas how 17 00:47.180 --> 00:49.000 to approach it, click on and resume. 18 00:49.000 --> 00:51.000 And we'll take a look at this approach together. 19 00:52.000 --> 00:55.710 So to give the executive what they want, if they want to see, you know, for 20 00:55.710 --> 01:01.000 example, high bandwidth usage including the categories and websites visited, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 20 00:55.710 --> 01:01.000 example, high bandwidth usage including the categories and websites visited, 21 01:01.000 --> 01:06.290 the first thing I would recommend us doing is not trying to create custom 22 01:06.290 --> 01:07.000 reports. 23 01:07.000 --> 01:11.260 And not trying to create custom data sets and not trying to create custom 24 01:11.260 --> 01:15.800 charts, but rather look for a report that is very close to what the executive 25 01:15.800 --> 01:17.000 is asking for. 26 01:17.000 --> 01:21.240 So the first thing would be to go ahead and look for existing report or get one 27 01:21.240 --> 01:23.000 that's very close to that. 28 01:23.000 --> 01:25.000 And then we can clone it and tweak it. 29 01:25.000 --> 01:27.000 And then secondly, we could go ahead and schedule it. 30 01:27.000 --> 01:30.500 And then once we schedule it, we could also then take the next step of having WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 30 01:27.000 --> 01:30.500 And then once we schedule it, we could also then take the next step of having 31 01:30.500 --> 01:34.520 an email or place it on a server in the same location so that the executive 32 01:34.520 --> 01:36.000 could get to it very easily. 33 01:36.000 --> 01:39.310 We'd also want to be aware that if there's sensitive information included in 34 01:39.310 --> 01:42.500 the reports, we'd also want to be very careful on the distribution of that 35 01:42.500 --> 01:43.000 report. 36 01:43.000 --> 01:48.580 For example, we wouldn't want a competing company, for example, to get a report 37 01:48.580 --> 01:52.350 of, you know, things that are happening in our environment that may be problems 38 01:52.350 --> 01:53.000 or issues. 39 01:53.000 --> 01:54.000 We'd want to keep that fairly private. 40 01:54.000 --> 01:57.190 So following this approach, looking for a report that may work for us and 41 01:57.190 --> 02:01.160 scheduling it, let's go back to the 40 analyzer and see if we can get a very WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 41 01:57.190 --> 02:01.160 scheduling it, let's go back to the 40 analyzer and see if we can get a very 42 02:01.160 --> 02:02.000 close match. 43 02:02.000 --> 02:06.490 All right, so back at the 40 analyzer on the left hand side, we'll go to 44 02:06.490 --> 02:08.000 reports and report definitions. 45 02:08.000 --> 02:13.010 And let's see, they want high bandwidth usage. Let's just do a search for the 46 02:13.010 --> 02:15.000 word, hi, press enter. 47 02:15.000 --> 02:17.000 There we go. That looks like a good start. 48 02:17.000 --> 02:21.140 So high bandwidth application usage report, we can double click on that. In 49 02:21.140 --> 02:24.000 fact, let's just clone it and we can tweak it. 50 02:24.000 --> 02:27.000 So we'll right click on that report. We'll do a clone. 51 02:27.000 --> 02:32.000 And let's go ahead and call it our exact high bandwidth. No click on OK. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 51 02:27.000 --> 02:32.000 And let's go ahead and call it our exact high bandwidth. No click on OK. 52 02:32.000 --> 02:34.000 And then we can further edit it if we need to. 53 02:34.000 --> 02:38.000 All right, so they're asking for, he wants a weekly report. 54 02:38.000 --> 02:42.440 So the previous seven days sounds great. And for the time zone, I'm in the 55 02:42.440 --> 02:43.000 Pacific time zone. 56 02:43.000 --> 02:47.150 So that's what we'll base the report on as well. And then for devices, I'm 57 02:47.150 --> 02:49.000 going to include all 40 gate devices. 58 02:49.000 --> 02:52.350 So I can either specify and click on select. They're all selected or I can say 59 02:52.350 --> 02:54.000 all devices, either way is great. 60 02:54.000 --> 02:57.290 And then we can go ahead and schedule it. So if he wants it weekly, we can 61 02:57.290 --> 03:01.200 click right here on an able schedule and we'll do it once a week starting and WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 61 02:57.290 --> 03:01.200 click right here on an able schedule and we'll do it once a week starting and 62 03:01.200 --> 03:02.000 let's go ahead and start it. 63 03:02.000 --> 03:07.400 How about tomorrow at midnight? And because we scheduled it, it automatically 64 03:07.400 --> 03:08.000 did the auto cash for us. 65 03:08.000 --> 03:12.000 We can also set up an email server and then also, you know, deliver it. 66 03:12.000 --> 03:15.470 If we enable notification here and we can deliver it to the executive, you know 67 03:15.470 --> 03:17.000 , whenever that report runs. 68 03:17.000 --> 03:19.640 So because I don't have an email server set up, I'll go ahead and leave that 69 03:19.640 --> 03:20.000 off. 70 03:20.000 --> 03:23.370 And now that we've saved it, if we wanted to tweak it here, we could also click 71 03:23.370 --> 03:24.000 on editor. 72 03:24.000 --> 03:28.000 And here we can say, for example, summary for our exact. 73 03:28.000 --> 03:31.320 And then scrolling down is going to have these charts that are included and the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 73 03:28.000 --> 03:31.320 And then scrolling down is going to have these charts that are included and the 74 03:31.320 --> 03:33.000 text here and the font and so forth. 75 03:33.000 --> 03:37.000 So we'll click on apply and then we just let it go ahead and run. 76 03:37.000 --> 03:40.990 So here's our report right here currently is filtered with the word hi there 77 03:40.990 --> 03:44.310 and we'll right click on it and we'll just run it immediately right now by 78 03:44.310 --> 03:45.000 clicking on run report. 79 03:45.000 --> 03:48.430 And that's in the process of running. So we can also double click here and it's 80 03:48.430 --> 03:51.000 now showing us for the last seven days where that report has been run. 81 03:51.000 --> 03:58.000 So we just generated it. So it takes us a few moments here to go ahead and have 82 03:58.000 --> 03:58.000 that report created for us by 40 analyzer. 83 03:58.000 --> 04:02.200 So it'll show up right here in just a moment, unless I ran the wrong report. So WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 83 03:58.000 --> 04:02.200 So it'll show up right here in just a moment, unless I ran the wrong report. So 84 04:02.200 --> 04:04.000 let's go to other it is. 85 04:04.000 --> 04:07.770 I almost gave up on it. So there is right there. And once the format column 86 04:07.770 --> 04:12.490 here populates, we can click on the option, which we'll see, for example, HTML 87 04:12.490 --> 04:14.000 or PDF and take a look at that report. 88 04:14.000 --> 04:18.470 And that report is taking a while now because we had the caching enabled, it 89 04:18.470 --> 04:22.000 may not have had an opportunity yet to build that cache. 90 04:22.000 --> 04:27.410 So for subsequent runs of that report, it should be much, much faster. In fact, 91 04:27.410 --> 04:29.000 we'll test that here in a moment. 92 04:29.000 --> 04:33.090 So this one is still not ready yet. So once it's done, we could look at the WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 92 04:29.000 --> 04:33.090 So this one is still not ready yet. So once it's done, we could look at the 93 04:33.090 --> 04:38.000 diagnostics and identify how much stress or pressure the 40 analyzer was under. 94 04:38.000 --> 04:40.760 But again, the second time we run it, it should be much, much faster because 95 04:40.760 --> 04:43.000 most of that information is already going to be cached. 96 04:43.000 --> 04:47.000 In fact, while that's running, let's go ahead back to the dashboard and status. 97 04:47.000 --> 04:49.000 And it doesn't look too stressed here. 98 04:49.000 --> 04:52.280 So here on the log received monitor, that doesn't look too stressed. If we 99 04:52.280 --> 04:56.420 scroll down, here's disk I O, here's the information that came into the 40 100 04:56.420 --> 04:57.000 analyzer. 101 04:57.000 --> 05:01.360 And as it's inserting into the database, that looks okay. So if we go back to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 101 04:57.000 --> 05:01.360 And as it's inserting into the database, that looks okay. So if we go back to 102 05:01.360 --> 05:06.000 reports and generated reports, that one is still not ready yet. 103 05:06.000 --> 05:10.490 And that report has been a few minutes. It is not coming up. I'm going to go 104 05:10.490 --> 05:12.000 ahead and run the report one more time. 105 05:12.000 --> 05:15.000 Maybe he's had a fluke with that one. Let me go back to report definitions. 106 05:15.000 --> 05:19.090 Scroll down. There's our exact high bandwidth report. Let me just take a look 107 05:19.090 --> 05:20.000 at the details. 108 05:20.000 --> 05:24.270 Go to settings. It's supposed to run weekly. The caching is enabled. So I won't 109 05:24.270 --> 05:25.000 make any changes there. 110 05:25.000 --> 05:29.090 It's going to return. Let's right click and run the report one more time. So 111 05:29.090 --> 05:30.000 click on run report. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 111 05:29.090 --> 05:30.000 click on run report. 112 05:30.000 --> 05:34.280 It says it's running. We'll go back to generated reports. So this is the one 113 05:34.280 --> 05:38.000 previously and we should have a new printing report coming up as well here in a 114 05:38.000 --> 05:38.000 moment. 115 05:38.000 --> 05:41.230 And there's the second one right there. So hopefully here in a moment, ah, 116 05:41.230 --> 05:44.000 fantastic. So that other one, why did it take so long? 117 05:44.000 --> 05:48.000 Let's right click on it. And from the drop down, click on retrieve diagnostic. 118 05:48.000 --> 05:50.000 I'll save that to my downloads folder. 119 05:50.000 --> 05:53.600 Let me open that up in a text editor and let's take a look. That's 39 charts. 120 05:53.600 --> 05:57.000 AutoCached is enabled as far as the system status. 121 05:57.000 --> 06:00.350 It didn't look like the CPU is too stressed or memory. We had plenty of disk WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 121 05:57.000 --> 06:00.350 It didn't look like the CPU is too stressed or memory. We had plenty of disk 122 06:00.350 --> 06:01.000 space. 123 06:01.000 --> 06:04.600 On here, it looks like it was building the cache for two log tables. And that's 124 06:04.600 --> 06:06.000 because I just created the report. 125 06:06.000 --> 06:10.260 It hadn't had time yet to go ahead and build those caches. Maybe the caches 126 06:10.260 --> 06:12.000 weren't all ready to go. 127 06:12.000 --> 06:15.120 And that's why this one kind of had a problem. But this one, which is the 128 06:15.120 --> 06:17.000 second one we ran, it ran pretty quickly. 129 06:17.000 --> 06:20.550 So does it test? I'm going to take this one that never completed, right click 130 06:20.550 --> 06:22.000 on it and say I want to delete it. 131 06:22.000 --> 06:26.020 Click on OK. And now that everything should be cached, let me run that same 132 06:26.020 --> 06:27.000 report again. 133 06:27.000 --> 06:30.180 So go back to report definitions. We'll go to our exact high bandwidth report, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 133 06:27.000 --> 06:30.180 So go back to report definitions. We'll go to our exact high bandwidth report, 134 06:30.180 --> 06:34.000 right click on it, click on run, and then we'll go back to reports. 135 06:34.000 --> 06:37.920 And here it is. And if the caches are all populated, that should be done a lot 136 06:37.920 --> 06:39.000 faster and it is. 137 06:39.000 --> 06:42.540 All right. So it's just a matter of the initial cache is being populated. And 138 06:42.540 --> 06:45.000 that second one ran very, very quickly. 139 06:45.000 --> 06:49.220 Click on the HTML here that'll open up a new tab. And here is our summary for 140 06:49.220 --> 06:55.000 our exec, including 54 applications, six categories, 1.19 gig total bytes. 141 06:55.000 --> 06:59.000 So here's one of our charts here with the application categories by bandwidth. 142 06:59.000 --> 07:02.000 So updates, 277 megabytes. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 142 06:59.000 --> 07:02.000 So updates, 277 megabytes. 143 07:02.000 --> 07:05.560 And that's because a few minutes ago, I just did some updates and lots of web 144 07:05.560 --> 07:08.000 browsers on a few of my clients to generate some traffic. 145 07:08.000 --> 07:11.950 So if we scroll down, looks like there wasn't a lot of harmful apps like point 146 07:11.950 --> 07:15.000 to point applications or file sharing applications. 147 07:15.000 --> 07:19.000 If we scroll down here, here's another chart for video and audio applications, 148 07:19.000 --> 07:22.710 which includes mostly, it looks like Netflix traffic, but continue to scroll 149 07:22.710 --> 07:23.000 down. 150 07:23.000 --> 07:27.100 Here's the top 10 video slash audio users by session. And then here's a another 151 07:27.100 --> 07:30.350 chart in a table form here at the bottom showing that most of the traffic was WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 151 07:27.100 --> 07:30.350 chart in a table form here at the bottom showing that most of the traffic was 152 07:30.350 --> 07:31.000 Netflix. 153 07:31.000 --> 07:35.410 So back at our scenario, it'd be wise to find a report that's already similar 154 07:35.410 --> 07:40.380 to what we need and just tweak it as needed, as opposed to creating our own 155 07:40.380 --> 07:44.000 custom data sets or custom charts or custom templates. 156 07:44.000 --> 07:47.190 Because very likely, we're going to have some reports out of the hundreds that 157 07:47.190 --> 07:49.000 are available that will serve our needs. 158 07:49.000 --> 07:52.410 And again, if we need a little tweaking, we can simply clone one of those 159 07:52.410 --> 07:56.000 reports, tweak it as needed, and then schedule it to run whenever we need it. 160 07:56.000 --> 07:59.430 So thanks for joining me in this set of videos regarding 40 Analyzer and 161 07:59.430 --> 08:03.010 reports, and I look forward to seeing you, my friend, in another set of videos WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 161 07:59.430 --> 08:03.010 reports, and I look forward to seeing you, my friend, in another set of videos 162 08:03.010 --> 08:04.000 very, very soon. 163 08:04.000 --> 08:09.080 Until then, I hope this has been informative, and I'd like to thank you for 164 08:09.080 --> 08:10.000 viewing.