Okay.
So now we'll set up the easiest data source, but just be careful of this one because we look at the
settings already.
We've got 2000 active series now.
We haven't really done much yet.
Who thousand is quite high already.
Looking at the free tier, you get 10,000 metrics in a free tier, you'll very easily go over 10,000
metrics.
If you don't set this up the way I do.
Justin is trying out face okay, so into your account interface on the final labs, there's the Prometheus
data source settings here.
Let's look at the details.
Okay.
So once again, my information will be different than yours.
What were we looking at this time?
Is the remote right.
And point is that one there?
So we'll have our existing Prometheus service.
This reminder of what that looks like on the diagram.
We have installed a Prometheus service which happens to be on the same service on US server, but it
could be any way you like and it's querying a local not exporter.
And I set up an order exporter as well that it's also querying so that Prometheus service has its own
user interface.
It's a standalone system, but we've set up a Prometheus data source in Jafar that will also read that
Prometheus data.
Okay, so what we do this time, isn't that right?
URL that is just here.
We'll set up Prometheus to push data to this Prometheus data source here in microphone, a cloud version.
Okay.
So the Prometheus service there will still exist, but while we can still read it if we want to through
our California server, the Prometheus service will be pushing all its data that it knows about to a
Prometheus data source existing on microphone, a cloud instance.
Okay, so back in here again, we need to generate a key also for this one.
So generate right now I'm going to call it may see a show and it's a matrix publisher again so API.
Okay so I can close that remember my case will change once our our place at the end of the video was
something that is actually secret and you shouldn't share your live ones either.
Okay.
We have a new node we need to add for Prometheus config, which is this remote right option here.
So open up your Prometheus configuration.
So I'm on my server where I have my Prometheus service installed and running, so I'm going to see the
UTC makes this and there it is Prometheus.
Why I'm I'm going to edit that so.
Okay.
So this is the Prometheus voicemail as was set up in the course so far.
It has three scrape config, says the first one being from atheists.
There's only one job name node and I actually set up several other targets, but I've commented about
four now in this job.
Name Raphinha.
Okay, so that's the end of that file.
And copy this remote.
Right.
And put that in.
Right click.
There we go.
And that is added with the correct URL, the correct name and key.
Now for saving.
Just so that we don't go over the metrics limit, we should comment about this scrape target.
Also.
The default Prometheus scrape target.
So that you've only got one scraped target and figured there go targets localhost nine 100.
This is so that we don't go over the 10,000 k metrics limit.
You'll see that just even one node exporter will push that number very high.
So now I control X to save that.
Yes.
And so now let's restart Prometheus.
And ticket status looks good.
Now, going back to your main page here, this number will go up in a moment.
But if we go to immigration data sources and we look at the final cloud B code from the information
information's already configured, the data sources was added automatically and is put in the correct
username key.
It's called password here for us.
Okay.
So that is good.
So test that data source is working.
That's important.
Dashboard for note exporters now.
So dashboards browse will import.
And from my documentation this not export a dashboard was it a11074?
So I stopped that in there.
11074.
Like that.
Okay.
Note export of information general metrics like the data source being rom and import.
Very good and it seems to be working so far.
After more time, there'll be more to look at as found.
Localhost, not 100.
That's my only scraped target that I have running on my Prometheus server so that for the last five
we'll see some more data in a moment.
But anyway, you can see that's looking pretty well.
And going back to the dashboard there, these numbers have been updated just yet, but do be careful
that they will update and that will probably be about 5000 metrics already.
Okay.
So just to show what I did using the diagram, I added that remote write parameter so that my existing
Prometheus server sold server is pushing a copy of all its data off to my atheist data source or microphone,
a cloud instance.
So once again, you might prefer to use your phone in this way where you haven't managed to find a cloud
account but be aware that it is quite expensive versus what I've shown in the course where I just set
up it manually on the cheapest installation server I can get.
And also I prefer to do all these things manually like management, firewalls, etc. but anyway, cloud
is option for you.
Excellent.
And also go back into your Carvana account page.
I'm looking at my SB code cloud information here.
You can see now the current usage is 3808 matrix full Prometheus.
That's my low key kilobytes an hour.
So you can monitor that here as well as for this refresh that has not loaded yet, but it will mean
that's an introduction to provide a cloud in case you want to do that.
Excellent.