PRTG Network Monitor Reviews

We are primarily using this product for alerting. We receive notifications for events like the interface going up or down and remote access, as well as information such as the interface volume.

We're using the basics of it to monitor our switches and routers and primarily just the networking equipment for up-down status.

This solution makes it easy to group devices. It is easy when it comes to dependencies of devices, so if your router goes down, the three or four switches behind it will automatically be paused so that you don't get multiple alerts.

The maneuverability within it is fairly intuitive, especially once you get used to it.

I would like to see them take their graphing tools and convert them into a collector so that we can point telemetry to them. This is a general comment about all of the network monitoring equipment and I think that it would make the product more valuable in the long run. As it is now, you have to point telemetry at Kibana or another open-source solution and then graph out of that. I don't see the point of that, given that I've got SolarWinds and the choice of other network monitoring software. However, none of them allow you to use it as a collector for telemetry, so the stream is part of the switch.

I posed this question to PRTG and they were unresponsive, so it seems like not enough customers are complaining about it or would be potentially using it. But that's where I think in the long term, it would be of benefit. Licensing becomes an issue, and I understand that, but I think that if they could allow a collector of telemetry and re-displaying that graphically, it would be the next best thing.

If you don't have something that is doing the SNMP manipulation then it is a bit clunky, although they have good documentation on it. You can add as many SNMP MIBs as you want to, and it's just a matter of processing them into their format.

We have been using the PRTG Network Monitor for between three and four years.

This is a fairly stable product and we don't have to do a lot of maintenance. They do come out with patches and we're applying them. We do have to occasionally reboot it, although I'm thinking it's not nearly as buggy as SolarWinds. In this version of PRTG, I don't have any issues that I'm aware of.

Scalability is not bad and you can add extra to it. We don't have a scaling issue right now but from what I can tell, it appears that it can scale well.

We have used SolarWinds products and currently use them for backup. We have problems with stability and we fix them by rebooting the device. PRTG seems to be more stable, in general.

One of my senior engineers performed the initial setup. I am doing the maintenance on it along with my engineer. Applying patches if required is not something that we've had an issue with.

It's an annual license that is based on the number of endpoints that we're tracking and using.

We have created several maps for this product, and there is at least one map that people specifically use. It is put up on our wall for the helpdesk, and it has all of the switches and routers in a pie so that you can see what's down and what's up. It is a nice red, green, and blue color coordination. This is displayed along with the utilization of firewalls and our egress points, and some other critical points in the network for the service desk to look at. If they get several calls from a site and they can look up at the map and see that there is a bunch of red, possibly recognizing a network issue, then it is helpful.

I would rate this solution an eight out of ten.

Our primary use case is monitoring when our network fails, when a server goes down or a site goes down. We have five sites.

We're more proactive. Usually, we already know when something has gone down by the time we get the phone calls. When someone says, "We can't log in," or "We can't get on the internet," we probably already know about it.

It makes us, as an IT department, more "time-effective" and if time is a cost then it makes us more cost-effective. Rather than getting 20 phone calls, we can just send an email out, company-wide, saying, "We know this has occurred, we're looking at it." It's cost-effective, time-wise.

Its proactiveness is its most valuable feature. We already know when we come in, in the morning, if a server or site is down, as opposed to someone telling us. Before, we'd have to find out ourselves, check it ourselves, which we were not likely to do, realistically. I wouldn't come in, first thing in the morning and see if all the servers were up, are all the sites were up. It was not the first thing I'd do.

The sensors and remote probes are good. I've used them for a while. The sensors are good because you can change the length of time before they notify you. One of the problems we used to have was that we had it on 30-second alerts, so as soon as there was a slight network blip we would get an email. What's good is that they're adaptable.

Overall, the solution's feature set is really good. I've probably only used about ten percent of it. We use the Ping sensors and the bandwidth utilization sensors. We don't use half of the rest. What we are using is fairly key to what we do.

It probably has this already, but if it had a mobile app that would be helpful. For example, on a day like today when I'm out, if I could just fire it up and see green, green, green, green, green or red, that would be good.

The stability of the solution is very good. We've had no issues with it. It's pretty sound. It always works. I can't really fault it.

It is scalable. We've only got a small infrastructure, but if we had a larger infrastructure it would be fine. We probably only monitor 20 to 30 devices on it. We could do more but we don't.

I've never used their technical support, but I suppose that's a good reflection on the product itself.

I've used it for quite a while. I just played around with it initially, it's pretty intuitive. I might google the odd problem I've had with it, and how to do this, that, and the other but most the time it's intuitive enough.

We had system downtime before implementing the solution. I've been where I am now for about eight years. Before, there were issues all over the shop. I walked in and we had servers that had no disk space, which this product can look at. We had issues with poor connectivity to certain sites which this will obviously flush out.

