PRTG Network Monitor Downtime
Did you experience any network or system downtime before implementing this solution? If yes, was it a driving factor in your decision?
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.View full review »
PRTG been great. It has let us know when a few of our SX servers have been having little issues, things you wouldn't necessarily notice under the covers unless you started hammering the system. It's definitely prevented downtime which, at the end of the day, is what we're after. It's done well.View full review »
Finally, while we hadn't necessarily experienced downtime, we were having issues with stability in the network. Some of the output from PRTG helped to narrow down where those issues were coming from, so it gave us a much clearer idea of where we need to go.View full review »
The time that it took to get the information required to be as proactive or reactive as possible is what drove us to PRTG.View full review »
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.View full review »
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.View full review »
The driving factor in the decision wasn't 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.View full review »
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.View full review »
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.View full review »
One of the things which became apparent was that we didn't know when things were going down out of hours unless somebody sat and was there watching the consoles. Nobody knew when things were going down. Now, one of the things that we've noticed is we are picking up when we are having out of hours outages. The solution is starting to correlate data so we can speak to the relative representatives and make sure the outages stop happening.
We were experiencing network and system downtime before implementing PRTG. This was that a driving factor to switch solutions.View full review »
We used to have a lot of downtime and have definitely been able to improve that.View full review »