New Relic vs PRTG

• Monitor traffic rates and server usage on real time
• Helps engineers to dive deep into an issue and guides them to the root cause
• Provides high-level system health status of different components (ie. Server capacity, RPM, page load time, error rate..)
• Near real time reporting
• Links with deployment so easy to understand if an issue has occurred after a particular release

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

• It would be helpful if use cases for particularly a Windows installation, were provided to help determine which set of configuration files would be the one a group would want to control. I.e. potentially with a department trying to do DevOps, it's difficult to determine which team needs to have responsibility for what at times. The reason I mention this, is New Relic seems to in many ways be a tool that's useful for DevOps-related processes and staff.
• On the main New Relic One site, sometimes a refresh option is available for new features. It would be helpful to see what the new features are in advance before trying this out. Particularly if doing a demo or a working season with another team.
• I'm not aware of a page or specific site which describes/summarizes all of the different NR Products and their features.
• Sometimes it's tricky to determine which product to use to accomplish a task.

Read full review

• The probe service can be quite resource-intensive. This can cause false-positive readings from some sensors sometimes.
• The software gets updated very regularly. Whilst this is usually a good thing to fix bugs etc, it does meantime downtime of the monitoring quite often while they are installed.
• The ability to create Maps from Libraries. Very specific issue but a lot of people have been asking for it for years and it is still not available.

Read full review

• Gives us great visibility into what our services are doing at all times.
• Alerts us quickly when there is a problem so we can address it with alacrity.
• Gives us extremely customizable options in regards to how we want to track, store, and materialize our data.

Read full review

• The ability to analyze multiple pieces of information in one place, especially with historical data, has saved our IT department time and headaches. It would be so much more difficult to trace an issue without PRTG, just relying on event logs and an open task manager window.
• The cost is not cheap, so it's an expense that hits the bottom line like everything else. Figure in hardware costs as well, ideally a server outside of your main environment.
• I keep saying this, but the historical data piece is worth so much. There's really no good way to collect all of that information in one place without something like PRTG. And that definitely saves time and money in the long run.

Read full review