1 00:00:00,090 --> 00:00:06,060 So provided we have the Prometheus data source set up, then we can query Prometheus, we can query 2 00:00:06,060 --> 00:00:10,830 two different kinds of jobs, such as Node and Prometheus. 3 00:00:10,920 --> 00:00:11,760 We can continue. 4 00:00:11,760 --> 00:00:17,750 It will install two dashboards in this video, one for the Prometheus service, which is that there 5 00:00:17,820 --> 00:00:22,620 that will tell us about the performance of the actual Prometheus service and a dashboard for the node 6 00:00:22,620 --> 00:00:23,170 exporter. 7 00:00:23,190 --> 00:00:24,050 And that is there. 8 00:00:24,120 --> 00:00:28,760 The node exporter is useful for telling us about the performance of our server as a whole. 9 00:00:28,770 --> 00:00:32,369 It will have many statistics that will be very useful to watch over time. 10 00:00:32,580 --> 00:00:37,290 Now we can install not exporters on many service and will do that in one of the next videos. 11 00:00:37,350 --> 00:00:39,930 A case, a guide to configuration data sources. 12 00:00:40,080 --> 00:00:46,050 Prometheus in dashboards here, our first dashboard will be this one Prometheus two sets we can import 13 00:00:46,050 --> 00:00:49,140 that don't install this Prometheus stats dashboard. 14 00:00:49,140 --> 00:00:52,540 That's for the older versions of Prometheus and Graphite. 15 00:00:52,540 --> 00:00:56,070 And Matrix won't actually work just yet, but we'll talk about that in the next video. 16 00:00:56,100 --> 00:00:57,780 But for now, that's all we need now. 17 00:00:57,780 --> 00:01:01,640 If we click that, it takes us straight to a Prometheus dashboard. 18 00:01:01,650 --> 00:01:07,050 If we were to look at any of the queries behind these visualizations here, you'll see that the job 19 00:01:07,050 --> 00:01:08,370 is Prometheus. 20 00:01:08,700 --> 00:01:17,460 If we look at another one job, Prometheus and Job Prometheus, this script duration is actually grouping 21 00:01:17,460 --> 00:01:18,050 by job. 22 00:01:18,550 --> 00:01:23,700 There are two jobs node and Prometheus, so already that is very good. 23 00:01:23,700 --> 00:01:28,950 We can see better performance of the Prometheus service and just a reminder what Prometheus is doing. 24 00:01:28,950 --> 00:01:35,370 Prometheus is requesting data from as many node exporters that you can connect to it. 25 00:01:35,430 --> 00:01:40,770 If I had 20 servers, I can install not export on each of those 20 servers and set up Prometheus to 26 00:01:40,770 --> 00:01:43,140 query the non export on each of those service. 27 00:01:43,140 --> 00:01:46,720 And we'd want to know how Prometheus was handling that. 28 00:01:46,740 --> 00:01:54,450 And that is a good graph to help you understand that, such as query durations and script durations. 29 00:01:54,570 --> 00:01:59,040 But anyway, next, we're going to create another dashboard for the exports that go to dashboards, 30 00:01:59,040 --> 00:02:00,150 manage Scott. 31 00:02:00,150 --> 00:02:04,740 Any changes if you want or save them, we're going to import another dashboard. 32 00:02:04,800 --> 00:02:07,920 So let's go and find the dashboard that we want. 33 00:02:08,009 --> 00:02:13,080 Looking at a documentation is a link to the graph found a dot com graphs out dashboards website so open 34 00:02:13,080 --> 00:02:17,570 that yeah, so zero gryphon a dot com bafana dashboards. 35 00:02:17,580 --> 00:02:21,840 And if we use the filters here, it will find a whole lot of dashboards that we want. 36 00:02:21,840 --> 00:02:27,660 But the particular dashboard that I want is one one two seven four and there's a link for there, OK? 37 00:02:27,720 --> 00:02:29,900 Node exporter for Prometheus dashboard. 38 00:02:29,910 --> 00:02:33,470 It's updated recently and you can read about it there anyway. 39 00:02:33,480 --> 00:02:38,610 All I want is the ID, which we already have now put that into the import load. 40 00:02:38,970 --> 00:02:41,280 OK, Note Explorer for Prometheus dashboard. 41 00:02:42,230 --> 00:02:45,500 Selected data source Prometheus and import. 42 00:02:45,950 --> 00:02:51,530 OK, so this is a very impressive dashboard, and this is telling us everything about our server and 43 00:02:51,530 --> 00:02:54,390 it's getting that information via the net exporter. 44 00:02:54,410 --> 00:02:57,620 So that's the net exporter there I've installed on my Gryphon a server. 45 00:02:57,650 --> 00:03:02,810 The Prometheus service is requesting data from the net exporter and making it available for the Prometheus 46 00:03:02,810 --> 00:03:03,500 data source. 47 00:03:03,590 --> 00:03:04,430 And that's what we're seeing. 48 00:03:04,640 --> 00:03:06,380 So there's plenty of information here. 49 00:03:06,720 --> 00:03:10,310 I have one note explorer configured in the Prometheus configuration. 50 00:03:10,310 --> 00:03:12,890 Someone is saying just that one for localist, not 100. 51 00:03:13,010 --> 00:03:18,770 I can actually just make that a bit smaller since I only have one server right now, but really good 52 00:03:18,770 --> 00:03:26,960 information we can say about the CPU, disk space, internet traffic through memory and some other graphs 53 00:03:27,290 --> 00:03:28,910 show the information slightly differently. 54 00:03:29,360 --> 00:03:32,630 TCP ins and outs, open file descriptors. 55 00:03:32,630 --> 00:03:37,880 It is all very good information if you want to look at the performance of your server as a whole, so 56 00:03:37,880 --> 00:03:39,800 you can still not export as many servers. 57 00:03:39,800 --> 00:03:45,050 And then once you've set up scrape targets in Prometheus, you'll have them here as new instances. 58 00:03:45,260 --> 00:03:51,200 OK, so the information that is being used in these visualizations is coming from the job node there. 59 00:03:51,350 --> 00:04:01,460 So if we go to explore or discard any changes and go to metrics browser job node, if I look down here, 60 00:04:01,550 --> 00:04:06,190 most of those metrics start with node for press Prometheus. 61 00:04:06,200 --> 00:04:08,270 Most of those metrics start with Prometheus. 62 00:04:08,420 --> 00:04:11,990 There are duplicates such as Prefixed with Go and a few others. 63 00:04:12,020 --> 00:04:17,779 But those two dashboards, not exporter, focuses mainly on the node exporter, and the Prometheus two 64 00:04:17,779 --> 00:04:20,870 stats focuses mainly on the Prometheus job. 65 00:04:21,050 --> 00:04:27,340 These things become very useful the more time your service is running, you can see anyway. 66 00:04:27,380 --> 00:04:33,410 In the next video, we'll set up a dashboard for the Gryphon US service, which is much like the Prometheus 67 00:04:33,410 --> 00:04:37,370 dashboard, but specific about Agraféna application as a whole. 68 00:04:37,470 --> 00:04:37,810 Excellent.