Dynatrace Network Application Monitoring (Discontinued) vs. Request Metrics

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

Request Metrics is great for small web development teams that want to make fast web applications. It was quick for us to get started and we could use the reports right away without having to read through documentation. If you just need to get some performance metrics, Request Metrics is perfect. It would not be so good for a larger team or a complex backend application as it is pretty limited in what it can measure.

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

• Performance charts are really simple and easy for us to understand what is happening
• It was easy to get started and doesn't need administration or training
• It's affordable for our team
• It's fast

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

• I wish that it could also do uptime checking of the site
• There is not enough detail to drill into individual users

Best of breed.

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

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.

We also consider Speedcurve and Calibre for monitoring. Speedcurve was really nice, but the reports were slow. We had to wait a lot to get information. It was also out of our budget and would require extra justification to use it. Calibre was also nice, but the numbers were based on synthetic rather than real user performance. We felt that this wasn't as helpful for us.

• 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

• The launch of our project dashboard was much smoother and more successful because we could fix problems earlier
• It fit without our existing operations budget