PRTG Network Monitor Primary Use Case
I use PRTG because I have six clouds around the world, a mixture of our own and our customer data, so I need to know when it's all up and running and when it's dead. My team is the main point of call for all the infrastructure around the world. I get called out at all times during the night and day, including this morning at five am. View full review »
* We run two data centers and are a hosted voice provider. * We have an Azure presence. * We use PRTG as a monitoring solution to effectively monitor all of our servers, routing infrastructure, and switches. * We have some Session Border Controllers, which are effectively Voice Firewalls. We monitor the uptime and availability of those via things like Ping. However, we are also using SNMP sensors. * We've written some SQL queries that PRTG is utilizing. * We check things, like error logs, through PRTG. * We are feeding things, like system log messages. * We use SNMP Traps. View full review »
We use it to manage customers and to keep an eye on when stuff goes down or when stuff is not working as intended. We monitor mostly servers, but we use it to monitor websites and some of the network infrastructure as well. View full review »
Learn what your peers think about PRTG Network Monitor. Get advice and tips from experienced pros sharing their opinions. Updated: January 2021.
456,966 professionals have used our research since 2012.
The primary use case is for monitoring infrastructure: servers, printers, endpoints, and certain services on certain systems. We are alerted in regards to any issue with them. View full review »
PRTG is a very versatile and flexible tool. We have a vast number of users spread over more than 300 installations in India and neighboring countries. We have many different types of customers who use this tool for project control monitoring and other types of network monitoring. View full review »
We use it to keep an eye on the equipment we've got out there. We've got a Citrix farm which we shut down on an evening. We have alerts to tell us if they haven't come back up. View full review »
We use it to monitor our critical infrastructure, i.e., the services our users depend on. It is very useful for us to have that holistic view, e.g, one single view of the dashboards. The product is a useful kit to summarize the health of our infrastructure. View full review »
Our primary use case is network performance monitoring, but we also use it for things like network traffic flows and getting a better idea of the actual types of traffic that are going through our network. View full review »
I look after the infrastructure side of Lookers. We have 8000 users, 400 various servers, and 190 sites. We've been rolling the product out and are relying on the infrastructure purely for the whole of our business. View full review »
We primarily monitor Windows-based servers and services running within them. We also have some ties-in scripting into more bespoke areas, as well on our network. We host a virtual environment running VMware in-house. View full review »
We use the solution for full network monitoring, to manage our entire estate; that includes things like disk space and network usage. It alerts us of any potential outages so that we can attend to those before they occur. View full review »
We use it mostly for monitoring our servers, network equipment, firewall, etc. View full review »
We use PRTG to monitor all of our business critical and distributed systems around the areas that we operate in the UK. This is ensure they have good system uptime and can demonstrate against SLAs. View full review »
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. View full review »
PRTG has been a network monitoring solution for our company for over five years now. We constantly monitor our servers, switches, broadband. Anything that we can put a sensor on, it monitors. I monitor four domains and I use cross-domain network monitoring as well. View full review »
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. View full review »
The primary use case if for monitoring bandwidth, uplinks and using SNMPs. We are slowly scaling out to monitor hard drive disk spaces, as well. Our bandwidth solution, which are the uplinks that we have at the moment for circuit breakouts, and ISPs don't give us the best information. So, we use what we can and monitor the uplinks before they hit the equipment. View full review »
We use it for monitoring items on the network: switches, servers, and other devices, to guarantee or at least monitor uptime. View full review »
We use it to monitor our servers. We try to monitor all of the functions the servers as closely as possible. View full review »
It is for monitoring the up/down of our core infrastructure: Internally, the edge routers in our major occupancies, core switches, access switches, etc. It sort of give us real-time feedback for what is going on. We use it to determine if a switch is up, our traffic is running optimally or at a normal rate. View full review »
The solution is for network monitoring. View full review »
It provides a consolidated view of servers, switching, and network connectivity for the offices that I look after. View full review »
Our primary use case with PRTG is measuring and monitoring the system. We have a few servers running in redundancy. There are two monitoring ones. One for the maintenance staff with more details and the other one is for general control and assessing when there is a user error or 401. We use it on the business logic level. With redundancy, the FRC is just to monitor whether there is a complete down or only one system goes down. We see everything being monitored on the screen. When we do mapping it's easier for us to monitor whether it's the server's fault, the feature's fault, or it's the router, or some other device, or some other legacy system. It all starts with the monitoring. View full review »
Monitoring of all our disparate sites through a central console is our primary use case. View full review »
We use it to manage our systems internally. At some point, we will be offering it as a managed service. View full review »
Our primary use case is monitoring when our network fails, when a server goes down or a site goes down. We have five sites. View full review »
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. View full review »
We have deployed this solution on numerous platforms. View full review »
We use the solution to recollect data from past equipment. View full review »
We primarily use the solution in order to monitor the network performance and stability. View full review »
We have offices around Australia, we're a company organization with a couple of hundred people where we monitor four or five offices and their networks. We use the solution on a daily basis. We're a customer of PRTG and I'm president of our company. View full review »
We use it for some internet providers and educational institutes. View full review »
We use this solution for monitoring servers in our data center. It performs pretty well. View full review »
Within our organization, only the network department uses this solution — there are eight of us. View full review »
Learn what your peers think about PRTG Network Monitor. Get advice and tips from experienced pros sharing their opinions. Updated: January 2021.
456,966 professionals have used our research since 2012.