ScienceLogic on Wednesday launched CloudMapper, a visual monitoring service for Amazon Web Services that took more than two years to develop.
Why did it take so long? AWS was adding services and features too quickly. As soon as CloudMapper could capture enough performance counters---health and cost metrics for AWS---something new would launch. Those launches are fun for AWS, but make monitoring tricky.
Dave Link, CEO of ScienceLogic, added that the application, which can be deployed with an Amazon Web Services AMI, on-premises or in a hybrid environment, monitors 337 health metrics on AWS. Most enterprises use AWS in some way, but have had trouble capturing the cloud service's various metrics. It doesn't help matters that AWS rolls out new services and features rapidly.
ScienceLogic's argument for standalone CloudMapper is that traditional tools, namely from giants such as BMC Software and CA, don't capture enough performance counters. AWS' CloudWatch service captures 186 performance counters. ScienceLogic also offers a variety of data center monitoring tools.
"We were going for breadth of coverage and simplicity," said Link. "CloudMapper can launch with a customer's AWS credentials."
IT infrastructure monitoring has become more complicated over time because most tools were able to work off one Internet Protocol address. The cloud brings dynamic infrastructure that's harder to pin down. "When you look at AWS it's really a series of technologies and there are about 50 APIs to instrument against," said Link.
The challenge for enterprises is that they care about operating system and application health, but AWS native reporting focuses on server health and availability. CloudMapper fills in the gaps so a company can see its AWS asset performance as if it were its own data center. CloudMapper can visualize interdependencies on AWS, workloads moving in and out of the cloud, where servers are physically running and aggregate accounts, zones and regions.
As for the use cases, ScienceLogic said CloudMapper could be used to:
- Spot expensive AWS resources;
- Aligning security policies with virtual private clouds;
- Selecting the best zone to use;
- Visibility into AWS.
Here's what a hybrid deployment, which is the most likely scenario, would look like followed by the AWS credential route: