WEBVTT 00:00.150 --> 00:03.150 OK, so in this video, I'll add another S&P agent. 00:03.180 --> 00:08.100 This one will be external when you connect to an external S&P agent doesn't matter whether you're using 00:08.130 --> 00:13.680 telegraph warning system, there are a few extra considerations about connectivity, so I'll solve those 00:13.680 --> 00:14.200 in this video. 00:14.220 --> 00:20.270 So I'm going to log onto my my SQL server, and that's where I'm going to set up another S&P daemon. 00:20.300 --> 00:25.320 OK, so I'm on my MySchool server, and now I'm going to install this and MVPD. 00:25.590 --> 00:32.670 Now I'm only installing S&P D, not the S&P or S&P MIPS loader from the other lesson. 00:32.940 --> 00:37.050 That's because I don't also need to enable MIPS on this other S&P Daymond. 00:37.080 --> 00:44.160 The MIPS translation from allied to the MIPS descriptions happens on the server that is actually making 00:44.160 --> 00:44.790 the request. 00:44.940 --> 00:49.860 The server that is running S&P walk away as an empty table or any of those other S&P commands. 00:49.870 --> 00:52.380 So I only need a stampede because this will return. 00:52.380 --> 00:58.590 The raw stampede data and the translation to MIPS will happen on the Telegraph Influx DB server, where 00:58.590 --> 00:59.970 MIPS has already been installed. 01:02.250 --> 01:08.250 OK, I now need to configure the S&P DX configuration, so S&P decode. 01:08.490 --> 01:14.780 OK, so go downwards until we find the agent address here. 01:14.790 --> 01:19.530 So comment that out and will replace it with this here. 01:19.560 --> 01:21.480 UDP call one six one. 01:22.530 --> 01:28.950 Now, by default, the S&P dateline the story, but to only binds to the local one 27 zero zero one 01:28.980 --> 01:31.290 address on IP born IP six. 01:31.290 --> 01:35.520 I'm not using IPv6, so it doesn't really matter at all about any IP. 01:35.520 --> 01:38.540 The six settings I happen is server agent address. 01:38.550 --> 01:44.880 It's now just binding UDP one six one will bind to zero zero zero zero, so all Ethernet devices banned 01:44.880 --> 01:47.250 on this actual server will be able to get poor. 01:47.250 --> 01:49.170 One six one a woman who's the firewall? 01:49.230 --> 01:55.530 OK, I'm also going to increase the range of wide prefixes that this server will return. 01:55.560 --> 01:56.820 OK, so going down? 01:57.300 --> 02:03.930 OK, so this server will now turn anything with that prefix, which also happens to include that. 02:03.930 --> 02:06.210 So you can actually comment that line out now. 02:06.230 --> 02:10.590 Remember, the Eve table information is actually prefixed with that void. 02:10.800 --> 02:17.460 So in order to allow our server to return that ID plus the one plus everything else, we can just do 02:17.460 --> 02:17.740 that. 02:17.790 --> 02:18.160 OK. 02:18.180 --> 02:24.200 So control to say yes, enter and we can restart the S&P D service. 02:24.210 --> 02:29.480 Also, if you don't have a firewall, there's some IP tables information there that you can refer to. 02:29.490 --> 02:33.180 I'm going to use a firewall anyway, so it's an MPD restart. 02:33.270 --> 02:41.040 OK, so now we can go back onto our influx DB server and we'll try and do a request of the S&P daemon 02:41.040 --> 02:42.720 running on my Mos crossover. 02:42.840 --> 02:45.030 OK, some of my influx DB server. 02:45.030 --> 02:47.100 OK, so I'm just going to copy that command. 02:47.730 --> 02:54.650 I put that in and it's going to replace that section with the VPC IP address of my master server. 02:54.660 --> 02:57.940 So that's the virtual private network address. 02:58.110 --> 03:02.780 If I look at digital ocean, that IP address is 10 one three three three four. 03:03.250 --> 03:04.560 I was a place the. 03:04.590 --> 03:06.480 Now this is not going to work straight away, OK? 03:06.510 --> 03:10.950 That's because on that actual server, my mosque, your server, I have a firewall set up. 03:11.130 --> 03:14.250 So if I go to my firewall settings, my skill? 03:14.250 --> 03:19.920 Yeah, I will create a new rule custom UDP one six one. 03:19.980 --> 03:25.740 I'm going to remove those rules and add the IP address of my influx DB. 03:25.770 --> 03:30.030 That's where I'm making the request from my copy that so paste that into. 03:30.210 --> 03:31.200 OK, save. 03:32.550 --> 03:37.720 All right, so UDP requests to put one six one from that server should now be allowed to back on my 03:37.720 --> 03:39.320 influx DB server. 03:39.490 --> 03:40.240 Run that again. 03:40.270 --> 03:47.200 I get a response and we can see that despite the fact that I didn't install S&P or the MIPS loader on 03:47.200 --> 03:50.670 my MySchool server, I'm still getting MIPS descriptions. 03:50.710 --> 03:53.530 That's because the translation happens on this server. 03:53.560 --> 03:54.550 It's not that important. 03:54.580 --> 03:58.720 No, that doesn't matter if you don't understand what I'm actually talking about, there is just if 03:58.720 --> 04:03.400 you do a lot of work with this and it's good to know what's necessary and what isn't. 04:03.610 --> 04:09.660 Now I'm going to go into the telegraphed configuration and add the agent information for my Mos Cable 04:09.670 --> 04:11.120 as an MPD service. 04:11.210 --> 04:12.400 So clear. 04:13.240 --> 04:19.240 Sudo Nano, ATC Telegraph, Telegraph, dot com. 04:19.360 --> 04:20.200 And so OK. 04:20.200 --> 04:26.170 So scroll down to We Get to the Inputs S&P section here, and agents will add another agent to Pol. 04:26.180 --> 04:33.010 So UDP slash slash the IP address of my Moscow server. 04:33.010 --> 04:35.410 I'm using the internal private IP. 04:35.410 --> 04:39.490 So 10 one three three zero four there and do that. 04:39.700 --> 04:46.210 OK, so the input system is now making requests to two different S&P demons on different servers. 04:46.240 --> 04:50.200 One local and one across the network control x yes. 04:50.290 --> 04:58.330 Sudo Service Telegraph, restart intel and check the status for any errors. 04:58.630 --> 05:00.910 I don't see anything control. 05:00.910 --> 05:02.950 So you get out of that now an influx DB. 05:02.980 --> 05:11.110 Go to the Explore tab and we should start to see some S&P data for the other service s in MP. 05:11.230 --> 05:15.550 They would go its uptime and it's showing me both IP addresses. 05:15.730 --> 05:18.580 That's my Moscow server and that's the local. 05:18.580 --> 05:22.780 If I submit now, we can see two lines being drawn there. 05:22.810 --> 05:25.780 So look at the source there Moscow and Influx DB. 05:25.900 --> 05:30.490 So the hostname is already coming through and that's in the source property there. 05:30.520 --> 05:36.820 So if I just move that sideways a little bit and then select source, we see the names of this service 05:37.450 --> 05:39.430 and also do that the source. 05:40.490 --> 05:47.540 So I will look at Moscow will both makes sense, so that means we can read that in an hour or so. 05:47.550 --> 05:48.800 So script editor? 05:49.730 --> 05:50.270 Copy that. 05:50.500 --> 05:53.360 OK, Explore tab influx, Debbie Paste. 05:54.050 --> 05:54.470 All right. 05:54.620 --> 05:55.430 There we go. 05:56.180 --> 05:58.310 We'll just zoom into that section. 05:58.590 --> 06:01.130 If we go, we can see the data for both my service. 06:02.220 --> 06:05.520 Coming through, look at the table there, I can see this a new row. 06:06.560 --> 06:10.730 Anyway, in the next videos, we'll create a dashboard to read this Gravano. 06:10.760 --> 06:16.310 I'm going to do the same process with my Agraféna server, though I did with the MySchool, so that 06:16.310 --> 06:18.610 I'm getting data from three S and P demons. 06:18.620 --> 06:22.220 So it's exactly the same process, but just four different server, different IP address. 06:22.430 --> 06:26.270 The IP address will be Microphone Isabell 10 one three three zero three. 06:26.420 --> 06:26.840 Excellent.