OK, so in this video, I'll add another S&P agent.
This one will be external when you connect to an external S&P agent doesn't matter whether you're using
telegraph warning system, there are a few extra considerations about connectivity, so I'll solve those
in this video.
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.
OK, so I'm on my MySchool server, and now I'm going to install this and MVPD.
Now I'm only installing S&P D, not the S&P or S&P MIPS loader from the other lesson.
That's because I don't also need to enable MIPS on this other S&P Daymond.
The MIPS translation from allied to the MIPS descriptions happens on the server that is actually making
the request.
The server that is running S&P walk away as an empty table or any of those other S&P commands.
So I only need a stampede because this will return.
The raw stampede data and the translation to MIPS will happen on the Telegraph Influx DB server, where
MIPS has already been installed.
OK, I now need to configure the S&P DX configuration, so S&P decode.
OK, so go downwards until we find the agent address here.
So comment that out and will replace it with this here.
UDP call one six one.
Now, by default, the S&P dateline the story, but to only binds to the local one 27 zero zero one
address on IP born IP six.
I'm not using IPv6, so it doesn't really matter at all about any IP.
The six settings I happen is server agent address.
It's now just binding UDP one six one will bind to zero zero zero zero, so all Ethernet devices banned
on this actual server will be able to get poor.
One six one a woman who's the firewall?
OK, I'm also going to increase the range of wide prefixes that this server will return.
OK, so going down?
OK, so this server will now turn anything with that prefix, which also happens to include that.
So you can actually comment that line out now.
Remember, the Eve table information is actually prefixed with that void.
So in order to allow our server to return that ID plus the one plus everything else, we can just do
that.
OK.
So control to say yes, enter and we can restart the S&P D service.
Also, if you don't have a firewall, there's some IP tables information there that you can refer to.
I'm going to use a firewall anyway, so it's an MPD restart.
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
running on my Mos crossover.
OK, some of my influx DB server.
OK, so I'm just going to copy that command.
I put that in and it's going to replace that section with the VPC IP address of my master server.
So that's the virtual private network address.
If I look at digital ocean, that IP address is 10 one three three three four.
I was a place the.
Now this is not going to work straight away, OK?
That's because on that actual server, my mosque, your server, I have a firewall set up.
So if I go to my firewall settings, my skill?
Yeah, I will create a new rule custom UDP one six one.
I'm going to remove those rules and add the IP address of my influx DB.
That's where I'm making the request from my copy that so paste that into.
OK, save.
All right, so UDP requests to put one six one from that server should now be allowed to back on my
influx DB server.
Run that again.
I get a response and we can see that despite the fact that I didn't install S&P or the MIPS loader on
my MySchool server, I'm still getting MIPS descriptions.
That's because the translation happens on this server.
It's not that important.
No, that doesn't matter if you don't understand what I'm actually talking about, there is just if
you do a lot of work with this and it's good to know what's necessary and what isn't.
Now I'm going to go into the telegraphed configuration and add the agent information for my Mos Cable
as an MPD service.
So clear.
Sudo Nano, ATC Telegraph, Telegraph, dot com.
And so OK.
So scroll down to We Get to the Inputs S&P section here, and agents will add another agent to Pol.
So UDP slash slash the IP address of my Moscow server.
I'm using the internal private IP.
So 10 one three three zero four there and do that.
OK, so the input system is now making requests to two different S&P demons on different servers.
One local and one across the network control x yes.
Sudo Service Telegraph, restart intel and check the status for any errors.
I don't see anything control.
So you get out of that now an influx DB.
Go to the Explore tab and we should start to see some S&P data for the other service s in MP.
They would go its uptime and it's showing me both IP addresses.
That's my Moscow server and that's the local.
If I submit now, we can see two lines being drawn there.
So look at the source there Moscow and Influx DB.
So the hostname is already coming through and that's in the source property there.
So if I just move that sideways a little bit and then select source, we see the names of this service
and also do that the source.
So I will look at Moscow will both makes sense, so that means we can read that in an hour or so.
So script editor?
Copy that.
OK, Explore tab influx, Debbie Paste.
All right.
There we go.
We'll just zoom into that section.
If we go, we can see the data for both my service.
Coming through, look at the table there, I can see this a new row.
Anyway, in the next videos, we'll create a dashboard to read this Gravano.
I'm going to do the same process with my Agraféna server, though I did with the MySchool, so that
I'm getting data from three S and P demons.
So it's exactly the same process, but just four different server, different IP address.
The IP address will be Microphone Isabell 10 one three three zero three.
Excellent.