Amazon CloudWatch is a native AWS monitoring tool for AWS programs. It provides data collection and resource monitoring capabilities.
$0
per canary run
Broadcom DX Unified Infrastructure Management
Score 9.1 out of 10
N/A
Broadcom DX Unified Infrastructure Manager, formerly from CA Technologies, is a unified tool for systems monitoring and analytics. It offers multiple deployment options for IT teams and MSPs .
N/A
Pricing
Amazon CloudWatch
Broadcom DX Unified Infrastructure Management
Editions & Modules
Canaries
$0.0012
per canary run
Logs - Analyze (Logs Insights queries)
$0.005
per GB of data scanned
Over 1,000,000 Metrics
$0.02
per month
Contributor Insights - Matched Log Events
$0.02
per month per one million log events that match the rule
Logs - Store (Archival)
$0.03
per GB
Next 750,000 Metrics
$0.05
per month
Next 240,000 Metrics
$0.10
per month
Alarm - Standard Resolution (60 Sec)
$0.10
per month per alarm metric
First 10,000 Metrics
$0.30
per month
Alarm - High Resolution (10 Sec)
$0.30
per month per alarm metric
Alarm - Composite
$0.50
per month per alarm
Logs - Collect (Data Ingestion)
$0.50
per GB
Contributor Insights
$0.50
per month per rule
Events - Custom
$1.00
per million events
Events - Cross-account
$1.00
per million events
CloudWatch RUM
$1
per 100k events
Dashboard
$3.00
per month per dashboard
CloudWatch Evidently - Events
$5
per 1 million events
CloudWatch Evidently - Analysis Units
$7.50
per 1 million analysis units
No answers on this topic
Offerings
Pricing Offerings
Amazon CloudWatch
Broadcom DX Unified Infrastructure Management
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
With Amazon CloudWatch, there is no up-front commitment or minimum fee; you simply pay for what you use. You will be charged at the end of the month for your usage.
Cloud watch is great and essential if you decide to invest in AWS and have any need to monitor the health of all aspects of your VPC resources, or at the organizational level (multiple accounts). Another benefit of the service is constant upgrades at no additional costs; the software evolves to develop modules and interface improvements. For first-time users in AWS, this is going to take a bit to understand, so the learning curve to this metrics environment can seem overwhelming at first glance/use.
Well Suited: - Multiple units (you may split Nimsoft per Groups, companies, etc.) - When your Business Teams NEED Dashboards (they'll love it after they learn how to use, for example, if they discover that the may even run SQL queries together with monitor the webpage of the application, and display business data) Less appropriate: - If you are beginning to monitor your environment (because you need to know your environment at least a little bit to check if the entire set of monitoring Nimsoft plugins will really help you or you will only use it to ping your application) - If you don't have at least one (i do recommend 2 or 3 after some short time) people dedicated to deploy and fine-tune the monitoring. The tool is really good, but if you don't have anyone working on it, you will notice that you're spending money in an elephant to kill an ant or worst, that you passed the entire year, and still have the same problems of the last year, cause no one put the hands enough time in the tool. I saw this happening during the first year when I was the only one working with the tool and still supporting the entire team.
It provides lot many out of the box dashboard to observe the health and usage of your cloud deployments. Few examples are CPU usage, Disk read/write, Network in/out etc.
It is possible to stream CloudWatch log data to Amazon Elasticsearch to process them almost real time.
If you have setup your code pipeline and wants to see the status, CloudWatch really helps. It can trigger lambda function when certain cloudWatch event happens and lambda can store the data to S3 or Athena which Quicksight can represent.
Memory metrics on EC2 are not available on CloudWatch. Depending on workloads if we need visibility on memory metrics we use Solarwinds Orion with the agent installed. For scalable workloads, this involves customization of images being used.
Visualization out of the box. But this can easily be addressed with other solutions such as Grafana.
By design, this is only used for AWS workloads so depending on your environment cannot be used as an all in one solution for your monitoring.
I'd like to see improvements in inventory management. Currently node management isn't as efficient as I'd like.
I also see a big opportunity to offer greater customization in the Detail Tab. I'd like the ability to pick and chose which metrics are displayed by default in the Detail Tab snapshot.
Support is effective, and we were able to get any problems that we couldn't get solved through community discussion forums solved for us by the AWS support team. For example, we were assisted in one instance where we were not sure about the best metrics to use in order to optimize an auto-scaling group on EC2. The support team was able to look at our metrics and give a useful recommendation on which metrics to use.
I believe that CloudWatch is a better solution to use with AWS services and resources in terms of cost and ease of integration with AWS infrastructure services. But keep in mind that Elasticsearch is better at aggregating application-level metrics. We chose CloudWatch because of its capabilities to integrate and monitor AWS services in almost real-time.
All tools have their own gaps , some seem to do more than others, some just work better. With UIM we have found a sweet spot with features, price point, pros, cons, etc
We were able to set up log streaming, retention, and simple downtime alerts within a few hours, having no prior experience with CloudWatch, freeing up our engineers to focus on more important business goals.
CloudWatch log groups have made it relatively easy to detect and diagnose issues in production by allowing us to aggregate logs across servers, correlate failures, isolate misbehaving servers, etc. Thanks to CloudWatch, we are generally able to identify, understand and mitigate most production fires within 10-15 minutes.
Choosing CloudWatch to manage log aggregation has saved us quite a bit of time and money over the past year. Generally, 3rd-party log aggregation solutions tend to get quite expensive unless you self-host, in which case you typically need to spend a fair amount of time setting up, maintaining, and monitoring these services.
Business Units love It - Good for them, but worse for the IT Team until we share the responsibility of the dashboards.
If no one put their hands on it, it will take some time to give results. I'm talking about environments with 400 devices, for example, in something about 6 months to one year, if no one is dedicated, and depending on the consulting company. Some, even certified by CA, was not good. If possible, try to use CA services directly.
IT Teams, after they start to notice that the tool really work, will want to monitor everything. Depending on the company, this will be more or less easy to measure, as ROI. And I'm telling this because usually IT teams don't know how to sell them to C-Levels, and the tool, because of the price, is always a motivation to questions like: "What is this tool? Do you really need it? Is there another way to monitor this?"