WEBVTT 00:00.510 --> 00:00.960 Excellent. 00:01.050 --> 00:06.840 So far, we have in flux DBI version to install, we have a telegraph collector collecting stats and 00:06.840 --> 00:12.060 sending it to influx Digby, and we can visualize that through the complexity without a source in Gravano. 00:12.120 --> 00:18.570 Now, like how we've set up other data sources in the past, you can have one main server such as Prometheus 00:18.570 --> 00:23.070 or Loki, and have many collectors or from Taylor, for example. 00:23.070 --> 00:27.600 For Prometheus, it's not exporters, and there are many other kinds of exporter's for Prometheus, 00:27.600 --> 00:33.390 not just not exporters or the Gryphon metrics, end point or any other endpoints that Prometheus can 00:33.390 --> 00:33.720 read. 00:33.720 --> 00:39.480 For Influx DB, we can have multiple telegraphs, so I can set up telegraph on my moskvy or server and 00:39.480 --> 00:46.830 pointed to either the VPC IP address of the influx DB or the external address, or I can have telegraphs 00:46.830 --> 00:50.280 on all the servers that I got access to or sending to Fox DB. 00:50.310 --> 00:54.010 Now I'm not going to show you how to do that in this video if you do want to ever do that. 00:54.030 --> 00:54.840 It's not that hard. 00:54.840 --> 00:59.940 You just copy the instructions that we use for the first telegraph that we installed, and you would 00:59.940 --> 01:06.450 configure the URL that you're sending the data to in your telegraph configuration there and whichever 01:06.450 --> 01:08.070 inputs you want to collect. 01:08.100 --> 01:11.250 So in this video, I'll be introducing you to S and MPD. 01:11.280 --> 01:13.250 OK, so there's no need for that. 01:13.260 --> 01:15.800 You can do that if you want to in your own time. 01:15.810 --> 01:18.270 But in this video, I'll introduce you to S&P now. 01:18.270 --> 01:24.600 SMP Simple Network Management Protocol is a protocol that's been around since before the internet went 01:24.600 --> 01:25.080 public. 01:25.140 --> 01:28.860 So it's very old and there's a lot of devices that still support it. 01:28.890 --> 01:36.180 Now it's useful in those cases where you can't install a service such as routers or switches or printers, 01:36.180 --> 01:39.210 or even servers and workstations can support SMP. 01:39.240 --> 01:44.580 You'll find a lot of hardware in corporate environments where you can't actually install Telegraph Electron 01:44.580 --> 01:46.970 to or we can't install prompter onto. 01:46.980 --> 01:48.390 It is not an operating system. 01:48.390 --> 01:52.260 We can do that, so those devices may provide data through an internet interface. 01:52.320 --> 01:57.120 Now also, since you properly don't have A. an MP device on your own network that you can use, I'll 01:57.120 --> 02:02.850 show you how to install an SMP daemon on Ubuntu twenty point zero four so that we can at least have 02:02.850 --> 02:03.810 some experience with it. 02:04.020 --> 02:10.200 OK, so I'm going to install the SNP daemon on the same server as my influx DB server. 02:10.260 --> 02:14.570 OK, so log on to your influx DB server and we'll install the SMP demon on it. 02:14.640 --> 02:14.950 OK. 02:14.970 --> 02:22.710 Some of my influx DB server, so install SMP, S&P Dow and S&P MIPS Down Downloader because we use all 02:22.710 --> 02:31.830 those right click to place and enter then yes, now I'm doing this just so that we can show S&P because 02:31.830 --> 02:35.430 you're very unlikely to have an actual S&P device on your network. 02:36.330 --> 02:40.560 So this way of doing it is more reproducible while you're learning, OK, so it's normally started when 02:40.560 --> 02:44.070 we've installed it so we can check it status active running. 02:44.100 --> 02:44.430 Excellent. 02:44.430 --> 02:52.200 OK, now we can do a simple test query, so copy that S&P Walke version to see the community is public. 02:52.200 --> 02:58.380 One two seven zero zero one So that's this computer dot means give me everything, and we got a lot 02:58.380 --> 02:59.880 of data being returned. 03:00.030 --> 03:04.460 Now, it's important to note that the data returned is showing our ID numbers. 03:04.470 --> 03:06.060 So this is one way it's shown. 03:06.060 --> 03:09.090 Also, those numbers equals a value. 03:09.150 --> 03:13.170 So as we say here, ISO equals data type in a value sometimes set. 03:13.170 --> 03:15.880 Why not say, Oh, sorry, that might say no one doesn't really matter. 03:15.900 --> 03:21.150 What's important is that when we continue to set up the Telegraph collector for S&P, it's going to 03:21.150 --> 03:27.000 be doing search on what's called MIPS and maybe stands for management information base, but maybe some 03:27.030 --> 03:29.520 other form of a string like that. 03:29.520 --> 03:34.500 And when we do the telegraph configuration, it will be looking up the string version. 03:34.950 --> 03:37.780 So same with this one and if table as well. 03:37.800 --> 03:42.330 So it's important to make sure MIPS work on your SMP daemon. 03:42.340 --> 03:49.260 So one way we can do that is to go into a file called SMP dot com, not as S&P dot com. 03:49.260 --> 03:54.390 So copy that ciudadano ADC, SMP, SMP, dconf into. 03:54.420 --> 03:57.510 Now scroll down and will comment at that line. 03:57.540 --> 03:58.620 So it's now hash. 03:58.740 --> 04:01.120 Maybe just comment to the tropics to save? 04:01.140 --> 04:01.680 Yes. 04:02.070 --> 04:04.350 Now if we do that same query again. 04:04.950 --> 04:09.270 Version two C. S. Public 127 zero zero one dot, which means everything. 04:09.360 --> 04:12.950 Each line showing the MAIB description no longer the numbers. 04:12.960 --> 04:18.020 So when we set up Telegraph, our configuration will be searching for map descriptions, for example. 04:18.030 --> 04:19.680 So and you can see that down here. 04:19.680 --> 04:24.720 So we're looking for information, maybe if description, so we can actually search one of those directly. 04:24.730 --> 04:26.050 So why just copy that? 04:26.070 --> 04:27.190 We'll see if that works. 04:27.220 --> 04:30.540 OK, so doing that query again, we'll get rid of that dot at the end. 04:30.720 --> 04:35.280 And if I just put in that whole query, press enter and returns what I'm looking for now. 04:35.310 --> 04:40.760 You can also just get rid of the RF C one two three bit there at the beginning to even do that. 04:40.770 --> 04:41.470 And it's the same. 04:41.490 --> 04:41.850 OK. 04:41.880 --> 04:44.760 That's just a little bit of information about SMP for you there. 04:44.760 --> 04:48.780 S&P's a very large subject, but I'm just showing you the beginnings to help me get started. 04:48.840 --> 04:52.890 OK, now let's open up our telegraph configuration like that. 04:52.890 --> 04:55.770 And if we just scroll down, look at the input section. 04:55.770 --> 04:59.220 So we have quite a few inputs already from the last videos. 04:59.640 --> 05:01.080 Another one for S&P. 05:01.230 --> 05:09.600 So copy, I've got there, so I want to copy that whole lot right click and it's just a minimal S&P 05:09.600 --> 05:11.340 input configuration there. 05:11.730 --> 05:17.970 That's the address that we checking one 27 zero zero one call one six one and it uses the UDP protocol. 05:18.000 --> 05:18.810 OK, so that's good. 05:18.810 --> 05:23.490 That's going to do some simple queries of the S&P Daymond that we just installed on our local server 05:23.490 --> 05:29.280 here, the Clucks DB server, and we'll be able to see that information first influx DB and then in 05:29.460 --> 05:30.060 Safana. 05:30.060 --> 05:31.900 So control X to save that. 05:31.930 --> 05:35.460 Yes, OK, so now to restart the telegraph service. 05:35.580 --> 05:45.360 So sudo service telegraph restart a status, then it looks pretty good so far. 05:45.540 --> 05:47.490 So any errors, I'll see. 05:47.540 --> 05:50.630 Now let's go into influx and see what we've got. 05:50.640 --> 05:53.210 So in your influx DB, go to explore. 05:53.220 --> 05:58.730 And if we look at this measurements section, we should start to see some S&P. 05:58.740 --> 06:02.670 There isn't much there at the moment, showing up as just the uptime, maybe. 06:02.790 --> 06:05.580 So I submit that it's showing uptime here. 06:05.640 --> 06:09.390 I look at the query there that's see sometimes coming from this name. 06:09.390 --> 06:11.210 Does uptime also in there? 06:11.220 --> 06:17.100 We have agent host, host and source source here has come up. 06:17.100 --> 06:19.290 It's a tag is tag equals true. 06:19.320 --> 06:22.490 So we can also use that the same as the host, really. 06:23.430 --> 06:25.040 But that is a table if you like. 06:25.050 --> 06:30.120 But anyway, we're not seeing any information yet for if table or if description. 06:30.120 --> 06:36.090 And the reason for that is because by default, when we install the S&P D on a but to the information 06:36.090 --> 06:38.670 S&P D will return is quite restricted. 06:38.670 --> 06:42.990 It's restricted to decides with that prefix or that prefix. 06:42.990 --> 06:48.360 What we'll need to do is change it so that it returns a larger range of our IDs. 06:48.360 --> 06:52.920 So very quickly, let's just try and search for maybe if table. 06:52.930 --> 06:58.950 So we could verify that it's not returning anything by typing that it's an empty table command version 06:58.950 --> 07:00.570 to see public local IP. 07:00.570 --> 07:07.170 If Table says no entries, so let's change the allowable ID prefix in the S&P Daymond configuration. 07:07.180 --> 07:12.420 So this time it's S&P D dot com until and if we scroll down. 07:14.500 --> 07:20.140 And we can see down here where it describes the view, we can comment at that line because it's not 07:20.140 --> 07:23.460 going to be necessary and just remove this last one. 07:23.470 --> 07:25.830 So control x, yes. 07:25.840 --> 07:33.160 And now to restart the S&P Demon Sudo service, it's an the restart. 07:33.160 --> 07:37.450 And now we'll for that query again if table and we get some data. 07:37.480 --> 07:43.600 Okay, so that means after the moment to the graph should have caught up and we'll start to see some 07:43.600 --> 07:51.970 more information on the interface in flux DB and we start to see all of those values being returned 07:51.970 --> 07:53.440 through if table there. 07:53.950 --> 08:00.580 So for just get rid of that good if description and if index we look at if description, we can look 08:00.580 --> 08:04.020 at each Ethernet device that our server has bound. 08:04.030 --> 08:05.950 So I'll just get rid of that submit. 08:06.020 --> 08:11.480 OK, so we can see that that if table query is now working inside the Telegraph, collect any information 08:11.480 --> 08:13.030 that's going to in flux DB. 08:13.060 --> 08:15.070 So if we just copy that script. 08:16.160 --> 08:21.470 They can put that into Carafano, so explore influx TB paste. 08:21.620 --> 08:24.410 Click out of that unsupported import type main. 08:24.440 --> 08:25.100 Doesn't matter. 08:25.110 --> 08:28.790 Let's just get rid of that one for now on query. 08:28.790 --> 08:29.590 And there we go. 08:29.600 --> 08:32.150 We start to see all the information coming through. 08:32.180 --> 08:38.930 We'll use this information in the next few videos to create a dashboard for S&P inside Gryphon. 08:39.110 --> 08:44.800 OK, so you should now be saying that S&P information inside Carafano or the influx daily data source 08:44.810 --> 08:46.750 now note how this has been set up. 08:46.760 --> 08:53.810 The S&P D is serving data that has been requested from Telegraph, so the Telegraph agent is periodically 08:53.810 --> 08:55.270 requesting data from it. 08:55.370 --> 08:55.940 They pay data. 08:56.090 --> 09:01.530 We can set up Telegraph to query multiple S&P Demons on different servers. 09:01.550 --> 09:08.270 So the next video of set up another is an MPD on my Moscow Agraféna server, so that we can see S&P 09:08.300 --> 09:12.980 data from multiple servers through the one telegraph because they will create a simple dashboard, Agraféna, 09:12.980 --> 09:14.420 where we can view all three servers. 09:14.810 --> 09:15.260 Excellent.