What is your primary use case for PRTG Network Monitor?

We use PRTG Network Monitor for monitoring traffic on interfaces and the behavior of network traffic. If there are sudden changes in traffic or any configuration issues, we can sort them out using PRTG. It's very helpful for troubleshooting and monitoring traffic utilization on our interfaces.

I am a partner company and use PRTG Network Monitor as a monitoring tool for our customers. We use it to monitor entire IT infrastructures, like AWS devices, and other IP kind devices.

The solution's use cases depend on the number of interfaces you want to monitor. You have to calculate the values by referring to the licensing prices publicly published on their portal.

We use the product for network monitoring.

I use PRTG Network Monitor to monitor server and network environments in my company.

We use the solution for monitoring the bandwidth and reachability of a big network. We rely on reachability to generate an alarm as banks have different branches and routers. We use the PRTG to assess whether there is any fault in any branches or ATM buses. We have been using a site with 5000 sensors in 60-78 sites.

The solution is used for infrastructure monitoring and for some limited automation and SNMP monitoring. If any parameters cross any threat, then it would trigger some healing, like restarting by sending some special commands.

I use the solution to monitor the availability of devices and check if ping has generated ICMP requests.

Our primary use case for this solution is for every computer operator in my data center to be able to easily operate and use devices.

We use PRTG as part of a general support platform we offer to our clients. It provides a single pane of glass to monitor network hardware and software and head off critical incidents.

Our use case is limited.

We use the solution to monitor customer sites.

We're using PRTG Network Monitor for server-level monitoring and network-level monitoring, and in our network, we have switches and firewalls. We're also using the solution for bandwidth monitoring and internet link monitoring. We're also planning to use PRTG Network Monitor to monitor CCTV and other IoT devices.

If you want to grant access for clients to the MSP service provider, you can use this solution. For example, if the client wants to monitor the net flow and net flow traffic with PRTG, you can analyze this traffic for them.

We are mostly using PRTG Network Monitor for monitoring servers, and switches. For example, we monitor uptime on critical resources.

We use it to monitor our network because we have a central site that connects to many remote sites, and we have primary and alternative links. We need to monitor both links for each site to be able to react when it is necessary in case of failure. It is beneficial for us to check the connectivity and bandwidth used in a particular channel.

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

Our primary use case for this solution is monitoring all our live servers, their resources and networking equipment like firewalls, routers, switches and network switches. Additionally, we have a bandwidth monitoring map deployed in PRTG Network Monitor to monitor our internet bandwidth continuously. The solution is deployed on-premises.

PRTG Network Monitor is used by network monitoring teams for keeping a tab on services that are down. Once you are aware of a failure you are able to quickly reinstate the service before customers or brand users notice. This can be done even before the service is down, if you see a pattern of service degradation, it can quickly attend to it.

Our use case for PRTG Network Monitor was end-to-end monitoring, but we couldn't achieve it, particularly the monitoring from the perspective of looking at the complete dashboard of the entire infrastructure, though it's a server virtualization network. For example, monitoring any device, even a swiping machine or a camera, or any device which comes and adopts an IP address should be monitored using PRTG Network Monitor, so that was our use case in the beginning. Eventually, we then wanted the tool to also monitor our applications, so our current use case for PRTG Network Monitor is to monitor applications residing on our infrastructure, apart from devices that use or adopt IP addresses.

PRTG Network Monitor is used for monitoring internet service providers, and we want to receive the downtime of the network devices mapped. PRTG Network Monitor is hosted in a local host server in our three data centers.

I use PRTG Network Monitor to monitor network devices, routers, switches, servers, applications, and services.

We are using PRTG to monitor networks, applications, and databases like Oracle Database or SQL Database. Now we plan to use PRTG for IT aggression management. Though it's not suitable, I think we can also use PRTG for operations monitoring. We will make a dashboard in PRTG and use it to control when we have a problem. We can analyze which part has a problem so that we can analyze and report to our SQL. We have about 10 to 12 people in the IT department working with PRTG.

We use this solution for security and supervision of our network. There are two people using PRTG Network Monitor in my company. The solution is deployed on a private cloud with Microsoft Azure.

I have experience in configurations and troubleshooting, and I use PRTG Network Monitor for network monitoring activities, e.g. monitoring the bandwidth and where it's coming from. For example, I use NetFlow instead of SNMP only. We had a big amount of bandwidth being used, and I wanted to check whoever was using that amount of bandwidth. We managed to find the source IP address of who was using that specific bandwidth amount, with the help of PRTG Network Monitor.

We are using PRTG Network Monitor for performance monitoring. We use it to monitor traffic and to identify network issues. In our school, the network is slow, so we use PRTG Network Monitor to capture the network and traffic status, and through it we found out that one of the servers is sending out messages.

We use PRTG network monitoring to monitor our server, especially for computing resources.

It's a globally distributed network. We have multiple data centers or IT setups, and PRTG is deployed at the local data centers. Some of the applications are in the cloud, and PRTG can also monitor those.

We use PRTG Network Monitor for network monitoring. We mainly monitor uptime on our switches and our network environment, and we're looking at expanding into server monitoring as well.

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.

Our primary use case is for monitoring numerous services; internet providers, university campuses, etc. We are resellers.

We are using this solution for the health check of our infrastructure.

While I cannot say for certain, I believe we are using the latest version. We use it for monitoring network devices and downloads.

We primarily use the solution for monitoring.

We primarily use the solution for applicative monitoring, or network and applicative monitoring for some customers so that they can make sure that all equipment is up, and sometimes we use it to look for some more accurate sensors.

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.

We are a service provider in the IT industry, and this is one of the products that we implement for our clients. We are using this product ourselves, and we have several customers who are also using it. It is basically used for monitoring alerts, such as memory from a server has gone down.

We use PRTG Network Monitor for connectivity and communication between devices.

Our clients use this solution to see if the network is up and running, for pings and services such as emails and disk space.

We primarily use the solution in order to monitor the network performance and stability.

We use the solution to recollect data from past equipment.

The solution is for network monitoring.

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.

We use it for some internet providers and educational institutes.

Within our organization, only the network department uses this solution — there are eight of us.

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.

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.

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.

We have deployed this solution on numerous platforms.

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.

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

We use it for monitoring items on the network: switches, servers, and other devices, to guarantee or at least monitor uptime.

We use it to manage our systems internally. At some point, we will be offering it as a managed service.

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.

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.

Monitoring of all our disparate sites through a central console is our primary use case.

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.

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.

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.

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 use it mostly for monitoring our servers, network equipment, firewall, etc.

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.

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.

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.

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.

It provides a consolidated view of servers, switching, and network connectivity for the offices that I look after.

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.

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.

* 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.

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.

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.

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.

We use this solution for monitoring servers in our data center. It performs pretty well.

We sell the product to customers and handle their problems. From every problem that we handle, we learn from it. As a company, we deploy WiFi network in major hotels (four or five star level). The guests who come to stay in those hotels are very sensitive to availability and performance. So, we have to monitor the bandwidth high availability, as well as the basic infrastructure, such as checking the system and all the IT infrastructure in those hotels. Today, we have a lot of customers, hundreds in India and neighboring countries, Sri Lanka and Bangladesh. Some of our customers have taken us to Malaysia because they did business with us in India. We also work with two countries in Africa, Congo and Nigeria.