Amazon CloudWatch vs. CA Unicenter Network and Systems Management (Discontinued)

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.

Incentivized

It's a decent system if you're a pure IT shop and want to become ITIL-aligned. It forces everyone into an ITIL mentality - service level agreements, change management, and asset tracking. It's very rote, for better and for worse. It's not appropriate at all as a customer-facing or non-IT facing self-service tool. You will never get your end users to really understand how to use the interface.

Incentivized

• 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.

Incentivized

• ITIL ticketing (incidents, problems, etc.).
• Change orders.
• Matching up its asset management system with incidents/change orders.

Incentivized

• 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.

Incentivized

• The user interface (UX) is antiquated and clunky. Compared to ServiceNow, it feels like it's 15 years behind.
• It's complicated - We do routine internal training just to get people to use it correctly.
• It doesn't have an automated way of discovering assets. Everything has to be force-fed.

Incentivized

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.

Incentivized

We have to hire 2 full-time 3rd-party consultants to run this application. That tells me it's not a very IT-friendly, vendor-supported application. Compare that with, say, SolarWinds, which is much easier for regular IT staff to customize without sacrificing features and capability. Sure, we have to bring in Loop1 to consult for us when we need to do a major SolarWinds config change or need a really unusual custom query built, but we never need more than 10 hours of consulting per month.

Incentivized

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.

Incentivized

I did not select CA. If it were up to me, I would migrate us to ServiceNow. The user interface on ServiceNow is 100% more modern and 200% more user friendly. With ServiceNow, the front page for end users makes it clear: one button that says "Ask for something" and one button that says "Report a problem". That's what our end users need. The biggest problem we have in our organization is that our end users don't report issues to the Help Desk often enough and rarely ask for things through the Help Desk. A clean, simple self-service option like this would open up a world of new information for our customer service team.

Incentivized

• 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.

Incentivized

• It helped make us an ITIL shop.
• It was integral during our large IT consolidation 10 years ago in merging 10 different IT departments into one by converging on one ticketing system for all IT issues.
• Its lack of user-friendliness has gated us from being able to deploy a true self-service IT help desk.

Incentivized