OK, so the next part so that we can query through our lucky data source is to install a collector for
the lucky service and we'll use pronto.
You'll often see Prompt Allen like he used to get OK, so let's install the prompt health service on
our Gravano server as well.
OK, so we can get prompt on the same place that we got lucky.
That's the low key releases web page.
So if open that.
It's currently two point four point one for me.
If I scroll down, I can see the prompt tail related binaries and I'll be installing pronto Linux AMD64
because that suits the architecture of my Linux machine.
So make sure you in that usr local bin folder already.
I already am usr local bin paste, so copy that line there where downloading prompted Linux i amd64
from Safana like it releases version two for one into case of I type less see in there prompt tale Linux
AMD64 zip.
It's on the zip it OK on the prompter alongside these 64 zip.
OK, so that's inflated less.
OK, so from tail locks, AMD64 already has excuse permissions.
Excellent.
If not, you can run that line there.
OK, we don't need to create the config file for our quantile so sudo nano config from tail.
Why now?
OK, let's add this script of copy to the clipboard.
OK, right click or pastes.
So it's going to listen on Port Ninety eight.
It's also going to create a gypsy port, and zero means bind to any port, which means it's going to
be quite hard for me to block their port if I want to.
So I'm going to explicitly put it on a different port number being nine zero nine seven, which is the
next in line after the port that Loki was using.
I will block that port eventually.
OK, when prom tail starts, it will be connecting to our Loki service, running on our local host three
one hundred and pushing data to it.
It has one scrape config called system targeting itself.
And are we reading all the log files?
VAR log star log.
That's a wildcard control.
X to save that, yes, enter Ellis Heights again, and we can see that there's a config pronto watermill
as well.
These files don't need excu permissions.
Only just binaries do.
OK, so this configuration file I got from the official repository again.
So we look at that.
That's it.
So do take note that if you're not using version two point four point one, this configuration file
might be slightly differently or version OK.
So now we'll configure pronto as a service, just like we did with Loki.
So let's create a specific user that what we use to execute pronto tail and I'll call that user pronto
pseudo user add system promptly so we can check that that prompt our user exists by typing ID from tail
and UID nine nine six script by day is nine on six, and as part of the Prompt Hale Group, we could
also check the ID for Loki that we created in the last video.
Loki nine on seven.
Let's create a service file from Pronto, so copy that line using nano again.
And in that, add this script just copied that script to clipboard right click from tail service type
simple user prompt tail exec start user like helping prom tail locks ai amd64.
That's the file which is copied from the Loki repository and unzipped its config file is usr local bin
config prompt male or female?
Excellent.
We can side that control x y for yes, and so we can now start it from tail start and check its status.
OK, active running perfect.
I use control seat, except that status.
OK, so the prompt service is now started and is now running and is pushing data to Loki.
But there is one problem the prompt male user that I've created doesn't have access to.
Read all the log files in the VAR log folder, so I'll show you this if we change our directory to see
a VAR log and we do lists l'hygiene, we can see there's a whole lot of log files in there.
But if I just scroll up, we can see the user and the group of these log files is syslog adim, so they're
further down.
There's also one kernel syslog admin syslog ID. For this log as well our prompt.
Our user doesn't have permission to read those files, so we need to add our prompt L used to that group.
So to do that user mode, add to Group ID. prob tail.
Right click that.
OK, now if we do ID prompt tail.
Prom tale is now part of the A-Team group, that means the prom tale is now able to read the log falls
in the server and pushed information to low key.
After doing that, we should restart pronto.
Case that's taken quite a while to restart.
OK, so that took about a minute.
It would have been scanning those log files.
OK, now we just double check the status.
OK, so it's active running control, so you get out of that.
OK, so now go back into Safana, go to the Explore tab and make sure like use your data source, you
should see this term here.
Low browser and when you click it, we'll see the available log fall so we can query that Prometheus
has put into liking.
So click one of those you can click in to turn them on and off like that.
So all this look at job VAR logs and then show logs, and that is now showing me all the logs that I'm
getting from my syslog.
There's a lot of information there right now.
You can look through that, but we'll go through this in the next video.
And if you want, look at the other one, we can turn off jobs and press for name and we can look at,
say, or slug, for example Sherlock's.
And we can see who's logging on and off and when.
Excellent.
So have a good look through that.
In the next video, we'll look at log Kuo, which is the query language used by Loki to query log files.
And that is a very simple, logical statement there.
We'll look forward to that next for you.
Excellent.