Paessler PRTG Reviews & Product Details

It is best in carrying out its own setup faster by automatically finding networks and routers. It is very good at controlling numerous sensors and handling them easily. It is very flexible and supports 3rd party protocols and interfaces. Review collected by and hosted on G2.com.

It definitely requires training and skilled personnel for using this software. It requires a huge amount of storage space. The performance of the tool might get compromised due to controlling/handling a large number of sensors. Review collected by and hosted on G2.com.

The stability remains impressive, even when handling peak monitoring loads. The notification policies are detailed enough to prevent alert fatigue, allowing for a more manageable and focused experience. Review collected by and hosted on G2.com.

Creating custom sensors demands some scripting expertise, which can be a hurdle for those without that background. Additionally, exporting reports in specific custom formats requires additional steps and effort. Review collected by and hosted on G2.com.

I love that the device tree structure mirrors my actual network layout — makes it very intuitive.

* The option to tag devices/sensors is underrated; I use tags to group by department and service.

* The fact that I can integrate with ticketing tools via API is very practical. Review collected by and hosted on G2.com.

* Large reports sometimes take too long to generate.

* Some sensors require a bit of scripting knowledge to customize properly.

* The licensing model means I need to plan carefully before adding too many test sensors. Review collected by and hosted on G2.com.

I love that I can pause notifications during maintenance windows — no more unnecessary alarms when we’re patching systems.

The device tree structure makes it really easy to mirror our actual IT infrastructure layout.

The API is great — I connected PRTG data into a custom dashboard we use for daily stand-ups. Review collected by and hosted on G2.com.

Sometimes the auto-discovery picks up devices I don’t care about, and I have to clean them up.

The licensing model can feel restrictive when testing new setups.

The mobile app lags when scrolling through large dashboards. Review collected by and hosted on G2.com.

Once I have configured the sensors I want to monitor for a specific device I can always clone it. What is a very user-friendly task before, it is even more easy since I have learned to use the new API. It provides me with the information I need from sensors covering up to 365 days, making daily analysis easy. Review collected by and hosted on G2.com.

The new interface is faster, but it still doesn't have all the features of the old one. So I work with both at the same time. Review collected by and hosted on G2.com.

Easy to get started — auto-discovery made setup quick and I had monitoring running within a day.

Alerts are accurate and reliable, I only get notified for real issues instead of endless false alarms.

One tool covers almost everything: servers, switches, applications, and even custom scripts.

Cost-effective, stable, and gives real-time visibility without adding unnecessary complexity. Review collected by and hosted on G2.com.

Desktop and mobile apps could use improvements in usability.

Missing features like better syslog handling, deeper cloud integration, and easier automation.

Licensing based on sensors can get expensive quickly since one server consumes multiple sensors.

Support and roadmap updates could be more responsive. Review collected by and hosted on G2.com.

1. Fast time‑to‑value: automatic discovery and a large library of preconfigured sensors let you start monitoring servers, switches, interfaces and common services in hours, not days.

2. Clear, actionable visibility: intuitive dashboards, maps and dependable alerts make it easy for on‑call staff and NOC teams to spot and prioritize real issues at a glance.

3. Friendly for small teams: the Windows installer and solid documentation kept our rollout smooth — we had meaningful monitoring running the same day without hiring extra staff.

4. Reliable core functionality: uptime, bandwidth, CPU/memory and service checks are robust and help surface trends before they become incidents. Review collected by and hosted on G2.com.

1. Sensor‑based licensing: costs can climb quickly once you count interfaces, VMs and multiple service checks — plan your sensor estimate up front.

2. Windows‑only core: the primary deployment is Windows-centric, which can limit multi‑platform collector strategies for cloud‑first or heterogeneous environments.

3. Customization and integrations: building bespoke sensors, scripting and API workflows is more manual and less polished than some integration‑focused alternatives.

4. UX gaps in editing: map/dashboard editing can feel dated (limited undo/copy‑paste and HTML-centric tweaks), which slows iterative refinement. Review collected by and hosted on G2.com.

1. Pragmatic, appliance-style monitoring that our NOC used every day — discovery and device templates let me onboard a new site in under an hour.

2. Remote probes use encrypted tunnels and worked reliably across poor WAN links, so we collected accurate metrics without huge central load.

3. The API is solid: I automated device provisioning and deprovisioning from our CMDB, which eliminated manual mistakes and saved several hours per week.

4. Notifications are flexible — email, webhook, scripts — so we could push structured incidents to Slack and trigger safe remediation steps automatically.

5. Maps and live dashboards turned into our operational status board; engineers and managers alike knew where to look during incidents. Review collected by and hosted on G2.com.

1. Sensor licensing forces discipline. If you don’t consolidate metrics into useful KPIs, license consumption spikes quickly.

2. Out-of-the-box retention management is basic; we had to implement down sampling/archive scripts to manage long-term storage and keep UI snappy.

3. When many people open large dashboards simultaneously the web UI can lag; role-based focused dashboards helped but take design effort.

4. Some custom sensors (REST/script) needed hardening and retries for production reliability — they work, but expect to test thoroughly.

5. Support times varied based on region — proactive testing of HA and upgrades in our lab was necessary before production changes. Review collected by and hosted on G2.com.

1. Fast to stand up: discovery gave me a working view of switches, firewalls and servers in under an hour — good for quick pilots.

2. Clear visualizations: maps and dashboards made it easy to communicate status to ops and non-technical stakeholders during weekly reviews.

3. Remote probes work: placing probes at regional sites kept polling local and kept our central server responsive over flaky WAN links.

4. Practical automation: I built a small script PRTG can run to restart a hung service; that eliminated repeated manual fixes for a known issue.

5. Useful historical data: daily/weekly reports and trends helped me validate ISP outages and plan capacity changes. Review collected by and hosted on G2.com.

1. Sensor-based licensing can surprise you — costs rose faster than expected when we added interface counters and flow sensors.

2. The web UI can slow when many sensors or very complex dashboards are open at once; splitting dashboards helped but required extra setup.

3. Deeply custom reports required exporting data and some scripting; built-in templates cover common needs but aren’t infinitely flexible.

4. Mobile dashboards can feel sluggish loading large historic charts. Review collected by and hosted on G2.com.

PRTG makes it straightforward to bring new devices and services under monitoring with minimal effort, which significantly shortens the time to get value out of the platform. Its wide sensor library covers most infrastructure needs, and the customization options allow us to tailor monitoring to unique use cases. The interface is intuitive, making day-to-day operations seamless even for new team members. In addition, the vendor’s support team has consistently provided fast and knowledgeable assistance whenever needed. Review collected by and hosted on G2.com.

Managing very large environments can become resource-intensive, and the licensing structure based on sensors requires careful planning to avoid overspending. Advanced reporting and visualization are functional but less refined compared to specialized tools, which can slow down more complex analysis. Review collected by and hosted on G2.com.