One of the reasons we went with it is because I had used it before.

The only downside - and it's a minor thing - is when I've uninstalled it. I usually install it on a server to use the probe. When you uninstall it, it requires a reboot and sometimes it doesn't quite warn you enough that it's going to reboot the server, so you have to be very careful.

From the time we set up solution until it provided with us with feedback on the infrastructure was 20 minutes. Install it and it's working 20 minutes later.

It has a free trial so I would give it a go, you have nothing to lose really. Just try it. It doesn't take long to set up.

I rate PRTG at eight out of ten. I wouldn't go higher because I haven't investigated it, used it fully-optimized. But I'm really happy that it does what it needs to do.

We're using PRTG for network, asset, and infrastructure monitoring. I have five network and infrastructure engineers using the solution, and we're not using it extensively. It's one of our secondary monitoring tools.

PRTG gives us true visibility of the downtime of particular circuit functions. So if a circuit is up but not routing traffic, I will know with this tool. I can write a customized script for a sensor to detect specific things.

One useful feature is PRTG's scripting ability. We can go into the system and create monitoring sensors, for lack of a better phrase. So I can look for something specific instead of just uptime or downtime on a specific asset.

PRTG's documentation could be improved.

I've been using PRTG Network Monitor for about a year.

PRTG's stability is fine.

We're not that big of an organization, so I can't say much about scalability, but we've had no problems with it.

I've had no contact with PRTG support.

In the past, we used SolarWinds. We switched to PRTG because it was more scriptable and customizable.

Setting up PRTG was straightforward and took a few hours.

After the initial acquisition cost, the license is about four grand a year.

I rate PRTG Network Monitor seven out of 10. If you are considering PRTG, you should take into account the fact that the data is going up into the cloud in a private, isolated console or a tenant in a multi-tenant environment. Just be aware of what you want to look for and know how to get it in terms of status, uptime, etc.

We use it to monitor services, things like hardware usage and whether hard drive space is running out. We use it for quite a lot of our networking solution as well. If there's a glitch in the network, anything that's abnormal, being able to see that show up is quite good.

The historical data provided by the solution helps optimize our network performance. We can see what's going on in our network infrastructure, more so in terms of our core networking. We can see which fiber links have been used heavily and, if they are used heavily, we can introduce more links to particular buildings or particular areas. It's more around the networking that we use the historical data. 

Also, if we have any issues with particular hardware, we can monitor those. We can monitor the network on those ports and come back with any issues or see if anything is flipping out or has stopped working. It's helpful being able to see that historical data.

It makes us more proactive, as opposed to reactive, with any issues. We tend to see issues occur before anyone else even knows about them. That's really useful for us. Particularly if there's any abnormality on the network, because of the historical data, we tend to know about it. PRTG tells us about anything that's out of the ordinary, which is good.

The sensors work well.

The remote probes seem to be a little bit buggy at times. They just stop working or they say they can't communicate. What we tend to do to is install the remote app onto the servers that we use. That seems to clear it up. As long as the app is there, all the probes seem to work fine.

It would be nice if, for the maps view - what you can lay out on the screens - there were a bit more functionality. It would help to be able to add titles to the top or to be able to change text sizes. There's not much you can really do with that in terms of configuration at the moment.

The stability has been good since it went in. It's never had any issues. It has just worked. It updates itself, it's easy to manage, easy to maintain.

It's difficult for me to judge the scalability. For what we use it for - I think we've got 1,000 sensors and we use about 800 or 900 at the moment - it all runs fine. I'm sure it would scale very well if we needed it to go any further than that. But for what we use it for, it's relatively small.

We haven't used the tech support or the online resources. It has always just worked; it's always been fine.

We have a third-party we go to if we get stuck with our network and they recommended PRTG. They actually started using it to troubleshoot some issues on our site, and from that, we decided it was something we wanted, so we invested in it from that point and set it up from scratch.

There wasn't really any system downtime which factored into our decision, but there were a few performance issues which PRTG helped us to solve. That was another reason to get it put in place, long-term.

The initial setup was surprisingly easy, the way the menus are all laid out. I set it up myself and it explained what to do, where to go. There were little pop-ups on the screen saying, "This is where to go for this, that's where to go for that." It made it all really easy to do. 

Also, adding servers or switches, it was auto-discovery, so I didn't have to do any config on that. You could just let it discover everything and then delete what you don't want.

It took about two days from the time I set up the solution until it provided feedback on our IT infrastructure.

PRTG was recommended to us and we went with it on the free basis to start with and then we moved to the paid version, for more sensors. We haven't really compared it to anything else, because it was recommended. Overall it seems very good.

Just install it, follow the instructions, and off you go. It just seems to work.

