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

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

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

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

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.

• 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