You're reading from Infrastructure Monitoring with Amazon CloudWatch Effectively optimize resource allocation, detect anomalies, and set automated actions on AWS

Product type Paperback

Published in Apr 2021

Publisher Packt

ISBN-13 9781800566057

Length 314 pages

Edition 1st Edition

Tools

Amazon CloudWatch

Concepts

Infrastructure Management

Author (1):

Ewere Diagboya

View More author details

Table of Contents (16) Chapters

Preface

1. Section 1: Introduction to Monitoring and Amazon CloudWatch

2. Chapter 1: Introduction to Monitoring FREE CHAPTER

3. Chapter 2: CloudWatch Events and Alarms

4. Chapter 3: CloudWatch Logs, Metrics, and Dashboards

5. Section 2: AWS Services and Amazon CloudWatch

6. Chapter 4: Monitoring AWS Compute Services

7. Chapter 5: Setting Up Container Insights on Amazon CloudWatch

8. Chapter 6: Performance Insights for Database Services

9. Chapter 7: Monitoring Serverless Applications

10. Chapter 8: Using CloudWatch for Maintaining Highly Available Big Data Services

11. Chapter 9: Monitoring Storage Services with Amazon CloudWatch

12. Chapter 10: Monitoring Network Services

13. Chapter 11: Best Practices and Conclusion

14. Assessments

15. Other Books You May Enjoy

Case study regarding a consolidated EBS volume dashboard

You have been hired as the system administrator for a company that just migrated to AWS. This company has been running an on-premise service for the past decade, and they are planning a massive migration. This migration involves about 30 virtual machines all running different operating systems, with different configurations and disk spaces. The CTO is worried about monitoring the disk usage of the servers in the long run, as the disk usage of about 10 virtual machines that have been migrated as EC2 instances is not visible in CloudWatch. You have been hired as an expert in cloud monitoring, particularly AWS, to handle this. The CTO wants to have a single dashboard to be able to see the disk usage for every virtual machine/EC2 instance that has been migrated so that the CTO can know when the disk is getting used up and plan for more space or perform optimization operations to delete some of the cache data within the EBS volumes...