WEBVTT 00:00.120 --> 00:00.690 Okay. 00:00.700 --> 00:06.390 So now we'll set up the easiest data source, but just be careful of this one because we look at the 00:06.390 --> 00:07.800 settings already. 00:07.800 --> 00:09.960 We've got 2000 active series now. 00:09.960 --> 00:11.760 We haven't really done much yet. 00:11.820 --> 00:13.380 Who thousand is quite high already. 00:13.380 --> 00:19.350 Looking at the free tier, you get 10,000 metrics in a free tier, you'll very easily go over 10,000 00:19.350 --> 00:19.800 metrics. 00:19.800 --> 00:21.900 If you don't set this up the way I do. 00:21.930 --> 00:29.190 Justin is trying out face okay, so into your account interface on the final labs, there's the Prometheus 00:29.280 --> 00:30.600 data source settings here. 00:30.720 --> 00:31.740 Let's look at the details. 00:32.340 --> 00:32.910 Okay. 00:32.910 --> 00:36.090 So once again, my information will be different than yours. 00:36.150 --> 00:37.890 What were we looking at this time? 00:37.980 --> 00:39.960 Is the remote right. 00:39.960 --> 00:41.460 And point is that one there? 00:41.580 --> 00:43.850 So we'll have our existing Prometheus service. 00:43.870 --> 00:46.480 This reminder of what that looks like on the diagram. 00:46.480 --> 00:52.170 We have installed a Prometheus service which happens to be on the same service on US server, but it 00:52.170 --> 00:55.500 could be any way you like and it's querying a local not exporter. 00:55.890 --> 01:00.870 And I set up an order exporter as well that it's also querying so that Prometheus service has its own 01:00.870 --> 01:01.650 user interface. 01:01.650 --> 01:07.800 It's a standalone system, but we've set up a Prometheus data source in Jafar that will also read that 01:07.800 --> 01:08.820 Prometheus data. 01:08.850 --> 01:10.880 Okay, so what we do this time, isn't that right? 01:10.920 --> 01:12.840 URL that is just here. 01:13.410 --> 01:19.170 We'll set up Prometheus to push data to this Prometheus data source here in microphone, a cloud version. 01:19.350 --> 01:19.620 Okay. 01:19.620 --> 01:24.960 So the Prometheus service there will still exist, but while we can still read it if we want to through 01:24.960 --> 01:30.240 our California server, the Prometheus service will be pushing all its data that it knows about to a 01:30.240 --> 01:34.110 Prometheus data source existing on microphone, a cloud instance. 01:34.200 --> 01:38.280 Okay, so back in here again, we need to generate a key also for this one. 01:38.280 --> 01:45.680 So generate right now I'm going to call it may see a show and it's a matrix publisher again so API. 01:45.680 --> 01:51.300 Okay so I can close that remember my case will change once our our place at the end of the video was 01:51.300 --> 01:54.480 something that is actually secret and you shouldn't share your live ones either. 01:54.930 --> 01:55.380 Okay. 01:55.410 --> 02:00.330 We have a new node we need to add for Prometheus config, which is this remote right option here. 02:00.330 --> 02:02.820 So open up your Prometheus configuration. 02:02.820 --> 02:09.930 So I'm on my server where I have my Prometheus service installed and running, so I'm going to see the 02:09.960 --> 02:13.830 UTC makes this and there it is Prometheus. 02:13.830 --> 02:15.390 Why I'm I'm going to edit that so. 02:17.550 --> 02:18.060 Okay. 02:18.180 --> 02:23.400 So this is the Prometheus voicemail as was set up in the course so far. 02:24.800 --> 02:29.150 It has three scrape config, says the first one being from atheists. 02:29.810 --> 02:35.720 There's only one job name node and I actually set up several other targets, but I've commented about 02:35.720 --> 02:36.770 four now in this job. 02:36.770 --> 02:37.520 Name Raphinha. 02:37.610 --> 02:40.370 Okay, so that's the end of that file. 02:40.370 --> 02:41.930 And copy this remote. 02:41.930 --> 02:42.350 Right. 02:43.100 --> 02:43.950 And put that in. 02:43.970 --> 02:44.600 Right click. 02:44.630 --> 02:45.070 There we go. 02:45.080 --> 02:49.010 And that is added with the correct URL, the correct name and key. 02:49.020 --> 02:50.470 Now for saving. 02:50.480 --> 02:56.660 Just so that we don't go over the metrics limit, we should comment about this scrape target. 02:57.500 --> 02:58.400 Also. 02:59.350 --> 03:02.050 The default Prometheus scrape target. 03:03.620 --> 03:08.480 So that you've only got one scraped target and figured there go targets localhost nine 100. 03:08.540 --> 03:11.880 This is so that we don't go over the 10,000 k metrics limit. 03:11.900 --> 03:15.810 You'll see that just even one node exporter will push that number very high. 03:15.830 --> 03:18.500 So now I control X to save that. 03:18.500 --> 03:19.040 Yes. 03:19.330 --> 03:22.130 And so now let's restart Prometheus. 03:24.300 --> 03:27.030 And ticket status looks good. 03:28.000 --> 03:32.710 Now, going back to your main page here, this number will go up in a moment. 03:32.770 --> 03:40.370 But if we go to immigration data sources and we look at the final cloud B code from the information 03:40.370 --> 03:44.890 information's already configured, the data sources was added automatically and is put in the correct 03:44.890 --> 03:45.940 username key. 03:45.940 --> 03:47.680 It's called password here for us. 03:47.740 --> 03:48.050 Okay. 03:48.100 --> 03:49.060 So that is good. 03:49.180 --> 03:51.370 So test that data source is working. 03:51.370 --> 03:52.370 That's important. 03:52.390 --> 03:54.380 Dashboard for note exporters now. 03:54.400 --> 03:58.510 So dashboards browse will import. 03:59.690 --> 04:05.220 And from my documentation this not export a dashboard was it a11074? 04:05.240 --> 04:07.170 So I stopped that in there. 04:07.190 --> 04:09.800 11074. 04:09.950 --> 04:10.980 Like that. 04:11.000 --> 04:11.330 Okay. 04:11.360 --> 04:17.000 Note export of information general metrics like the data source being rom and import. 04:17.850 --> 04:21.390 Very good and it seems to be working so far. 04:21.810 --> 04:24.120 After more time, there'll be more to look at as found. 04:24.120 --> 04:25.250 Localhost, not 100. 04:25.260 --> 04:31.770 That's my only scraped target that I have running on my Prometheus server so that for the last five 04:32.430 --> 04:34.440 we'll see some more data in a moment. 04:34.440 --> 04:36.690 But anyway, you can see that's looking pretty well. 04:36.690 --> 04:41.970 And going back to the dashboard there, these numbers have been updated just yet, but do be careful 04:41.970 --> 04:45.940 that they will update and that will probably be about 5000 metrics already. 04:45.960 --> 04:46.290 Okay. 04:46.290 --> 04:52.230 So just to show what I did using the diagram, I added that remote write parameter so that my existing 04:52.230 --> 04:59.280 Prometheus server sold server is pushing a copy of all its data off to my atheist data source or microphone, 04:59.280 --> 05:00.440 a cloud instance. 05:00.450 --> 05:04.620 So once again, you might prefer to use your phone in this way where you haven't managed to find a cloud 05:04.620 --> 05:11.280 account but be aware that it is quite expensive versus what I've shown in the course where I just set 05:11.280 --> 05:14.430 up it manually on the cheapest installation server I can get. 05:14.520 --> 05:19.650 And also I prefer to do all these things manually like management, firewalls, etc. but anyway, cloud 05:19.650 --> 05:20.910 is option for you. 05:20.970 --> 05:21.450 Excellent. 05:21.450 --> 05:24.180 And also go back into your Carvana account page. 05:24.180 --> 05:27.180 I'm looking at my SB code cloud information here. 05:27.180 --> 05:32.730 You can see now the current usage is 3808 matrix full Prometheus. 05:32.730 --> 05:34.980 That's my low key kilobytes an hour. 05:35.010 --> 05:39.810 So you can monitor that here as well as for this refresh that has not loaded yet, but it will mean 05:39.900 --> 05:42.870 that's an introduction to provide a cloud in case you want to do that. 05:43.050 --> 05:43.440 Excellent.