So provided we have the Prometheus data source set up, then we can query Prometheus, we can query
two different kinds of jobs, such as Node and Prometheus.
We can continue.
It will install two dashboards in this video, one for the Prometheus service, which is that there
that will tell us about the performance of the actual Prometheus service and a dashboard for the node
exporter.
And that is there.
The node exporter is useful for telling us about the performance of our server as a whole.
It will have many statistics that will be very useful to watch over time.
Now we can install not exporters on many service and will do that in one of the next videos.
A case, a guide to configuration data sources.
Prometheus in dashboards here, our first dashboard will be this one Prometheus two sets we can import
that don't install this Prometheus stats dashboard.
That's for the older versions of Prometheus and Graphite.
And Matrix won't actually work just yet, but we'll talk about that in the next video.
But for now, that's all we need now.
If we click that, it takes us straight to a Prometheus dashboard.
If we were to look at any of the queries behind these visualizations here, you'll see that the job
is Prometheus.
If we look at another one job, Prometheus and Job Prometheus, this script duration is actually grouping
by job.
There are two jobs node and Prometheus, so already that is very good.
We can see better performance of the Prometheus service and just a reminder what Prometheus is doing.
Prometheus is requesting data from as many node exporters that you can connect to it.
If I had 20 servers, I can install not export on each of those 20 servers and set up Prometheus to
query the non export on each of those service.
And we'd want to know how Prometheus was handling that.
And that is a good graph to help you understand that, such as query durations and script durations.
But anyway, next, we're going to create another dashboard for the exports that go to dashboards,
manage Scott.
Any changes if you want or save them, we're going to import another dashboard.
So let's go and find the dashboard that we want.
Looking at a documentation is a link to the graph found a dot com graphs out dashboards website so open
that yeah, so zero gryphon a dot com bafana dashboards.
And if we use the filters here, it will find a whole lot of dashboards that we want.
But the particular dashboard that I want is one one two seven four and there's a link for there, OK?
Node exporter for Prometheus dashboard.
It's updated recently and you can read about it there anyway.
All I want is the ID, which we already have now put that into the import load.
OK, Note Explorer for Prometheus dashboard.
Selected data source Prometheus and import.
OK, so this is a very impressive dashboard, and this is telling us everything about our server and
it's getting that information via the net exporter.
So that's the net exporter there I've installed on my Gryphon a server.
The Prometheus service is requesting data from the net exporter and making it available for the Prometheus
data source.
And that's what we're seeing.
So there's plenty of information here.
I have one note explorer configured in the Prometheus configuration.
Someone is saying just that one for localist, not 100.
I can actually just make that a bit smaller since I only have one server right now, but really good
information we can say about the CPU, disk space, internet traffic through memory and some other graphs
show the information slightly differently.
TCP ins and outs, open file descriptors.
It is all very good information if you want to look at the performance of your server as a whole, so
you can still not export as many servers.
And then once you've set up scrape targets in Prometheus, you'll have them here as new instances.
OK, so the information that is being used in these visualizations is coming from the job node there.
So if we go to explore or discard any changes and go to metrics browser job node, if I look down here,
most of those metrics start with node for press Prometheus.
Most of those metrics start with Prometheus.
There are duplicates such as Prefixed with Go and a few others.
But those two dashboards, not exporter, focuses mainly on the node exporter, and the Prometheus two
stats focuses mainly on the Prometheus job.
These things become very useful the more time your service is running, you can see anyway.
In the next video, we'll set up a dashboard for the Gryphon US service, which is much like the Prometheus
dashboard, but specific about Agraféna application as a whole.
Excellent.