In this video, we'll now set up a telegraph collector which will collect stats about our operating
system that I installed influx flux debris onto and store them in influx daily, and we'll install those
statistics into a bucket that we've named Telegraph.
OK, so it's going to be installed locally on the same server, so to pushed to one two seven zero zero
one one eight eight six.
Now, I mean, influx to be right now.
If I look at the buckets there and I click Telegraph, I can explore it.
So there's a whole lot of information already that we can already raid these orders.
Internal statistics being created from the telegraph bucket that was created in influx DB.
But the Telegraph agent that I'll install now will push a whole lot of extra statistics to that that
will be able to use.
But just to show that we can already breed data in Gravano just from these available statistics, for
example, memes stats allocated bots, we can see that as a graph, we can actually view that data in
Gravano right now without actually installing Telegraph because this data's already present in flux
DB.
So click script editor up there and that script we can just copy.
Go into Safana and in the Explore tab on Safana.
Select Influx DB paste that there make the time frame a little bit smaller, for example, and you'll
begin to see data.
So we're reading that in Kafala now.
So everything we're seeing in influx DB we can see in Gravano.
And mostly the reason for that is because of the API token here that I'm using code griffon as token
now, something which I should have done in a previous video I'll fix now is actually create a read
only token because if we look at the Gryffindor token, it has a lot of permissions reading right authorizations,
buckets, dashboards, org sources.
Many, many things.
That's an admin user.
We shouldn't be using Raphinha to query influx DB using an admin user.
So what I'll do is create a new API token, a read write API token.
In fact, only I read token that will be Bafana read only.
That's what I'll call it.
Save that refinery to only copy that to clipboard.
Go back into a Farnum data sources in flux DB down here where it says token just reset that and replace
it with the new token save and test.
And now I can only see one bucket and that is the telegraph bucket.
So going back out into Explore sample query showed buckets.
I can only see one telegraph bucket.
So going forward, I'm going to use this to only use your finger Gryphon.
Okay, so I'm no longer going to use that token, and that's this bit better practice.
OK, so going back to explore my script edits a copy that.
That should still work.
There we go and there's some data.
Just be sure that you can still do that with your Read-Only user.
Anyway, if we look at those values that we can query, switch back to query builder.
There's quite a lot in there.
But normally you want more.
If you go to the data tab and you look at these sources page as a whole, lot of things in here that
you can choose from in this video.
I was told the Telegraph collect a process and set it up so that the query data about the CPU disk disk
I was will mem memory net and through other things, processes as well.
This millions of things to choose from, but I'm just going to show you a very quick way to get all
those things in.
First thing, though, is to install the telegraph process.
OK, so we can install that from the downloads page.
So open that up.
OK.
This is the same page from the last video.
Instead of scrolling down further telegraph open source dot a click to installing Telegraph version
one point twenty point four Ubuntu Debian is a few choices there, and they are the instructions.
I've copied these onto my documentation as well.
So first line log on to your influx DB server pasting.
OK, that's downloaded now to install it using the Debian package manager.
And so.
OK.
Sudo service.
Telegraph status.
OK, so it's active running now, it's got an error for one unauthorized will solve that problem now,
so.
Just control C to get out of that.
The telegraph process needs permission to push into the influx DB database.
OK, so what we can do is create a specific token for that purpose, but instead, I'll show you another
way of doing this.
If we go to telegraph here and we select create configuration, we get this wizard and I'm just going
to click system there and continue.
I'm going to court system and it's going to create a dashboard in influx DB querying these properties.
So I create and verify.
OK.
So it's just created a token for us, which we'll use in the moment, but we can ignore this page.
Press finish.
Go to API tokens.
The new token is down here.
So right?
Telegraph bucket rate system telegraph config.
So it has the required permissions.
So we'll use that token there.
But before then, let's modify the configuration for telegraph back on the server side into the new
Telegraph folder.
So ATC Telegraph.
And if we do place there are three files in the Telegraph.
Conf is the one we want.
I'm going to create a backup of that file to C.P Telegraph Token to telegraph dconf thought back.
That's just the backup that you can refer to later on if you want to.
OK, Alex, like OK, it's full force now.
Delete Telegraph to arm telegraph dconf.
OK, we're going to create a new one sudo nano telegraph dconf.
Just like that into all my documentation, I have a default configuration.
Right click is setting up just the minimum we need.
It's quite an output plugin.
Influx DB version two.
We're pushing to the local eight zero eight six the token.
Delete that.
And put this in copy that now if you just right click it, will paste it in.
Don't worry about the word rapping like that.
That's just what A. us when the line is too long to fit with that organization.
And when I created my first log in, I actually created an organization as well, and I called that
SB code.
You can verify that using the application here on your user says SB Code.
That's my organization.
You be different.
Pay packet telegraph.
OK, so we have our inputs for CPU disk disco mem net processes swap and system control.
X Yes.
Now let's restart telegraph.
Restart.
Give it a moment and then check its status.
OK, and if we move along, there are no errors there.
OK, go into flux again, go to explore.
If I just zoom up there, we start to see some extra properties mem net processes.
Swap system, so if I type in process says, for example, I start to see a whole lot of extra things.
Another one is Troy.
Super nice to see you dislike that usage user is a good one.
Submit that I can see the CPU usage user.
Now this same query script editor, we can copy that and put that into a photo.
Click out of that.
And now I'm seeing that same information in graphite.
We can start creating dashboards with that last five minutes.
Now, I'm not going to show you how to try to dashboard, and his video will do that in the next video.
What I'm going to do the next video is rebuild this system dashboard.
Now this system dashboard was just created when I before when to data press, telegraph and did create
configuration and chose system.
So Board's system, so we'll create that in the next video.
OK, excellent.