Instructor: Okay, this is super important for the exam
to know how CloudWatch is linked to EC2,
super, super important so let's go ahead and see this.
AWS provides some metric for your EC2 instances
and AWS will push these metrics for you.
You have some Basic Monitoring such as
the metrics will be collected at five minutes interval.
But you can enable Detailed Monitoring
in which case these metrics will be collected
at a one minute interval.
And these metrics include CPU, Network,
Disk and Status Check metric.
Remember these four, they're very, very important.
Then you're able to use custom metrics and custom metrics
by definition, they're yours to push, they're custom.
And so the basic resolution
of your custom metric is one minute,
but you can go into high resolution custom metric,
which has all the way to one second.
And the custom metrics for EC2 you may want to push,
well that includes RAM or application level metrics,
for example.
If you do do that, then too you have to make sure
that your EC2 instance does have an IAM role
that allows it to push metrics to CloudWatch.
So all the metrics included for EC2, you need to know them.
So the first metric you need to know is CPU.
We will get the CPU Utilization as a metric
and also in case we have T2 or T3 instances that do burst,
then we can get the Credit Usage for the burst and the
credit balance.
For the Network we're able to figure out how much network
is going in our instance and out of our instance.
For the Status Check is basically checking whether
or not our instance is healthy.
We get an instant status.
This is Amazon checking if the EC2VM is working
or a system status, which is Amazon checking
if the underlying hardware is working.
And so these are very important ones.
These are Amazon health checks,
so you don't have any controls over that,
but it basically gives you an idea and you need to be able
to differentiate between your instance status
and your system status.
Finally, only for instance stores,
instance store back EC2 instances,
we get disc information,
we'll get the read and write operations
or bytes for our instance store.
And finally RAM is not included in the AWS EC2 metrics.
This is a common question at the exam, they ask you,
can you get the RAM from CloudWatch?
No, you cannot, AWS does not push the Ram usage
in CloudWatch, it is for yours to push.
Okay, so let's have a look at our monitoring metrics
for our EC2 instance.
So we are going in this monitoring tab
and then we can have a look at all the metrics in here
which I can add into a cloud dashboard
to make it a little easier to see.
So I can create a new dashboard and I'll call it EC2 Metrics
and okay, click on add to dashboard
and that's my dashboard name, I'll just call it EC2
and then click on creates.
Here we go and then add to dashboard.
So I am in my dashboard from CloudWatch
and we can have a look at all the metrics.
So first of all, CPU utilization, we know it
so this is something that can be varying
between zero and 100%
and this is a very common metric to monitor.
Status checks is going to be something we'll see soon
which is around how to have a look at
if your EC2 instances is having a failure
on the hardware level or the software level.
And so we can have the metrics on the failure
by being between zero and one.
Network in and out is quite obvious
which is how much network goes in and out
of your EC2 instance and number of packets as well.
Disk read and disk writes look like they're zero
and it's normal because we have an EBS volume attached
to our EC2 instance.
The disk reads and writes metrics are going to be seen
on the EBS volume itself, okay,
but if your EC2 instance was an EC2 instance
with an instance store, that means that the drive
and the storage is directly physically attached
to your EC2 instance,
then you would see these metrics being populated okay?
This is something common to know and to be aware of.
Finally, for CPU credit usage, this is going to be seen here
for burstable type of instances, AWS will be a zero.
And we can have also a look at the CPU credit balance.
As we can see as we're not using our EC2 instance right now,
the CPU credit balance is going up, up, up, over time.
And finally, if you wanted to enable detailed monitoring
for your EC2 instance, this is how you would do it.
So you click on and click on monitoring
and click on manage detailed monitoring
and you can enable it.
So this is going to show you graphs
with a one minute period instead of five.
So right now this is a five minute period,
but we can go into one minute period
but you're going to incur extra costs
if you do enable detailed monitoring,
which I will not do, okay?
So that's it for this lecture,
I hope you liked it and make sure at the end
to delete your cloud dashboard.
So delete this dashboard and you're good to go.
I will see you in the next lecture.