We do use the Desktop app and it's good, it works very well. It's very similar to the web-based system. It gets a little bit annoying sometimes because there are quite a lot of pop-ups. I'm sure we could turn them off but that's not something we've looked into. I actually find myself exiting the Desktop app, just to stop the pop-ups.

I wouldn't say that it has made our IT department more cost-effective at this point because, although we pay for it and we use it, we haven't really made any changes on the network because of PRTG. I don't think we've had any cost savings anywhere.

I would rate it eight out of ten. The desktop app seems a little clunky sometimes. There are a lot of pop-ups saying things are offline when they're not necessarily. That's more due to those probes. When we install the app on the servers there're no issues there, so we can get around that.

We use it to monitor our servers. We try to monitor all of the functions the servers as closely as possible.

The historical data provided by the solution allows us to look back in time and look at the baseline performance of the sensors. We can compare them over time to see if anything has gotten worse or improved. The data helps us optimize network performance.

It allows us to be more proactive when monitoring our infrastructure. With PRTG, we normally know of issues with our servers before anybody reports them. We used to be very reactive, but now we are alerted instantly. We've got hundreds of servers, so it's impossible to monitor them manually.

It definitely enables our IT department to be more cost-effective because we don't waste time checking things manually, which can be quite time-consuming. It frees us up to concentrate on the issues that we've been alerted to through PRTG.

The solution also provides us with defined measures of performance so we can see whether it has improved or decreased over time. We can then improve our infrastructure. We can measure that using PRTG.

Some of the valuable features include the following.

• Ease of use. The authentication links into our standard Active Directory authentication, which is very good.
• It's got a wide variety of sensors that can be applied to many different aspects of the service to monitor them. There's a very good selection.
• The remote probes are very useful. They allow us to provide a reference across different areas in the network. In trying to localize issues, that's very useful.
• It's web-based, which is a big advantage when you can access it from anywhere. 
• It's very reliable.
• It's independent of other equipment, so it's not going to fail due to anything else failing in the infrastructure.
• It's got apps as well, so it's accessible, even on your mobile.

It's an excellent product. In terms of the overall feature set, it has a lot of features. It can monitor a wide range of aspects of our equipment and it has a lot of options for alerting.

It's very good for monitoring our internal infrastructure, but we're using more cloud services now. It would be useful to be able to get information back from these cloud services in detail, and display any issues within PRTG for the rest of our systems.

It's very stable. It has to be when it's monitoring for failures in other parts of the system. We've had very few issues with stability. It's been very good.

It allows us to easily increase the number of sensors and the scope of what we can monitor. The scalability is very good. It grows with our business. We initially bought a set number of licenses and then upgraded it and bought additional server licenses to monitor other things in the business.

We haven't had to resort to contacting tech support much over the years that we've been using it. When we have, they've always responded quickly and been very good at helping to resolve any issues.

We didn't have a previous solution in place. 

It was very easy to set up a trial version of the server and evaluate it for a period to see what we could get out of the product.

The time from setup of the solution until it provided us with feedback on our IT infrastructure was quite quick. Before the trial was over, we already had a lot more information than we had had before. It was worth definitely the cost of licensing it and paying for it.

We did it ourselves. It was so easy.

I'm not involved in the commercial aspect of the solution, but the pricing is very low compared to other solutions.

We evaluated a number of different server monitoring solutions and selected PRTG as the best solution to go forward with. We looked at WhatsUp Gold and Nagios. PRTG was much easier to use, configure, set up, and get running. It provided better information which was very well displayed.

We also had downtime previously. That was definitely why we went ahead with a monitoring solution, so we could be alerted quickly to any issues and resolve them before they affected our service and users.

I would recommend trying PRTG and seeing the benefits.

We don't tend to use the Desktop app because the web-based interface is so good. I really don't have a lot of experience with the Desktop app.

I would say the product is a nine out of ten. It's been very successful and done exactly what we wanted it to do.

We use it for network monitoring, mostly. We look at any metrics that the sensors pull back for us, such as availability, performance. We have some custom sensors for service monitoring.

The solution's historical data helps us optimize network performance. We can find issues by looking at historical data and benchmark it against what it should be.

It's given us metrics which we can then pass on to customers, availability statistics and things like that. It's really added value to the services we provide. From that point of view, it has definitely improved things.

It makes our IT department more cost-effective because we can detect failures faster, we can do something about them. We can get early warnings on things that are going to go wrong, be proactive about dealing with them, and have less downtime.

It gives us the needed feedback on our IT infrastructure, such as utilization of disks on a server. We get that information back and are able to act on it.

One of the valuable features is the diversity of metrics available to us to monitor. It's all there, it's all in the box. It's all made very easy, by virtue of it being pre-configured. You point it at the box, pull your credentials in if you need to, and off it goes and does it. A lot of solutions do that, but this just has it all in one box, which is what makes it really good.

