So let's go through the new Klutch Unified Agents, and this is a new kind of agent which does metrics
and logs at the same time.
So it will be a great time to look at these agents in details.
So we're going to launch an instance and I'll use Amazon the next two.
And also like this one, I'll use it to to my crew.
And then for the instance detail, I will create a new email.
And for that I am role.
I'm first going to create it and say it's very easy to click on the next permissions.
And in there I'm going to search for policy.
And it's called cloud watch.
So let's look at Cloud.
And so we have cloud agents, server policy.
I think this one will be great.
Let's look at it in details.
So it has logs, put logs, events, log stream and create large groups.
So it will allow us to log stuff.
And also it has the cloud which put metadata.
So it will allow us to send metrics, customer metrics into cloud, but also it has the SSN get parameter.
And we'll see this in this lecture around how we can fetched configuration of the cloud agent from SSN.
So this is perfect.
We'll use this one call Nextag and next review and we'll call this one and Adewusi Cloud.
Watch the role for.
Easy to OK, this is great create the role and it's verify that everything is correct.
So I'll go to this role and the policy is there.
So let's attach this role into our instance.
And here it is.
And for now, we will not do anything else.
We'll keep this.
We won't.
You dogs.
Let's use Tiger.
Let's just name our.
You see two instance lugging instance because it's going to lug something and configure a security group.
This is fine with you and launch lunch and I usually skip areas and Lorraine says, OK, so our instance
is lunch and we're going to install Apache on it to just have a simple Web server and we'll stream the
lug of Apache onto codewords.
So back on our instance, let's connect to it using Ishita instance, connect, and that's going to
be simpler.
And from this I'm going to install AGB.
So for this I'm doing Studio Asou youm install HPD and this will install the Pache for me.
I'll say yes and then I'm just going to create an index that malleefowl.
So I'll say Hadco how the world into var w its html index dot HMO excellence.
So now if you go to our instance in here and then we go to our security group to the inbound rules,
so and we're going to add the HDP rule just so we can test whether or not AGP, HPD was correctly installed.
So here we go.
This is our rule that has been edited and back into our letting instance.
I'm going to copy the public, Ginés, and it's saying it's not it's perfuse because we haven't studied
it.
So that makes sense.
So we'll do a pseudo system.
Sitel as starts, uh, start HTP.
So this would again start as GTP d and now this should have started my Apache server.
So if I refresh this page it now says Helliwell.
OK, so everything is good.
We have installed HPD and now we would like to do is trained to log from VAR Log and in their loops
and in there we have different logging's available to us.
But the one log we are interested in too is HPD and then we'll have in their access log.
For example, this is one log file and we'll also get error log if we wanted to in here.
So these are two kind of logs that we'd like to have InterCloud watch.
OK, so let's get back into cloud watch.
And so the first thing we have to do is watch, actually, but the first thing we have to do is to install
the unified cloud agents to get started with cloud, which looks.
So there is this new thing is that before they used to be a covert agent for logs specifically, and
it was called the cloud, which logs agents and not.
And they used to be a metric system.
And the script to send data from your Ecija instance, for example, RAM and disk info into cloud watch
metrics as well.
So now they have created something called the Unified Cloud, which logs application sorry.
And that allows you to both send metrics, custom metrics and logs into, um, clouds.
And the cool thing with it is that you can store and retrieve its configuration into the system parameter
store and that will allow you to have a quick setup for all your instances if you wanted to have them
all configured the same way.
OK, so what we'll do is we'll go ahead through the pain of configuring it.
If you go through documentation, you'll find it's relatively complicated.
You see how you get started.
But thankfully, I've done this before and I've just summarized the information of how to do it here.
So the first thing we have to do is to do Webjet and download this file.
So let's get back into our easy to instant connection.
I'm going to exit the user and I'm going to show up, get to download this Amazon cloud agent R.P.M.
file.
Then when we've done this, we need to install the cloud agents.
So we'll do pseudo rpm minus you and then look at the file which is downloaded.
So here we go.
Now it's doing this.
And finally, we need to run the wizard and the wizard will go through the configuration of the cloud
agent for us.
So let's launch the wizard and see what is happening.
So it's saying, which OS are you planning to use for the agents?
And we are planning to use Linux.
The reason why is not smart, quote unquote smart and saying while you're using Linux, so obviously
you want Linux is that we could configure the cloud agent for Windows directly from the Windows, from
the Linux machine, and that would be fine.
So that's why we're here.
We're doing Linux.
So one.
And are you trying to fetch the default region for the EU data are using Ishita or on premise host while
saying, OK, we're using Ishita, which is are planning to run the agents as us so we can use route's
CW agents or others.
I'll use routes.
Do you want to turn on the stats, Deliman?
So this demon is used to collect stats demetris metrics from your applications.
And this is something that could be quite nice because if your application is the stats, the endpoints,
then the unified agents could send this directly into kybosh.
So we'll say yes, although we will not use this and so on.
What ports do you want to use it?
Uh, it's one, two five is absolutely perfect.
OK, now what is the collect interval for the stats to demand.
We'll keep it as ten seconds.
And what is the aggregation interval.
We'll keep it as sixty seconds.
OK, do you want to monitor metrics from collectedly.
So this is another kind of demand we can collect metrics from.
So we'll say yes.
And do you want your monitor and your host metric, for example, CPU, memory, etc.?
Yes, we definitely want to have CPU and memory.
Do you want your money to keep metrics per core and this is something we'll say yes to Soheir, things
to this cloud, unified agents, we're able to get CPU metrics not just at the aggregate level, the
way we see it in the cloud console, but per core.
So this is great.
And do you want to add two dimension, for example, emoji, instant side and so on into the metrics
will say?
Absolutely.
And then would you like to collect your metrics at a high resolution at some minute resolution?
And this is something we've seen for custom metrics.
So we could be every one second, every 10 seconds, 30 seconds or 60 seconds.
And to make sure that we don't overpay, we'll just keep it at 60 seconds.
But these are all the options that we can get because we have a custom metric.
What's the default metrics?
Conflict.
You want one basic standard in advance, and I'll just ask you to refer to the documentation for this,
but we'll just keep it with basic.
And this shows us the configuration that we have as follows for now.
So we are saying, OK, the agent is collecting six second run US routes and here is a dimension that
we need and here's the metrics that we collect and so on.
And we're going to collect the disk and also the memory and the memory use person.
So we'll get some ram information into cloud logs and so on.
So are you satisfied with the config?
We'll say yes.
And now we're done.
Now, I said, do you have any existing cloud logs here?
And so this is all the agents, because if we had the the agents, we would be able to import a configuration
file directly into this unified agent.
But because you don't have one or just say no.
And do we want you monitor any luck, we'll say yes.
And look how fast is going to be var log speed access underscore Lugg.
And this is going to represent the access log of our Apache server and the log group name could be access
logs.
Excellent.
We'll just keep it simple and the luxury name will be instant.
Perfect Perfect's.
Do you wanna specify any other files.
Yes, we'll say yes absolutely.
And this time it will be var log htp error underscore lugg excellence and we'll keep everything as default.
And you want any additional files.
I'll just say no and this should make it fully ready.
So here we go.
So we have the entire config in here.
And as we can see now, there's a log's part in this JSON configuration which says, OK, you should
collect these files.
And the collect list that you need to have is these file path with his group name instruments.
So everything could be editable afterwards.
Right.
So as I please check the debug content of the config and the content is also located in this file name,
so we can go ahead and copy this excellence and you can edit it manually if need to.
And the question is, do you want to store the config in the SSN Panetoz store?
And the answer is yes.
What parameters for names you want to use for your config and you'd use Amazon cloud prefix if you use
the managed policy.
So Amazon cloud Linux is a great one and I don't think it's going to work unless we would have the rights
and policy for this.
So if you go back to IBM, remember the cloud agent server policy allows us to just get perimeter as
well.
But we need to edit this to also do it puts.
So what I'm going to do is attach a policy and I'm going to type of cloud touch again.
But in here we can do cloud agent admin policy and this admin policy does everything as before.
But this time it allows us to do a Put's perimeter as well on the same Parmeter story.
So let's select this one click on Attach Policy and now this is good.
So now if we go back to our instance and go ahead and press enter to keep this choice and say, OK,
I'll use one is a great place to get started.
And the address credentials you should use is the one directly from the SDK.
So we'll keep it as one.
Here we go.
It's as successful.
We put config department store, Amazon Cloud Watch Linux program exists now.
So I'm just going to pause this video right now and I'll see you in the next video to see what happens.