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

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

New - relic is well suited if you want to analyse the performance of your services and you want to improve it. Integration with multiple services with same account gives a clear picture of flow of your APIs if you have micro-service architecture. New-relic is less appropriate when you want to do logging of your system. As it does not emits every single calls

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.

• gives us an monitoring of all our underlying servers and also we can configure some alerts upon them like CPU and memory alerts.
• Kubernetes cluster monitoring with new relic for EKS gives us and minute details of our cluster utilisation like node usage, pods memory request and limits
• Network traceability for each and every request with response time analysis is great we can trace which component is responsible for generating response delay
• log managements of the logs the infrastructure is generating we can view logs through there only

Incentivized

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

• I would like to see sort of simulator inside the user interface, that way we can send requests directly from it to test some configuration instead of setting up a test environment in our end.
• It would be nice if the data ingestion can be filtered by APM's. That way we can know which application is ingested most data.
• It would be nice if we could ingest logs (apache, system logs, and other logs) and correlate them with the APM.

Incentivized

The only issue that we have had with New Relic is that the price might be a little expensive for smaller companies. The amount of data you store in New Relic impacts the cost, and can get away from you if you don't work closely with the vendor. Overall though the application is top notch.

Incentivized

Best of breed.

As an engineer, New Relic has been very quick and easy for me to pick up/install/use. It has been less easy for some of the less technical-minded folks in our organization and their UI still is inconsistent multiple years after refactoring their platform to be New Relic One.

Incentivized

Never observed an outage

Incentivized

there are times where browser cache will cause issues that require you to clear your browser before continuing.

Incentivized

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

There are times I feel that the initial support is lacking. And in some cases the automated responses of not hearing anything are annoying if the reason why there has been no movement is because we are still waiting to hear back from NR support. So, i think they should loose the automation as it can seem disingenuous

Incentivized

It's better to start by implementing New Relic in one project and test everything. Try to follow best recommended practices and read all the official documentation. Everything seems well tested. Then, start by installing agents to the rest of your projects and keep a close look to all logs and metrics New Relic gives you.

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.

New Relic is the most full-featured offering that we've found, and is incredibly easy to start using with a PHP app. The New Relic agent is installed as a PHP extension so it is able to monitor and track the performance of any PHP app being run by the web server. Other tools required the installation and setup of a PHP dependency at the application level.

Incentivized

Agent deployment is easily integrated into our workflow. Adding the agent to new servers is quick and painless

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

• Less time debugging issues or letting issues go unknown
• We know of issues before our customers
• One common tool for logs, apm, infrastructure, and most alerting. Makes for easier developer experience.
• Cost is expensive and is one of highest engineering spends

Incentivized