In this video, explore the basics of what is out there when considering cloud monitoring tools.
- [Narrator] Okay now let's get into the fun stuff. Cloud monitoring tools. There are hundreds of tools all performing different roles in monitoring and operations. So understand that you're going to have a huge amount of changing complexity to go through in selecting tools. The trick is to pick the right collection of tools not necessarily the right tool. Keep in mind that Cloud monitoring and operations is really about leveraging several dozen tools typically or a complex enterprise grade problem domain and your ability in essence pick the right tools is going to be an ongoing process and by the way you're going to make mistakes. You're going to have to back up and try another tool and eventually you'll find the right collection of tools that are right for your enterprise. So understand that you have to refresh them often. So this means that we're continuously improving upon the tool sets that we're leveraging for operations. So we're always second guessing the decisions that we made. So part of the success in the culture changes that need to be done as we move into the cloud is the ability to admit that things are going to be constantly changing and we're going to have to continuously improve. So technology we're looking at for this course is going to be AWS CloudWatch and we'll show you a demo. We're going to look at Datadog as an example of a monitoring tool. Librato as an example of a monitoring tool. Cloud health as an example of a monitoring tool. Then Microsoft cloud monitoring. How that works. So these are only five and their fairly important because typically if you're going to run your applications on AWS and your going to leverage AWS and have to do the monitoring to see how things are going. There's a native tool that's there for you. CloudWatch. Just by the fact that you're a AWS subscriber fire up that tool and let it work for you. Datadog, Librato, Cloud health are examples of third party tools that don't necessarily belong to or in their case aren't apart of a larger public cloud provider. So, the benefit there is they can typically leverage, as a third party provider, other clouds at the same time. So if your deploying something in a multi cloud world they'll be able to leverage different cloud providers and therefore you can have different monitoring tools that operate across cloud providers. Then Microsoft is a cloud native tool. It belongs to Microsoft Azure and so you leverage it typically in those environments. Datadog is an example of a reporting tool. Amazon Web Services CloudWatch is an example of a health tool. Librato is an example of a health tool where as ones cloud natives specifically bound to AWS and the other's a third party provider. We have performance which is AWS CloudWatch. Which is able to provide monitoring and management in the performance area as well as is Librato. Which is a third party tool. And then of cost, governance there's Cloud Health and there's dozens of others. And by the way, there's dozens of others for each one of these categories. Whether it be governance, reporting, health, cost, security. And it's really your job as a cloud monitoring and operations professional if you choose that career path is to understand the different tools out there. The pluses or minuses of leveraging the tools and typically picking a collection of tools to solve your issues. So picking a tool. You need to understand your requirements. You do not have to fall in love with a tool and then try to find a problem that that tool is able to solve. This is a matter of you understanding your problems and then picking a tool to solve those problems. Keep in mind there's a budget. So you can't spend a million dollars on many of these tools because the money just doesn't exist to support them ongoing. So, you have to understand the pragmatic nature of the tools and their ability to in essence to bring value for the cost that your paying. And evaluations. You got to test the thing. It's one thing to look at what it says it does on the website. Perhaps even another thing to get a demo from the provider but test it in your environment. Understand that there has to be a certain amount of acceptance that occurs. And these by the way can last from 10 days to 30 days. Sometimes 60 days before we understand the true capabilities of the tool and it's ability to provide value in our particular cloud environment. So how does this translate to cloud? Well private, public, hybrid. We have usage, cost. Usage, cost for public. Usage, cost for hybrid. So if were picking for example in this case cost governance tool and say Cloud Health is an instance of that that we're going to look at but there's others out there as well. Then our ability to in essence look at a particular environments and how they in essence are applicable in those particular environments are really going to be beneficial. So in many instances we have legacy systems such as the private cloud based systems that are mixed together. We have public cloud or public clouds plural and then we have hybrid clouds which is the paired use of public and private clouds together. So your ability to in essence monitor are basically pick the right tool for your particular problem domain. Your particular architecture. You know, whether it's hybrid, all public, all private or typically it's going to be all of the above is going to be very important to you in essence driving this tool selection going forward.
- Cloud health, performance, and governance monitoring
- Cloud monitoring analytics
- Cloud monitoring costs
- AWS CloudWatch
- Librato CloudWatch
- Microsoft cloud monitoring
- Creating a cloud monitoring and operations plan
- Defining cloud monitoring operations patterns