I was using a free product called Nagios, but it was challenging to deploy, so I changed to PRTG. It's a similar configuration, so I can easily switch using PRTG.

I've previously used HPE and SolarWinds products in the past. 

We used a product called SolarWinds in the past, and its cost was high. Whereas, PRTG came in at a third of SolarWind's cost. 

SolarWinds was limited in terms of its support, as it was agent-driven, so each device had to have an agent installed. Whereas, with PRTG, it just listens via SNMP; nothing needs to be installed on the product. This was a big thing for us in terms of supporting and maintaining it.

We used to have a lot of downtime and have definitely been able to improve that.

I've used FortiMonitor, Huawei, and SolarWinds before. SolarWinds is complicated. An administrator needs more skills to work with SolarWinds. If you're going for a data center or vendor monitoring, it's good to have PRTG set up because it's very reliable.

We implemented the free solution in this company, but it is what I was familiar with. I have used the solution in previous companies before. We did have another monitoring solution, but the speed in which we could get the solution running and my familiarity with it was really helpful.

It was also very easy to take my colleagues through it in the new company in which I was joining. Everyone was quickly on board with it, and we used it as an extra in-depth monitoring on top of our other monitoring stuff.

We experienced network and system downtime before implementing this solution. It was a driving factor in the decision to implement this solution. We had a lot of issues with disk space utilization. We are a quite big company, so we have a lot of people with a lot of files flowing around. We needed an extra level of monitoring on our disks and services.

I didn't use other solutions apart from PRTG Network Monitor. My company had a lot of issues at the time the decision to use the tool was made. My company was blind as it didn't have any monitoring tool, yet it had a lot of sites, internet links, and services. Because I worked on the PRTG Network Monitor in my previous company, I was aware of its performance and that it meets basic requirements and the company budget, versus SolarWinds, which would require a larger budget, so my company went with PRTG Network Monitor. I deployed it within the environment, and the tool works fine so far.

The previous solution that we had (SolarWinds) was giving us a lot of false positives. We were spending a lot of time trying to figure out what was going on. We had used PRTG before, and it has always been a solid platform. 

We were experiencing network and system downtime before implementing PRTG. This was that a driving factor to switch solutions.

J’ai déjà utilisé Nagios, mais il était dépassé. PRTG, en revanche, est incroyablement facile à gérer, à développer, à promouvoir et à maintenir. Nagios, étant très âgé, est difficile à entretenir.

The main driver behind our decision was that we partnered up with a third-party which did all our monitoring for us but we moved away from that. There was a requirement to do it ourselves and that's why we chose PRTG.

We started off using open source, Nagios/Cacti-type monitoring software utilities. Yes, they're open source and they don't cost you anything, but adding devices is quite cumbersome, the management is quite difficult, and the training is more difficult. Whereas, the UI of PRTG is much easier to use; much more intuitive. 

Everybody generally starts off open-source, something that won't cost you much, but they soon realize the limits of open-source. PRTG is a company that has invested a lot of time and effort building it to make easy to use, to give it a nice UI, and to make it as responsive as it is. It's just a natural progression.

The driving factor in the decision wasn't that we experienced system downtime, it was the fact that we needed something more enterprise-oriented and something that was easier to use and manage, which PRTG is, compared to Nagios. When something like Nagios breaks, it's quite difficult to get it working again, whereas with PRTG, once you buy a block of sensors you get some support for 12 or 24 months, and you've got somebody to fall back on if you ever need it.

I did trials of SolarWinds and PRTG simultaneously and decided to go with PRTG because it's user-friendly and easier to understand. 

Prior to implementing this, we had some very basic home written ways of determining things, like remaining space on disk. It was very fundamental and wasn't fit for the purpose. It was for when the business had half-dozen servers, and as we grew, it wasn't. We knew we needed something, so we looked around, settling on PRTG.

There wasn't an incident that lead us to implement the PRTG Network Monitor solution. Obviously, all systems will have issues now and then. We knew we had to put something in place, but there wasn't a specific incident or instance that drove us in this product's direction.

