Learn the basics of monitoring the operational costs of clouds.
- [Instructor] So let's look at our final cloud monitoring topic, Cost Monitoring. So, what's important about this is that this type of system looks at cost monitoring, how things are going to cost over time. In essence, the ability to watch what you're spending and who's spending what. So, ultimately, this is about the who, where, why and what's being leveraged and who's leveraging it. This serves a couple of purposes. Number one, it provides us with what are called chargebacks, the ability to charge back to a particular department within the organization, a showback.
In other words, we have to allocate something from someone's budget, and, therefore, we figure out how many Amazon web services resources they're leveraging over time and able to, basically, deduct that from the particular budget. So, this is as important, if not more important, than a lot of the traditional technology monitoring because dealing with the cost keep a lot of folks out of trouble. I don't think a week has gone by in the last year where I haven't got a call from some particular client who found that their particular public cloud spend was way out of whack, and what they failed to do was set up a cloud cost monitoring system, a cloud cost governance system, and the ability to figure out who's using what and what are they doing, and ultimately get alerted when these things are occurring before you get the big bill.
So back to the foundations of monitoring and operations. We have cost, which is very important considering the fact that if we spend too much money, very much like we spend too much money on our power bill or our telephone bill or our cable bill, we're not going to have the budget to keep going, so cost monitoring becomes even more important. So, when considering cost, we need to understand what the cloud provider is charging for what behaviors and what resources. So, in other words, the particular monitoring tool needs to have, within its parameters, what Amazon is charging, what Google is charging for particular things such as storage and virtual machines and monitoring and management and database services, things like that, and have that in a database.
And then, monitor, actually, what's occurring out there. In other words, what people are using when when a chargeable event occurs and make sure they allocate the particular cost, understand who's leveraging those costs, understand who's using it, what they're using it for, and, if it goes out of whack, basically, goes out of the parameters that we set that we're able to correct the issue either automatically by kicking someone off the system, more likely calling somebody or emailing them, or often increasing the budget so they can get things done.
So, cloud cost deal with who, who's using what, when, where. This is very important because, ultimately, many people get $100,000, $200,000 public cloud competing bills at the end of the month, but they don't know who used it. In other words, people have access to the same accounts, they may share the accounts, there's no accountability in terms of what resources they're leveraging, there's no governance or limits that are placed on a particular public cloud provider. They want you to spend more money, by the way. So, you need to, in essence, protect yourself.
What are they doing? In other words, are they leveraging storage, are they leveraging database servers, security base systems, things like that. What's costing them money? And then, the costs and trends. So, how are we spending over time again, back to the long-term reporting and analytics. Is this something that's increasing over time to the point that we're killing our budget, or is this something that is legitimate and is going to occur? And, by the way, as we're moving additional workloads in the cloud, which we're doing every day, then, our cloud costs are going to go up.
We just need to make sure that we're monitoring this and we're in control of it so it doesn't get away from us. So, key technology needed, you need trending, figure out where things are going. Governance, we need the ability to play whack-a-mole and put limits on people who are spending too much money. You know, for example, someone in accounting is leveraging too much storage, and they're doing so because of end-of-quarter reports that you need to get done. That doesn't mean they may not have a legitimate reason to leverage that particular cloud system, but we need to understand that needs to be part of the budget so it's allocated so we can track as to what these folks are doing.
And, by the way, we do showback and chargeback so we take it out of their budget. Automation, the ability to automate these systems to, basically, take corrective action, something goes out awry. Logging and then budget over time, and budget is probably the most important thing. So, in other words, if I'm going to set spending limits for the particular department, and I'm going to use this cost monitoring system to basically control those things, then I'm going to disallow certain monies that may be spent by a particular organization that's not in the particular budget, so the budget becomes the single point of reference in terms of who's spending what, what they're doing and whether or not they're allowed to spend it.
- 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