So let's look at the Gryphon, a Matrix Prometheus dashboard now to back into Agraféna configuration
data sources, Prometheus dashboards, cofounder metrics, they import that.
OK, so this is not going to work straight away.
Let's look at it.
OK, lots of things missing.
If we look at one of the visualizations he is looking for, job equals Carafano just for the one.
A job equals profile.
OK, so we go to the Explore tab.
Discard Prometheus Matrix browser.
Look good job.
We only have jobs for Node and Prometheus, so that dashboard needs a job.
Mega-fauna now the Prometheus service and the node exporter both provide these endpoints that expose
the metrics that these services are meant to expose or to show those so on your Bafana's server, you
can view those so curl HTP Colon Slash Slash one two seven zero zero one colon 1990 slash metrics enter.
That is a lot of information in that response, but that is the information that you will find when
you query the Prometheus job.
For example, if I scroll up, here's something Prometheus, TSB storage, block sports, I'll just
highlight that so it copies it to the clipboard.
Now, if I thought that into there, we could say that it is one of the things that we can see in Prometheus,
and that's the value.
So it's a key space value kind of set up.
OK, so there's one for everything now.
It's the same thing for Node.
If I do a query on Port nine 100GB metrics, we're getting all the keys and the values for the node
exporter.
I just scroll up.
There's some poor node node system, do you state or do a search for that?
And we go in node system D unit state job node.
So it just so happens that the Gryphon US server, when it's running, also exposes its own metrics
endpoint and that is at Port 3000 slash metrics.
And we go.
So this is a whole lot of Gravano metric information that we can show in Prometheus.
We'll create a new script target in Prometheus.
It will also query this Carvana metrics endpoint.
So we need to open up the Prometheus configuration file that is in the folder side.
ATC Prometheus Ellis LRH.
This is where Prometheus was installed at Prometheus.
That Prometheus why IMO is the configuration space suit?
I know Prometheus.
Why HTML if we scroll down?
Into this scrape configs section here, I'll just scroll further there to scrape configs with a job
name Prometheus and another one job name.
Note this is what we're saying to the Prometheus job is getting its information from local hosts 1990,
and it's just doing a search for slash metrics.
The node is getting its information from local 9100 slash metrics.
So what you're going to do is create another job name for Gravano called Bafana that will take its information
from local hosts 3000.
So put your cursor at the bottom of that highlight just that job name there.
Make sure all the white space is selected and we can put the cursor up.
I can just add an extra space in their job name Bafana.
Throw down static configs at thousand.
Very good.
Now you can delete those to comment lines if you want in nano.
It is control, OK, and then control kigen that deletes lines, but that's optional.
Anyway, it's not the job name Gravano, and the static config is local host 3000.
That is the default port of Kafala when you first install it and is in the scrape config section in
Prometheus Y.M.C.A. Control X to save gas to save the buffer.
Press enter its restart Prometheus.
Double check its status.
I go that's running control C to get out of that.
Now if I just refreshed this whole screen to rug click and press refresh and then I press metrics browser
have jobs selected, we could see this new job for Bafana.
OK, so if I go back into the dashboards now, dashboards manage grandfather metrics there.
We're now starting to get data, so those queries are actually starting to work.
I do a search for the last five minutes.
We're getting most information.
Have a look.
What's wrong with hasty status codes?
They so first thing hasty http request total and is replaced that with this text will be on my documentation.
We now get a graph.
So two things have changed in the later version that status code now has done to school between the
two words and also that value is often a heist http request duration seconds second, some so we can
apply that never go.
We have a new graph which is showing the requests per second and the different status codes.
Now we look at this one here.
Prometheus Alerts Press eight added that it's no longer alerts, so delete that and let's just put a
bracket open up and start typing alert and you'll get some things that it could be.
Now I'm guessing that it's Gryffindor alerting active.
Let's take a look out of that, and that looks right.
There are zero alerts firing right now.
OK, so apply that.
Okay, so that works.
Now the last one, most use handlers edit sort top K Handler page to request total.
So once again change that HTP request total to Safana to be to the second.
There we go.
We start to see a table there now so we can also apply that never go because some information coming
through.
Now this is a very basic Griffon Up Metrics dashboard.
If you search on official Gryffindor dashboard website, there might be other options to choose from.
But anyway, let's just quickly what happens when you try to install a dashboard in Gravano Things?
I look at work because of the later versions, so you have to apply a bit of guesswork and you just
get better at that with experience.
Anyway, save that overwrite anyway.
The next video will install the Prometheus Not Explorer on our basketball server.
Excellent.