The solution provides us response times to issues, since we didn't have any of this type monitoring prior to putting PRTG in. The product has created a more robust environment. As an infrastructure manager, I am less at the mercy of staff members who are trying to find and work things out more quickly. There are just provided for me.

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

We are looking to take on other products. We are expanding, we are trying to share the two with other departments. As it often happens, the other departments say, "Well, why did you choose this and not something else?" And not
this or that?" Currently, we're looking into potential replacements.

We had sort of massive bandwidth bottlenecks, where our sites used VoIP telephonics. So, when something was throttling the bandwidth for one site, they wouldn't be able to make telephone calls. We had a few instances of that before we got the PRTG product in place.

We knew we need to invest in a new solution because of the amount of time that we were spending manually checking if devices were up or not, then troubleshooting those instances, and where devices went down. We realized that we could have seen these a lot earlier and spent a lot less time on them, thus allowing us to have more time to spend doing actual project work rather than dealing with the break/fix side of things.

I have not used any other solution other than PRTG Network Monitor.

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.

We used to use an old product called Servers Alive. It was good but very basic. It helped every once in a while, but it just didn't have anywhere near the kind of insights that you do with PRTG.

We knew we needed to invest in a new solution because I was getting stressed out and annoyed at the fact that I was getting called out so often, firefighting and fixing and stuff in the middle of the night, as well as doing the day job. I needed another pair of hands to be able to handle the infrastructure that was rapidly growing.

Downtime wasn't really a driving factor in our decision. We just upped and moved to the cloud. We wanted something that could keep an eye on what was going on in the back doors. That was one of the main reasons for the switch. We used to have a data center down in London, and driving down there to fix things up in the middle of the night wasn't exactly ideal. Although cloud is a little bit more expensive, regardless of what people tell you, it frees up time in the fact that you can literally rebuild stuff on the fly now, so much faster than you would if you had to procure servers. Having something keep an eye out to make sure all that is working in the background works for me.

I did not previously use a different product.

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

Our previous solution wasn't aware of what was going on across the environment. It was too focused on server infrastructure. This was a white label SolarWinds product through an MSP.

We had two or three solutions and we wanted to consolidate. One of them was SolarWinds ipMonitor, but I can't remember what the development one was now. They were going end-of-life and we wanted to consolidate, we wanted a single platform that we could work with. In terms of the feature set, PRTG seemed to cover all the bases.

Previous solutions had to many dependencies and were unstable for the most part. Overhead and additional cost of critical features were costly.

We have used other solutions in the past. For monitoring, this solution has been great.

We used other solutions previously but they did not compare in features with that of PRTG Network Monitor.

We have used OpManager. We switched to PRTG as per our customer's request.

We have been using OP Network Manager in parallel with PRTG Network Monitor.

My client is asking me to look into Icinga. Icinga is still new to me and I'm not yet sure about it. I think it's a Nagios software. I did use Nagios before, but I didn't configure it, it was part of the system delivery.

With Nagios, I can't see the graph, or the trends, or the mapping of an individual site. I'm not really sure about Nagios.

We used WhatsUp Gold prior to this solution. There were multiple problems with varying versions and support channels, and there is no standardization or central visibility with all of the instances.

What we wanted was a tool that is scalable and could be used in a modular approach, so we chose PRTG and moved away from WhatsUp Gold.

The time that it took to get the information required to be as proactive or reactive as possible is what drove us to PRTG. With the multitude of products that we had, it was the best solution since it allows us to see everything in one window.

We used the free trial of PRTG. Did a benchmark to see if the product is what we required, then went to the paid version.

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.

I've worked with a large variety of solutions, mainly Zabbix, Nagios, Cacti and Pandora FMS. In this case I resorted to PRTG because the client already had a license for it. One of the times I had to set it up from scratch and the other time I had to take over an installation which was already functioning.

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.

