So we are back in the second part of the climate unified agent configuration, so we just put the perimeter
into the pan and restore.
So let's have a look.
We're going to assess them for looking at the perimeter store.
So I'm going to open a system which is a systems manager and we'll see systems manager in depth in a
future section.
So here we go.
We have parameters in here.
And I'm going to look at this one called Amazon Cloud, which Linux.
And we can look at the value.
And it is this massive jassam that was created by the wizard that is inserted into this Panera.
And why do we have this?
Well, it's pretty obvious because we want other instances to boot up and directly fetch the value of
this configuration and use it for the cloud agents configuration.
So that makes a lot of sense.
So how do we use this?
Because right now, if you go to cloud, for example, and refresh, I mean, nothing happened.
We don't have any logs.
And if you go to metrics, we don't have any metrics.
So how do we start things and how do we start things?
Two points at this new SSN Parmeter.
So for this pretty easy, you have the option to two options.
OK, you can either Boutte's your cloud agents from an SSN configuration parameters to your name, OK?
Or you can directly bullets from a file in the file path.
So two options.
Either we use this file right here that was inserted into our operating system.
So we're saying, OK, look at the content of this file and use this file to boot up.
That would be the second command or we'll do like the cool kids do.
We'll use this this one, which is you need to start.
Oops, you need to start the clock agents, OK, by fetching a config and it's going to be a model for
you too.
And the the parameter surname is going to be and we need to insert it from the one we had in here.
So I'm going to go to a systems manager, copy this.
And back in here.
Right click.
And this is not working.
So that's with the old way, which is going to write it out.
So it's called Clowe.
Which Linux.
So Amazon.
Cloud, watch Linux and here we go, and so we are getting it says, OK, successfully fetch the config
and saved into this 10 file, then it starts to configure to validate the configuration.
It said it's as good and the validation phase has succeeded and the second phase has not succeeded.
And the reason being is that we're missing a file called Type's DB.
So what we'll do is that we'll have to create this file.
So I'm going to do make directory minus P, user share, collect D, so this is going to create the
right directory for me and I'm going to use this as pseudo and then I'm going to do pseudo touch, user
share and collect data and then finally types that DB just to create this file.
So now this has been created and so now hopefully we can go ahead and restart the agents.
And now, yes, the agent has been working and everything should be started.
So now we should start seeing the cloud logs and the cloud metrics into cloud.
So let's have a look.
So I'm going in cloud watch.
I'm going to refresh this.
And now I see my access log and my error error log log groups that have been created.
So here I am able to see, yes, my stream, which represents the access log that I have in here from
my Apache server.
And I could go obviously in here and look at the error log.
Excellent.
So this looks trim as well as great.
And then finally, if I go to college metrics, I could look at S.W. agents.
This is collaboration's and I get some custom metrics.
For example, I can get disk use so we can see how much of the disk is being used by every different
type of directories.
But also, I could go one up and look at this one.
And here this shows me the ram I use.
So here 12 percent of my ram is used.
And again, this is a custom metric that has been inserted by Macklovitch, uh, unified cloud agents
into college metrics.
So really cool.
I no longer configuration.
I know, but the idea with this new unified agents is that the configuration itself is stored into the
prime minister and can be changed, obviously whenever you want.
And all the instances may be using user data would simply fetch this configuration directly from SSME
and use this to configure the cloud, which logs agents the cloud unified, which is something that's
a little bit easier to do than just going to go ahead and configuring this file to be appearing on your
instant's magically every single time.
So I think this is quite an improvement from Amazon, especially as it provides us a lot of different
metrics and a lot of different facilities for luck files and so on.
Finally, you may ask me what metrics can be collected by this new collaborations?
Well, if you scroll down, you can see that there is a lot of different metrics that can be collected
by the cloud region, could be around CPU.
So if you Timex active guest and so on.
So we get some sebu information and a lot of those actually you get some disk free information.
So how much disk is being used on my machine, which is interesting.
So disk three disk use as a percent and IO time and so on.
And if we scroll down we get some information about the memory.
So this is a so how much is active, how much is available available as a %s and free and so on and
total.
And we get some information around the network interfaces as well in there so we can get some information
about the number of packets sent and received and so on.
And if I scroll down, we get some information about the processes.
So how many are dead, blocked, idle paging, running stopped and so on.
So we get a lot more information and finally swap three used and use %s.
So a lot of new metrics that can be collected by the cloud unified agents and for it it'd be super simple.
You would need to go into the Palantir store and edit the configuration and add on these metrics in
here that are collected by the politicians and you'll be all done.
So that's it for this lecture.
We are pretty happy, the state of it now.
We have two large groups to work with, so we'll see you in the next lecture.