This document discusses cloud monitoring and different monitoring tools. It notes that cloud monitoring is different due to changing and dynamic cloud environments. It then lists several traditional monitoring tools like IBM Tivoli, HP Openview, and Nagios. It also discusses newer application performance monitoring tools like AppDynamics and New Relic, and infrastructure monitoring tools like Prometheus, Consul, and New Relic AWS Monitoring. The document suggests cloud monitoring tools need to be flexible, scalable, adaptable to change, lightweight, and integrate easily with automation.

1. Monitoring the Cloud
Gang Tao

2. What to Monitor?
• Object -> App, Service, Device, Infrastructure
• Health Status
• Metric (performance)

3. Why Cloud Monitoring is
Different?

4. Changing World

5. Dynamic Cloud

6. Different Org/
People are using
different tools

7. Grand Grandpa of
Monitoring
IBM Tivoli
HP Openview

8. Network Monitor

9. Nagios

10. Application Performance
Monitor (APM)

11. AppDynamics
Cisco announced its
intents to acquire
AppDynamics for
$3.7 billion

12. New Relic
•Key host health metrics (CPU, Memory,
Load, Disk, Network), collected every five
seconds
•Disk resource utilization and time to full
metrics at-a-glance
•Full search of all your hosts that makes it
easy to find vulnerable packages — or
anything else — in seconds
•A real-time feed of all changes as they
happen across all your hosts, including
config changes
•Docker support, including the ability to
track container performance by image,
version, and other labels
•Correlation of your metrics and events to
provide better context of your hosts'
performance

13. New Relic AWS Monitoring

14. Metrics DB

15. Prometheus

16. Service Discovery

17. Consul

18. Consul Sample Architecture

19. Why not Splunk?

20. Some Requirements
• Flexible/Extensible
• Scalable
• adapt to quick change
• Light
• Easy to integrate with automation tools