Learn about common patterns for cloud monitoring.
- [Instructor] So in our last video, let's define cloud and monitoring operations patterns. So what's important about this is we're doing this as a last step to understand what we've learned from the use of tools, planning, and requirements. In other words, what we're doing is we're taking a great amount of detail that we've gathered over time including compliance issues, monitoring performance, logging events, those sorts of things, very technical geeky details and we're creating abstractions on top of those details to understand what are the common patterns that we're seeing and it's important to define these patterns to figure out how we're going to better monitor and manage our existing systems.
So I'm looking at the patterns. We need to know what we're watching, in other words, what ends up being kind of the core thing that we're monitoring and what's important to us and we're going to figure that out after about a year's time. So in other words, while we thought storage was going to be important, those seem to pretty much take care of themselves and we have automatic scaling capabilities and alerts to alert us when the storage is reaching capacity. All those sorts of things are there but EC2 or other compute instances and other public clouds may be more problematic and we have to kind of make the pattern that we're going to watch these things, probably 80% of the time, where we watch storage 20% of the time.
And by the way, another enterprise is it could be reversed where we're watching CPUs 20% of the time and storage 80% of the time if they're very data oriented. So why we're watching. So in other words, why are we watching that particular CPU and what's going on and how we're dealing with it, because we need to understand what we're looking for and why it's important to us to make these things occur. And then how we're watching. In other words, what, why, how we're looking at the various systems and basically how we're interfacing with those particular resources.
Some of the mechanisms are going to change over time. APIs are going to morph. Things are going to become more mature. Things are to become easier in some instances and harder in others to look into the resources and monitor the resources. Different standards will emerge. Those sorts of things need to be understood. So again, defining cloud monitoring operation patterns for your enterprise is really kind of stepping back and understanding what's generally going on here. What's generally important to us in terms of how we're monitoring the resources? What resource patterns are most important? Is it storage, is it compute, is it database, is it networking, is it middleware, is it queues.
All these things need to be figured out. Also, who needs the information what, and what and where and how, and how we're going to define the information between various administrators who are going to be leveraging the system. So in other words, how we're going to allocate our talent and our resources, our human resources, to ensure that we're monitoring core aspects of the system that are important to the business.
- Cloud health, performance, security, and governance monitoring
- Cloud monitoring analytics
- Cloud monitoring costs
- AWS CloudWatch
- Librato CloudWatch
- Cloud Cruiser
- Microsoft cloud monitoring
- Rackspace cloud monitoring
- Creating a cloud monitoring and operations plan
- Defining cloud monitoring operations patterns