We used a free product, although I can't remember the name of it. It was good but it wasn't giving us the feedback we wanted, especially for alerts. As I said, for our company that's extremely important but we just weren't getting those alerts. We did some research, found PRTG, and I spoke to another company that used it. They really loved it so we went ahead got the free license initially, did a trial, found it absolutely amazing, and then bought it.

We went with it because of a good review from somebody I know, which is always a good start. Also, the price was pretty good, very competitive. Finally, we experienced system downtime before implementing the solution and that was a driving factor in our decision. We needed something to help us stop that from happening, or at least to alert us that it was happening.

We used a different solution before using PRTG Network Monitor, but that wasn't an apple-to-apple comparison. For example, we used an IP monitor from SolarWinds, but that was just a Ping or ICMP utility.

I don't recall using a different solution in the past.

We didn't have a previous solution in place. 

When I started with my company, they were already using PRTG and SCOM. PRTG is more user-friendly than SCOM. I prefer PRTG over SCOM, but it also depends on the use case.

I have used Cisco solutions in the past. The main difference when comparing Cisco and this solution is Cisco supports Cisco Prime and this solution does not. This is the disadvantage if you want to use Cisco Prime. However, this solution is open sourced which has its benefits over Cisco.

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.

We previously used various open-source options like Nagios. They were quite limited and required specific agents being installed on all the hosts. They were slow to roll out. PRTG was a completely different ballgame. It was click and go. It was great.

We are also using Zabbix.

Before PRTG, we used something called MRTG, which was an open source alternative. Previously, it was very clustered, small monitoring systems which were just syslog-based with  big text files. It was alerts generated for just about everything. We had no central way of doing anything, and it got to the point where it was unmanageable. It became a case of needing one solution which could come in and just do everything.

The remote probes are great. We had some base core probes starting up, where they would collapse under the stress and the load. Setting up the remote probes has been great, especially the remote administration aspects of them. 

We were just using the Azure monitoring because all our resources were in Azure. We knew we needed to switch because the service kept filling up in terms of space and the client was alerting us. From a service management point of view, that's horrendous. We needed to the ones alerting the client.

Once we got PRTG on, we were able to not only alert the client, but we were able to rectify the potential issue prior to it being an issue and then alert the client: "We've identified this. We've rectified it. You need to do this."

We did experience system downtime before implementing the solution, but it wasn't a driving factor in our decision to go with PRTG.

We went with it because it looked quite simple. It almost seems too simple. It gives all the information we need. It has that dashboard for alerts on one of our monitors and we get alerts whenever there's an issue. It looked really user-friendly and really simple and it did what we needed it to do. As an IT engineer, you don't really want to be spending all of your time tweaking the monitor. It needs to be a tool.

Prior to the solution, we made use of Zabbix and continue to do so in respect of customers and management. We also tried out another product. 

The company is only about a year old. This was the first solution that we used.

We previously used WhatsUp for network monitoring, but it was more simplistic and did not provide the depth of monitoring that PRTG did.

We haven't used a monitoring system before.

We were actually using PRTG before we were using SolarWinds. From the feature side of things, I don't think that we ever fully implemented and tested PRTG. Then, we started testing SolarWinds and found SolarWinds was giving us a more detailed reporting. So, that is the avenue we went down for actually purchasing a product. We chose SolarWinds, but we still keep a hold of PRTG for its real-time stuff.

We're also using OneView for HPE BladeSystem for monitoring.

We previously used SCOM as a solution and migrated to this because the feature set is quite similar, but it cuts out a lot of the noise and the complexity of the configuration. We started looking for other solutions which would give us something that was easier to configure whilst producing the same amount of information.

We have used SAP ITIM. We switched because PRTG is more cost effective then SAP ITIM monitoring.

In the past, I have worked with a lot of different monitoring tools.

I used Solarwinds, to set it up and tweek took a very long time, and very expensive compare to PRTG.

I previously used Zabbix and Nagios which are problematic performance wise. They're not modern and neither are the interfaces. We prefer PRTG.