One of its valuable features is the fact that it handles multiple operating systems... And I like the fact that it tells me when things are about to fall over, which means I can preempt it and not have to wake up at three in the morning to fix it.
It's very easy to manage when you've got time to do some work on it: things like adding devices, adding groups, adding sensor clusters, and being able to clone and move stuff around.
We can see trends for a lot of different things, such as hard drive space and bandwidth usage. We can see and plan for the future by knowing, "We're sort of at 75% capacity now. In three months time, we know we're going to be up to 90%,so we need to plan ahead for it, getting upgrades booked in place." Since things like this take time and effort, it's handy to see trends into the future of where our company is going.
Infrastructure Team Lead at a recreational facilities/services company with 10,001+ employees
Apr 10, 2019
We use the remote probes a lot for our branch offices. Instead of deploying the full instance of PRTG, we'll put a remote probe out there. This simplifies the whole deployment for us.
It is a central solution in terms of how to actually use it. It has a very easy dashboard. Everything is concise. We are able to create custom sensors. For different parts of the business, we have many products across many environments, and it works for everything.
It would be good if there were better graphical interfaces when you have it on multiple monitors... Because we have so many servers, things can get lost in the fog a little bit. Maybe having a better way of showing different geographies, Flash, etc., would help.
The thing that we do struggle with a bit is in the historic data. If I want look over 30 days, because it averages out onto one graph, you can't zoom in and drill down information.
I wouldn't mind better categories for the sensors. When I go to add a new sensor for a new device, there are some categories in there already, and they can be filtered out, but there's quite a large pool of sensors... When I want to go in and find something quite specific, I have got to scroll down and scroll down to find what I'm actually looking for,
The only sort of limitation is the actual probes. So, if you don't have enough probes on there, you can over flip them and cause the WMI sensors and SNMP sensors to sort of overload. Sometimes, they might timeout for a minute, but they do come back.
In terms of sensors and probes, it would be really cool if PRTG had a purely Azure-based solution. We had to install a probe on one of our cloud servers and then let that probe out from there. It would be really cool if it just monitored Azure without having to install something on the device.
Infrastructure Team Lead at a recreational facilities/services company with 10,001+ employees
Apr 10, 2019
Once you start going above 5000 sensors, things do start to get a bit shaky. There are some best practice out there that you will need to adopt and be aware of.
Information Security Analyst at a financial services firm with 51-200 employees
Apr 10, 2019
We've had some issues previously with the performance of the sensors. We tend to deploy quite a bit of WMI, which is quite processor-intensive, and we've found that that impacts the sensors quite a bit.
With custom sensors, there is a lot of work which needs to be done in the background, just for it to be tailor-made for the specific thing that we are actually monitoring. We take a lot of time with the custom sensors. I would like to see the customer sensor be more robust and a bit more varied.
