Learn about how cloud monitoring fits in with operations.
- [Instructor] Let's understand your cloud monitoring and operations requirements. Ultimately, this is about understanding where you're coming from and what you need to monitor, and it's probably the most important step. I don't know how many people, or how many clients, I deal with that have jumped directly into AWS CloudWatch or the Microsoft monitoring solutions or the Google monitoring solutions or Librato or New Relic or other performance and health based monitoring systems without really understanding the requirements. When I get in there and find out their specialized, special purpose database requirements, compliance issues, things like that, that those tools don't really do a bang up job in doing because they're not specific in nature, but they're more general in nature.
You can't define the solution without defining the problem is the core message you're going to get out of this. In other words, you need to understand the resources, you need to understand the requirements, you need to understand your own business that you're in. You need to understand the legal issues and then you can figure out which monitoring solution is going to be best for you. The requirements, have to look at cost. Remember, that's a major thing. You can't spend $100,000 a month on a monitoring solution because it's really not going to provide the value. They're important, but you can find cost-effective monitoring solutions, open source monitoring solutions that are either free or at a fraction of the cost.
You may want to look at those if budget's an issue. Features, in other words, what features do they provide and what features can you look at? We went over alerting, we went over trending, we went over logging and all those things really need to be listed, so what's important to you, providing weights in terms of what's important to you, and then backing those in a particular tool set or tool sets, typically, as to what's going to meet your requirements. And the company, in other words, understand where the company came from, what they're doing, are they a poor start-up without a lot of resources, are they going to be a risk for going out of business? If so, what is your egress on that? What other tools are going to likely use if that particular tool provider goes away? Obviously AWS, Microsoft, chances are in Google, likely not to go away.
Some of these small providers that are providing niche-based monitoring solutions which may be very important to you, could go away, or they could get bought and the tool could be sunsetted and then you have to go ahead and figure out another solution to make that happen. The process, understand your cloud monitoring and operations requirements, again, and we'll go over the other two and three and four in the next presentations but understand what you're looking to do, and your requirements that you need to take and what's important to you as a business and once you define that, it's going to be easy to define your tools.
- 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