The solution’s sensors and remote probes are great, spot on. They keep improving them. It's only a problem from time to time when old sensors get deprecated and you have to replace them with a new one, but other than that it's a very good selection.

The overall feature set is good. It's diverse, it's all there.

I don't think the Desktop app is that great. I don't like it. I would like to see cross-compatibility on different platforms. Also, the window management isn't that great, and the refresh rates aren't that great.

Their roadmap is good and the features that they're releasing are good, but our main ask is around the scalability issue that I've mentioned elsewhere in this review.

If you have enough resources the stability is fine, fairly rock-solid. We're at double the recommended capacity in terms of sensors for our instance, and it's running fine.

Scalability is the only major sticking point for me. There is a recommended number of sensors, which is around 10,000, and we're double that. We're not comfortable putting any more than that, even though the server might be able to handle it. It's already well outside the support boundaries for the solution. 

The only option we have to scale is to buy another core, which would be a separate, stand-alone instance, would not be managed through the same interface, and we would have to be looking in two different places. We love the product, but at the moment that is the main sticking point for us.

There have been no real problems with tech support. We don't really need to go to them, the product takes care of itself. When we have needed them, they have been very responsive and gotten back to us quickly.

We did have system downtown before implementing the solution, but it didn't really influence our decision to get PRTG. We needed a monitoring system anyway, by virtue of the nature of our business.

We would have been using an open-source solution before PRTG but we needed a more feature-rich product to work with, given the number of solutions we were operating.

The initial setup was very easy. There's nothing much to do, honestly. You just install the software on the core server and then you can install remote probes in any private sub-nets that you need and they will speak back to the core. It's very straightforward.

Within about a half an hour of installing it, we had information back.

We did it ourselves.

Subjectively, it probably has saved our organization money, but it would be difficult to quantify it.

We pay for a perpetual license and we have a support fee.

We've had PRTG in place for a number of years, so what we evaluated was in the early days, a lot of open-source solutions: Zabbix, Nagios, Cacti, etc. PRTG is differentiated because it caters to all platforms and endpoints, has features for Windows, and WMI sensors which aren't necessarily available out-of-the-box in the other solutions. That would have been a determining factor.

It will do the job, more than anything I can think of. It will give you really useful monitoring statistics out-of-the-box, and will give you the ability to customize and do things that aren't there by default. It will take care of all your monitoring needs, pretty much, but just be conscious of scale.

I would say PRTG is an eight out of ten. We're very happy with the functionality. Those missing two points come from the scalability issues.

We are using PRTG Network Monitor mainly for real-time monitoring and communication in our environment.

The most valuable feature of PRTG Network Monitor is real-time monitoring.

PRTG Network Monitor should improve the NetFlow dashboard, there is no flexibility, and the NetFlow is not meeting the business needs. Additionally, they are missing part of the configuration management.

I have been using PRTG Network Monitor for approximately six years.

PRTG Network Monitor is stable.

I did not face any issues with the scalability of PRTG Network Monitor. However, I did not test it.

There are approximately 17 administrators using this solution in my organization.

I have not needed to use the support from PRTG Network Monitor.

The initial setup of PRTG Network Monitor is simple. It took approximately 15 minutes to deploy.

We did the deployment of PRTG Network Monitor in-house.

There is a license to use PRTG Network Monitor and it is annually.

We have evaluated a lot of software and we found PRTG Network Monitor the best solution.

It's a good solution regarding real-time monitoring only, but for the site of the operation, you can't rely on it without any other solution to fit all use cases.

I rate PRTG Network Monitor a five out of ten.

We use it specifically for our network devices and service providers. We're able to know if the connection with a certain internet service provider is still alive.

It is able to satisfy all our requirements in terms of email notifications and specific errors on the devices.

I would like to have a VM version that can be installed on a cloud such as Azure. We're using Azure, and we're eliminating on-premise servers. It would be helpful to have a PRTG version that can be installed on the Azure cloud.

I have been using this solution for five to six months.

It is stable. So far, we didn't have any problem with the product.

We're using the free version, and we can only enroll up to 100 sensors. 

Currently, we have two system administrators who use this solution.

We didn't use their support. We're using the free version.

We were using SolarWinds. SolarWinds is much more expensive than PRTG.

For those who have no experience with PRTG, it would be quite complex. Luckily, we have an experienced and knowledgeable staff. Our team did not encounter any problems. The whole set up took two to four days.

We set it up ourselves. We had two system administrators for its deployment.

We are using the basic PRTG that we can download for free. For now, we only need to monitor less than 100 devices. For more than 100 devices, we would need to buy a license. PRTG is much cheaper than SolarWinds.

I would definitely recommend this solution. I have friends in other companies who are also using PRTG, and their feedback is also good.

I would rate PRTG Network Monitor an eight out of ten. We're happy with the results.