RMG203 Cloud Infrastructure and Application Monitoring with Amazon CloudWatch - AWS re: Invent 2012

1,840 views

Published on

Amazon CloudWatch provides AWS customers the monitoring platform for keeping tabs on their cloud infrastructure and applications. In this session, we show you how to use CloudWatch to monitor vital operational resource data such as EC2 Instance CPU Utilization, ELB Request Counts, RDS Read Throughput and much more. Learn how to configure CloudWatch Alarms to alert you any time services are operating outside of ranges you define. Finally, see how you can monitor applications on your EC2 instances or outside of AWS.

0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,840
On SlideShare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
0
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

RMG203 Cloud Infrastructure and Application Monitoring with Amazon CloudWatch - AWS re: Invent 2012

  1. 1. Derek Pai, Senior Product Manager, AWS Henry Hahn, Senior Product Manager, AWS Darren Lee, Sr. Quantitative Engineer, Bizo#reinvent
  2. 2. • Quick access to resource measurements• Answer important operational questions• Receive timely change notifications• Reduce mean time to recovery
  3. 3. WHAT IS MY INSTANCE’S CPU UTILIZATION?
  4. 4. IS WEBSERVER TRAFFIC UP OR DOWN?
  5. 5. • Auto Scaling groups • Elastic Load Balancing• AWS estimated charges • Amazon Elastic MapReduce jobs• Amazon DynamoDB tables • Amazon RDS databases• Amazon EBS volumes • Amazon SNS notifications• Amazon EC2 instances • Amazon SQS queues• Amazon ElastiCache • AWS Storage Gateway caches
  6. 6. DEMO
  7. 7. DEMO
  8. 8. DEMO
  9. 9. INSTANCE MEMORY METRICS
  10. 10. Elastic Load Balancing CloudWatch Ops reports EC2 Instances Asperatus Application Alerts (email, SNS topics SMS, etc.)
  11. 11. Asperatus client codeMetricTracker asperatus = MetricTrackerFactory.forApplication();asperatus.track( “requestSize”, 500, Unit.Bytes, MachineInfo.dimensions );
  12. 12. Asperatus – Error Logging# logging.propertiesHandlers=com.bizo.asperatus.logging.error.ErrorLogHandler,…// Increments the application’s ErrorCount metric// with exception class and logger namedimensions.LOGGER.log(Level.SEVERE, logMessage, exception);
  13. 13. Asperatus – JMX Integration{ “objectName” : “java.lang:type=OperatingSystem”, “attribute” : “OpenFileDescriptorCount”, “metricName” : “OpenFileDescriptors”, “unit” : “Count”}// on application startupnew JmxBridge(asperatus).monitor(config);
  14. 14. Operational Alertsalarms: - # This might be the most important # alarm for web services metric: [ Sum, HTTPCode_Backend_5XX, LoadBalancerName=MyELB, AWS/ELB ] trigger: [>=, 250, 5m] notifications: ALARM: [ MySNSTopic ]
  15. 15. Front-End Bizographer ElastiCache DB1BizographerClient DB20-10ms 10-20ms 20-30ms CloudWatch
  16. 16. 95%
  17. 17. darren@bizo.com http://dev.bizo.com http://code.bizo.com
  18. 18. CloudWatch console• https://console.aws.amazon.com/cloudwatchCloudWatch documentation• http://aws.amazon.com/documentation/cloudwatch/Memory and disk monitoring scripts• Linux: http://aws.amazon.com/code/8720044071969977• Windows: http://aws.amazon.com/code/7932034889155460
  19. 19. We are sincerely eager to hear your feedback on this presentation and on re:Invent. Please fill out an evaluation form when you have a chance.#reinvent

×