Book Image

Infrastructure Monitoring with Amazon CloudWatch

By : Ewere Diagboya
Book Image

Infrastructure Monitoring with Amazon CloudWatch

By: Ewere Diagboya

Overview of this book

CloudWatch is Amazon’s monitoring and observability service, designed to help those in the IT industry who are interested in optimizing resource utilization, visualizing operational health, and eventually increasing infrastructure performance. This book helps IT administrators, DevOps engineers, network engineers, and solutions architects to make optimum use of this cloud service for effective infrastructure productivity. You’ll start with a brief introduction to monitoring and Amazon CloudWatch and its core functionalities. Next, you’ll get to grips with CloudWatch features and their usability. Once the book has helped you develop your foundational knowledge of CloudWatch, you’ll be able to build your practical skills in monitoring and alerting various Amazon Web Services, such as EC2, EBS, RDS, ECS, EKS, DynamoDB, AWS Lambda, and ELB, with the help of real-world use cases. As you progress, you'll also learn how to use CloudWatch to detect anomalous behavior, set alarms, visualize logs and metrics, define automated actions, and rapidly troubleshoot issues. Finally, the book will take you through monitoring AWS billing and costs. By the end of this book, you'll be capable of making decisions that enhance your infrastructure performance and maintain it at its peak.
Table of Contents (16 chapters)
1
Section 1: Introduction to Monitoring and Amazon CloudWatch
5
Section 2: AWS Services and Amazon CloudWatch

Understanding the performance metrics of Amazon EFS on CloudWatch

Throughput is measured in MB/s, meaning the number of megabytes written or read per second. This metric is generally used to measure the speed of a read/write operation. Amazon EFS is a storage system, hence, this metric also counts within it. EFS is also unique, as mentioned previously, in that it is a network attached storage service. This means that information sent to write to EFS is via a network. So, any network latencies or deficiencies will have a grave effect on the throughput of an EFS instance.

Being that EFS is a network thing, this means that the number of clients connecting to the EFS storage service matters a lot. EFS has a way of monitoring the number of connections performing any type of I/O operations on it. Remember that EFS can be mounted on multiple EC2 instances, as well as on on-premise virtual machines. So, knowing the number of client connections is another important metric that is captured...