Amazon CloudWatch vs DX Application Performance Management

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

Read full review

• Alerting which can be customized by the end user.
• Visualization of the metrics and data presented to provide a unique and attractive interface.
• Flexibility to manage actions and commands that we deem important for each application. The ability to define these and customize the metrics reported for each individual application is huge for us.

Read full review

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

Read full review

• We are facing challenges to meet RFP requirements in few areas where I would recommend CA to improve.
• We are facing challenges for non (java and dotnet application) which CA APM does not support. SAP is another solution where CA APM is not able to address our business requirement.

Read full review

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

Read full review

• Introscope is deeply utilized within the organization. However, CEM and Team Center not as much. Those that use one piece don't generally use the others. Partially because of the curve in learning how to use the consoles effectively.
• reporting is pretty well configured and easy to setup if you know how to use the tools. So this can be easy to use and takes less time to configure for the different groups within the organization.

Read full review