WEBVTT 00:00.330 --> 00:06.090 So let's look at the Gryphon, a Matrix Prometheus dashboard now to back into Agraféna configuration 00:06.090 --> 00:11.640 data sources, Prometheus dashboards, cofounder metrics, they import that. 00:11.790 --> 00:13.890 OK, so this is not going to work straight away. 00:13.920 --> 00:14.440 Let's look at it. 00:14.570 --> 00:16.380 OK, lots of things missing. 00:16.770 --> 00:24.660 If we look at one of the visualizations he is looking for, job equals Carafano just for the one. 00:25.110 --> 00:27.740 A job equals profile. 00:28.140 --> 00:30.000 OK, so we go to the Explore tab. 00:30.720 --> 00:33.780 Discard Prometheus Matrix browser. 00:33.810 --> 00:34.660 Look good job. 00:34.680 --> 00:39.480 We only have jobs for Node and Prometheus, so that dashboard needs a job. 00:39.480 --> 00:45.870 Mega-fauna now the Prometheus service and the node exporter both provide these endpoints that expose 00:45.870 --> 00:52.140 the metrics that these services are meant to expose or to show those so on your Bafana's server, you 00:52.140 --> 01:03.400 can view those so curl HTP Colon Slash Slash one two seven zero zero one colon 1990 slash metrics enter. 01:03.420 --> 01:08.940 That is a lot of information in that response, but that is the information that you will find when 01:08.940 --> 01:11.130 you query the Prometheus job. 01:11.280 --> 01:16.950 For example, if I scroll up, here's something Prometheus, TSB storage, block sports, I'll just 01:16.950 --> 01:18.910 highlight that so it copies it to the clipboard. 01:18.930 --> 01:24.660 Now, if I thought that into there, we could say that it is one of the things that we can see in Prometheus, 01:24.840 --> 01:25.890 and that's the value. 01:25.920 --> 01:28.850 So it's a key space value kind of set up. 01:28.880 --> 01:30.790 OK, so there's one for everything now. 01:30.790 --> 01:32.400 It's the same thing for Node. 01:32.460 --> 01:39.570 If I do a query on Port nine 100GB metrics, we're getting all the keys and the values for the node 01:39.570 --> 01:40.160 exporter. 01:40.180 --> 01:41.240 I just scroll up. 01:41.250 --> 01:45.480 There's some poor node node system, do you state or do a search for that? 01:45.510 --> 01:48.540 And we go in node system D unit state job node. 01:48.690 --> 01:54.750 So it just so happens that the Gryphon US server, when it's running, also exposes its own metrics 01:54.750 --> 01:59.940 endpoint and that is at Port 3000 slash metrics. 01:59.940 --> 02:00.450 And we go. 02:00.480 --> 02:05.670 So this is a whole lot of Gravano metric information that we can show in Prometheus. 02:05.670 --> 02:08.040 We'll create a new script target in Prometheus. 02:08.040 --> 02:10.890 It will also query this Carvana metrics endpoint. 02:11.040 --> 02:15.960 So we need to open up the Prometheus configuration file that is in the folder side. 02:16.230 --> 02:20.500 ATC Prometheus Ellis LRH. 02:20.530 --> 02:23.400 This is where Prometheus was installed at Prometheus. 02:23.430 --> 02:26.940 That Prometheus why IMO is the configuration space suit? 02:27.000 --> 02:28.710 I know Prometheus. 02:28.710 --> 02:30.870 Why HTML if we scroll down? 02:32.050 --> 02:39.070 Into this scrape configs section here, I'll just scroll further there to scrape configs with a job 02:39.070 --> 02:41.970 name Prometheus and another one job name. 02:42.020 --> 02:48.510 Note this is what we're saying to the Prometheus job is getting its information from local hosts 1990, 02:48.520 --> 02:51.440 and it's just doing a search for slash metrics. 02:51.460 --> 02:56.240 The node is getting its information from local 9100 slash metrics. 02:56.260 --> 03:01.510 So what you're going to do is create another job name for Gravano called Bafana that will take its information 03:01.510 --> 03:03.000 from local hosts 3000. 03:03.010 --> 03:07.180 So put your cursor at the bottom of that highlight just that job name there. 03:07.210 --> 03:11.200 Make sure all the white space is selected and we can put the cursor up. 03:11.290 --> 03:14.620 I can just add an extra space in their job name Bafana. 03:14.650 --> 03:18.340 Throw down static configs at thousand. 03:18.460 --> 03:18.940 Very good. 03:19.000 --> 03:22.600 Now you can delete those to comment lines if you want in nano. 03:22.660 --> 03:27.440 It is control, OK, and then control kigen that deletes lines, but that's optional. 03:27.460 --> 03:32.360 Anyway, it's not the job name Gravano, and the static config is local host 3000. 03:32.380 --> 03:39.610 That is the default port of Kafala when you first install it and is in the scrape config section in 03:39.610 --> 03:43.600 Prometheus Y.M.C.A. Control X to save gas to save the buffer. 03:43.690 --> 03:46.030 Press enter its restart Prometheus. 03:47.970 --> 03:49.440 Double check its status. 03:50.530 --> 03:53.360 I go that's running control C to get out of that. 03:53.380 --> 03:59.130 Now if I just refreshed this whole screen to rug click and press refresh and then I press metrics browser 03:59.170 --> 04:02.240 have jobs selected, we could see this new job for Bafana. 04:02.310 --> 04:09.190 OK, so if I go back into the dashboards now, dashboards manage grandfather metrics there. 04:10.100 --> 04:13.510 We're now starting to get data, so those queries are actually starting to work. 04:13.600 --> 04:16.320 I do a search for the last five minutes. 04:16.360 --> 04:17.740 We're getting most information. 04:18.030 --> 04:18.280 Have a look. 04:18.280 --> 04:20.230 What's wrong with hasty status codes? 04:20.730 --> 04:28.920 They so first thing hasty http request total and is replaced that with this text will be on my documentation. 04:28.930 --> 04:30.070 We now get a graph. 04:30.100 --> 04:35.440 So two things have changed in the later version that status code now has done to school between the 04:35.440 --> 04:42.490 two words and also that value is often a heist http request duration seconds second, some so we can 04:42.610 --> 04:43.960 apply that never go. 04:45.030 --> 04:51.210 We have a new graph which is showing the requests per second and the different status codes. 04:51.270 --> 04:53.130 Now we look at this one here. 04:53.140 --> 04:59.610 Prometheus Alerts Press eight added that it's no longer alerts, so delete that and let's just put a 04:59.610 --> 05:06.180 bracket open up and start typing alert and you'll get some things that it could be. 05:06.210 --> 05:09.300 Now I'm guessing that it's Gryffindor alerting active. 05:09.360 --> 05:11.880 Let's take a look out of that, and that looks right. 05:11.930 --> 05:14.100 There are zero alerts firing right now. 05:14.130 --> 05:15.420 OK, so apply that. 05:15.540 --> 05:16.560 Okay, so that works. 05:16.710 --> 05:23.450 Now the last one, most use handlers edit sort top K Handler page to request total. 05:23.460 --> 05:29.520 So once again change that HTP request total to Safana to be to the second. 05:30.090 --> 05:30.510 There we go. 05:30.510 --> 05:36.300 We start to see a table there now so we can also apply that never go because some information coming 05:36.300 --> 05:36.600 through. 05:36.690 --> 05:39.510 Now this is a very basic Griffon Up Metrics dashboard. 05:39.720 --> 05:43.970 If you search on official Gryffindor dashboard website, there might be other options to choose from. 05:43.980 --> 05:49.370 But anyway, let's just quickly what happens when you try to install a dashboard in Gravano Things? 05:49.380 --> 05:53.760 I look at work because of the later versions, so you have to apply a bit of guesswork and you just 05:53.760 --> 05:55.140 get better at that with experience. 05:55.140 --> 05:58.110 Anyway, save that overwrite anyway. 05:58.110 --> 06:01.980 The next video will install the Prometheus Not Explorer on our basketball server. 06:02.040 --> 06:02.490 Excellent.