CloudWatch
Hello Everyone
Welcome to CloudAffaire and this is Debjeet
In the last blog post, we have discussed DAX in DynamoDB and with that, we have concluded our introductory series in DynamoDB.
https://cloudaffaire.com/dynamodb-accelerator-dax/
In this blog post, we are going to start with a new AWS service CloudWatch.
CloudWatch:
Amazon CloudWatch monitors your AWS resources and the applications you run on AWS in real time. You can use CloudWatch to collect and track metrics, which are variables you can measure for your resources and applications. You can create alarms which watch metrics and send notifications or automatically make changes to the resources you are monitoring when a threshold is breached. You can also create events that indicate a change in your AWS environment or collect and store logs using CloudWatch.
Components of CloudWatch:
Metrics:
A metric represents a time-ordered set of data points that are published to CloudWatch. For example, the CPU usage of a particular EC2 instance is one metric provided by Amazon EC2. AWS services send metrics to CloudWatch, and you can send your own custom metrics to CloudWatch.
Namespaces:
A namespace is a container for CloudWatch metrics. Metrics in different namespaces are isolated from each other so that metrics from different applications are not mistakenly aggregated into the same statistics. The AWS namespaces use AWS/service naming convention. For example, Amazon EC2 uses the AWS/EC2 namespace.
Dimensions:
A dimension is a name/value pair that uniquely identifies a metric. Every metric has specific characteristics that describe it, and you can think of dimensions as categories for those characteristics. For example, you can get statistics for a specific EC2 instance by specifying the InstanceId dimension when you search for metrics.
Alarms:
You can use an alarm to automatically initiate actions on your behalf. An alarm watches a single metric over a specified time period and performs one or more specified actions, based on the value of the metric relative to a threshold over time. For example, you can set an Alarm on EC2 instance to send you a notification when the CPU utilization is above 95% for more than 10 minutes.
Events:
An event indicates a change in your AWS environment. AWS resources can generate events when their state changes. For example, Amazon EC2 generates an event when the state of an EC2 instance changes from pending to running.
Logs:
You can use Amazon CloudWatch Logs to monitor, store, and access your log files from Amazon Elastic Compute Cloud (Amazon EC2) instances, AWS CloudTrail, Route 53, and other sources. You can then retrieve the associated log data from CloudWatch Logs.
Hope you have enjoyed this article. We will discuss each component of CloudWatch in coming blog posts. In the next blog, we will discuss how to create your own custom CloudWatch metrics.
To get more details on CloudWatch, please refer below AWS documentation
https://docs.aws.amazon.com/cloudwatch/index.html