Amazon CloudWatch vs. Data Center Real-User Monitoring (DCRUM), discontinued

For out business we find that AWS Cloudwatch is good at providing real-time metrics for monitoring and analysing the performance and usage of our platform by customers. It is possible to create custom metrics from log events, such people adding items to a basket, checking out or abandoning their orders.

Incentivized

Dynatrace Network Application Monitoring (NAM), formerly DCRUM, has improved greatly compared to when it was DCRUM; however, it still needs a lot of improvement in end-to-end flow capture with regards to network monitoring. Its alerting and integration capabilities are very good and easy to use. But it still needs a lot of tweaking in usability.

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

• Dynatrace DCRUM can monitor legacy application protocols that are still used in a lot of organizations worldwide who still trust in those technologies.
• DCRUM monitors client-server architectures very well and can pinpoint issues along an infrastructure stack.
• Dynatrace DCRUM can analyze a wide spectre of protocols: Corba, DNS, DB2, Exchange, TCP, HTTP, IBM MQ, Citrix, ICMP, Informix, Tuxedo, SMB, LDAP, MSRPC, MySQL, NetFlow, Net8, Oracle Forms, RMI, SAP GUI, SAP HANA, SAP RFC, SMB, SOAP, XML.

• 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

• Major upgrades process is sometimes unpredictable.
• The use of SQL Server should be evaluated for something else.
• Easier SSL key handling.

It's excellent at collecting logs. It's easy to set up. The viewing & querying part could be much better, though. The query syntax takes some time to get used to, & the examples are not helpful. Also, while being great, Log Insights requires manual picking of log streams to query across every time.

Incentivized

Best of breed.

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

The only thing missing for a 10, would be if they texted or called you back.

Grafana is definitely a lot better and flexible in comparison with Amazon CloudWatch for visualisation, as it offers much more options and is versatile. VictoriaMetrics and Prometheus are time-series databases which can do almost everything cloudwatch can do in a better and cheaper way. Integrating Grafana with them will make it more capable Elasticsearch for log retention and querying will surpass cloudwatch log monitoring in both performance and speed

Incentivized

Nagios can't trace real user transactions from a front-end tier through a backend-tier,;with Nagios you only can monitor server availability and hardware issues. Riverbed is commonly used to determine networking issues without considering real user transactions impact on an application stack.

• Positive for alarms and alert notifications once configured/customized.
• Has upfront learning curve, and cost can increase as does the alarm activity and monitoring details you may require.
• Cost-effective for any size organization keeping with AWS and utilizing its native tools is a savings in long-term ROI.

Incentivized

• Dynatrace Network Application Monitoring (NAM), formerly DCRUM, helped us get a lot of info on an ongoing issue.
• It helped us figure out network bottlenecks in our environment.
• It is a very costly tool and a lot of other cheaper tools give same kind of info.

Incentivized