New Relic vs PRTG

• New Relic lets you drill down into the nitty-gritty of your application, breaking down requests however far you want in order to inspect the performance of your application throughout the request lifecycle.
• New Relic offers many integrations with other services and technologies, making it easy to get it set up and start using it.
• New Relic offers many views and types of visualizations to help you understand what's going on in as much detail as you want to know.

Read full review

• Very, very configurable. You can create all kinds of monitors for all kinds of things. Plus it has loads of suggestions out of the box. It can get complicated but monitoring is complicated. Pretty decent interface and good support - active community.
• I really liked how easy it was to add alerts by SMS. So easy to setup.
• I like their sizing models (for purchase). We're actually small enough that we are free. But it's not free as in stripped down - it's free because we don't use many "sensors" and don't honestly have the need.

Read full review

• Cloud-centric / OS-centric. There is no/limited ability to query metrics with an agent installed.
• Insights-based queries (dashboards and alerts) are limited to 1000 (soon to be 2000) records and that doesn't work for enterprise scale.
• NRQL is awesome -- except when it isn't. The replacement QL is more robust but is significantly more complex to learn.
• No agent management tools in the platform. And, yes, you will want agent management tools after the first dozen or so deployments.

Read full review

• Windows Only: PRTG does not support any other platform. Personally, I do not like tools that run on Windows because Windows requires a frequent update, which means downtime. You want your monitoring tool to be as highly available and low maintenance as possible. That and you also require a server license and Windows consume more hardware resource than other platforms. PRTG needs to add support for Linux.
• Limited ability to do things in bulk. There is no way I know of to mass onboard devices or to mass edit devices. So you will by modifying 1 device at a time. For instance, it would be useful to modify the name or company of 200 devices in one shot.
• Somewhat weak widgets and dashboard. If you put a lot of effort into it, you can probably come out with a very useful dashboard to keep an eye on key systems/devices. However, some widgets can look nice at first but they are not so useful or easy to understand. Again, it can be done, but a lot of effort is needed to get it right.
• White interface only. This might not seem like a big deal, but if you have people who use the tool all the time to keep an eye on the system, it can strain your eyes. Need a dark theme.

Read full review

• New Relic helps us detect defects before our customers do.
• New Relic helps us prioritize performance improvements. Engineers don't need to spend time measuring the latency of transactions themselves.
• New Relic helps us notify the appropriate people rapidly when there are problems.

Read full review

• Given us a nice, controlled, ringed-fence portal to deliver to customers for them to view monitoring on the services we sell them.
• Given us plenty of metrics to allow us to measure SLA's and OLA's.
• Given us the tools to deploy proactive measures for service outages.

Read full review