Amazon CloudWatch is a native AWS monitoring tool for AWS programs. It provides data collection and resource monitoring capabilities.
$0
per canary run
Cognizant Cloud360
Score 9.0 out of 10
N/A
Cognizant offers Cloud360, a comprehensive cloud management platform.
N/A
Pricing
Amazon CloudWatch
Cognizant Cloud360
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
Cognizant Cloud360
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.
Cognizant Cloud 360 is very well suited for cloud integration of modern, common software among users of a wide spectrum of proficiency levels. The user interface is well designed and intuitive, and all common software tools have existing implementation tools and intuitive platforms for cloud migration. Cognizant Cloud 360 is not as useful when most users are highly technically competent and use specialized, less common software tools that are to be migrated to the cloud platform. Cognizant is technically sound, but maybe not as much as some established competitors (Microsoft, IBM, Oracle, etc) and also may not have familiarity with lesser-known software applications.
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.
Very good customer service team. Very responsive to inquiries, and willing to collaboratively develop solutions to software Platform integration challenges.
Very intuitive user interface. Layout for various tools and settings is well-conceived and implemented, and the software is ultimately very easy to navigate for even novice users.
Customizable resource library. The platform makes it easy to select tools that are needed without forcing you to subscribe to additional tools that are not needed.
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.
Could improve in agility in the delivery life cycle. When customer demands change and abrupt changes in resources and configuration are required, the change order process is not as quick as desired.
Advanced technical competence and knowledge of a wide variety of specialized software applications is a bit lacking. Relative to some competitor software from Oracle, Microsoft, IBM, or HP, Cognizant isn’t as technically inclined and ready to handle issues with less common software tools.
Not as forthcoming with status updates as some competitors. In cases of interruptions or upcoming updates, Cognizant doesn’t disclose timely and detailed information unless it is specifically requested by the user.
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.
Support is very timely and thorough in their responses to inquiries, and also is very willing to help in finding collaborative solutions to any technical challenges. Overall, the only negative is they may not be as equipped or ready to proactively handle some more customized requests as a more established competitor would be. This is more of a reflection of the software than the support team.
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.
Cognizant Cloud 360 has more of a modern look to it and most of the same functionality. I prefer the layout of Cognizant as I find it more intuitive for a variety of users, but Microsoft’s is also pretty well laid out. Microsoft is more established and has more experience in integrating a wide variety of applications, and so is more ready and equipped to handle less common application cloud integration.
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.
Cognizant Cloud 360 has saved on overall hardware costs, as many resources have been migrated to the cloud platform and local storage and hardware systems are no longer needed.
There was an initial period of negative return as the migration was occurring, as some applications were interrupted, which in turn interrupted the flow of projects and inhibited the timely allocation of resources.
Another positive return can be measured in time savings, as users can more easily access applications from the central cloud source versus various locally customized network locations.
