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

Case study on Lambda tracing with Amazon X-Ray

The software engineering team just started using Lambda functions. For them, it is exciting to be able to deploy applications easier, due to the automated pipeline you have created for them using Amazon CodePipeline. So, deployments are smooth and fast. They also have access to the logs of the application in the CloudWatch console, so they can view the logs of each Lambda function. But they notice that data does not move from one function to the other. A particular Lambda function is supposed to call another Lambda function in succession, about six of them call each other in that manner. What service and feature will you use to show the path of the request from the first Lambda function to the last function?

Solution

It is obvious that the challenge they are facing is the inability to trace a request from one Lambda function to another. The service that can help with this is AWS X-Ray. The features in X-Ray are both service maps...