We use Auvik to monitor our whole network infrastructure. It helps us keep track of issues that arise and things that go offline. We have one main corporate office here that has multiple buildings and a lot of private fiber.

We have 68 access points, 46 switches, and 240 employees. Every person here utilizes the network on a PC, iPad, or iPhone. All of our CNC machines are on the network. That adds up to about 600 total devices on the network, including everything with an IP address. 

We are an MSP that monitors various customers' infrastructure, including firewalls and switches. We use Auvik for monitoring and creating network diagrams. Our environment consists of a data center with VPNs for each site we monitor and manage. 

From the data center, we have a probe where we can access every device we manage. We authenticate in the cloud and access the monitoring on-prem.

When I started working with Auvik, I was working for a managed service provider helping several clients manage their network environments. We tried Auvik and decided to stick with it. It is used for network monitoring and different troubleshooting issues.

We use Auvik to monitor our customers' networks for performance and availability.

We use Auvik for monitoring networks across all of our sites for alerts, reporting, configuration backups, and troubleshooting. Auvik does a little bit of everything when it comes to networking.

I'm not the only person that utilizes Auvik, but I'm the only network engineer. The infrastructure team uses it for server monitoring. Security guys can also access it, but I'm the primary caretaker.

I monitor 34 sites with 200 managed devices, and about another hundred are unmanaged. Altogether, I have over 2,600 devices that are not networked. If you subtract the network from that, it's about 2,300 devices that aren't network devices, including printers, servers, and computers. Auvik crawls and finds those kinds of things on the network. That's what I mean by total picture.

We've primarily used Auvik for:

• network monitoring,
• mapping out client networks,
• and being able to get remote access to networking equipment.

We use Auvik to monitor net flow within our primary core switch and firewall. We look at the health and traffic flow alerts from our wireless access points or switches.

We don't use any of the automation features. Our company uses Auvik strictly for managing alerts. Auvik acts as a dashboard to give us oversight and a sense of the overall network health. We don't do a lot of troubleshooting within Auvik. It's more of a documentation and dashboard tool that lets me see all the problems and drill down.

We only have one location where we're using Auvik, but we're expanding to a second location under construction and being rebuilt. We'll eventually have two more locations. We want to monitor multiple sites and how they interact because we use SD-WAN between the sites.

The solution helps us get a granular understanding of our environment, all the way down to the endpoints, to Azure, the networking, and all of the networking equipment, whether it's the access points, the firewall, or the switch. We can identify any latency or drops by keeping an eye on the network.

We needed SNMP monitoring for several clients and network devices. Auvik is for availability monitoring of network devices, like switches and routers. We also use it for monitoring CPU and a few other functions, but it's mainly just for the availability of our high-priority clients that require 24/7 alerts.

Our entire company uses Auvik, and it's deployed to customers willing to pay for it or customers of a certain size. The environments vary. Some of our clients are in education, government, and the private sector. Some clients have one massive site, but it's also used in companies with multiple branches around Australia. They range in size from 20 network devices to 2,000. We deploy it to any client who will buy it. Otherwise, we can't guarantee that we can monitor the network. Nearly 75 percent of our large customers have adopted it. Internally, about 90 staff members have access to Auvik. 

We're an MSP. We use this solution for all of our clients. For anyone that has a network more extensive than a switch or two, we install Auvik. We do this to make sure that we're getting the right connectivity and that everything is working as it should. I get alerts whenever something goes wrong, and I can jump in and say for example, "That's there. This is why." And I can tell what is happening. If I'm not on site, I can say, "Plug this port in because whoever was there, just plugged it back into the same switch." 

I use Auvik to create a network topology map for my business, which also serves as a monitoring tool for any downtime or issues within our company's network infrastructure. As a production company, we require continuous operation, so a tool like Auvik provides valuable visual insight even when I'm not physically present.

We previously had a basic alerting system in place, but it was not sufficient when we experienced networking issues within one of our two buildings. Often, it was unclear which cables were connected to which devices and where the connections led. Auvik, unlike other tools I've used, excels at visualizing these connections, making it easier for me to identify the source of the problem.

We use Auvik to monitor our client's infrastructure. It gives us real-time visibility into the devices, their status, and their availability at the device and interface level. Auvik monitors bandwidth utilization, TPU utilization, RAM, memory utilization, etc.

Auvik is deployed in a mesh environment consisting of five locations and the data center. We'll be moving toward Azure, but I'm not sure how well Auvik could cover us in that space.

Our primary use cases are network management and configuration backups. The solution is deployed across 1,500 to 2,000 devices, and we have multiple clients as an MSP. The tool is multi-tenant within our environment and deployed across VPNs and numerous sites. Our clients range from small family-owned businesses to enterprises.

We implement Auvik for our clients as a network monitoring solution. About 20 engineers use it, including me. We also have a business analyst, a systems admin, a capacity planner, two vice presidents, and a couple of data scientists.

Auvik is deployed across several departments. Organization-wide, we have 20,000-plus endpoints, but Auvik is monitoring a tiny subset of that, so about 2,000 more or less. 

Auvik is our primary network management tool. We utilize it to ensure all systems and remote sites are seamlessly connected to our central office. While its core function is network management, we leverage its capabilities for deep-dive technical analysis when needed.

In our setup, Auvik itself is deployed in the cloud. I'm not sure if they have a hybrid or on-premises option available. However, we do require a collector, which is a virtual server we own. This server stores data that Auvik accesses for network management and discovery. If the collector goes down, Auvik won't be able to report any information to the cloud. Although I manage everything through the cloud interface, I never need to log into the collector itself.

It has got a lot of use cases, but in my opinion, it's probably the best full-stack network monitoring management and alerting platform that's out there for routers, switches, firewalls, and non-server infrastructure.

We use Auvik to discover devices on the network, to get a good layout of the network, and to have the solution back up the configuration of certain network devices.

I was looking for a solution that we could use to catalog and keep track of our inventory. I thought about using Auvik in our lab environment to see how it would work for tracking inventory in a production setting.

We are using Auvik specifically for monitoring network devices. We are an IT company that's focused on network integration and monitoring for our customers. We use Auvik to monitor routers, switches, firewalls, load balancers, and other network devices.

We're a managed services provider using Auvik for network management of firewalls and switches. We use several tools alongside Auvik, which we primarily utilize for network mapping and managing communication between switches and firewalls. Our clients are set up on tenants within the solution.

Auvik enables us to make comprehensive network diagrams of the various companies that we manage. It gives us complete visibility into the network infrastructure, but we use an RMM for some of our other items. It doesn't replace the RMM or stuff like antivirus.

Our tier 1 support techs generally do not use Auvik because they're handling basic tasks. Auvik's interface is intuitive, but you need to know what you're seeing. Tier 2 and tier 3 engineers have the understanding needed to delve into the information Auvik provides. 

We're an MSSP serving many customers. Auvik is one of a set of tools that we offer our clients, including network monitoring and management, SIEM, and endpoint protection. They buy the bundle and get access to Auvik. 

We use Auvik for network monitoring, availability, and troubleshooting. The solution provides asset visibility and inventory management. Most people don't know what they have and where it is. They also use it to centrally monitor remote access from multiple sites. 

We have several different physical sites and we run our own network. Auvik has some exciting capabilities for aggregating Syslog from switches and having remote console administration across geographic locations. The solution puts a common off-wall in front of switch management but also makes it easy for us to go in and make changes.

We use the solution across multiple locations and departments.

We use Auvik where we have the most pain points because it's a charge per device brought online model. We use Auvik in a smaller proportion of our infrastructure, around 30% of our architecture.

It provides comprehensive visibility into your network infrastructure, automates network mapping, sends timely alerts for potential issues, and facilitates configuration management. With Auvik, you can receive notifications directly, ensuring you stay informed about the health and performance of your network.

When I integrated Auvik, the primary goal was to uncover issues that might be occurring without my awareness. Essentially, I wanted to identify potential problems before they escalated to a point where I became aware of them, often when it was already too late. I sought early warnings for network issues to proactively address and mitigate them.

We use it for everything from alerting and monitoring. We have had some use cases where we had to do some forensic type of work and track down devices at locations that were breaking policy and things like that. It was pretty handy because we were able to grab some identifying information from the device, and it took about 15 minutes to figure out where the device had been every day for the last seven days.

I have used Auvik for a comprehensive range of monitoring tasks, from managing network infrastructures to overseeing the health of our servers. It has proven invaluable for resource monitoring, and I have even employed it to monitor printers. Throughout my career, Auvik has been my go-to solution for monitoring virtually everything.

We didn't have strong visibility across our network devices. Auvik solved our visibility problem.

We used it for network monitoring and network health. We had it deployed at all of our sites. We are an MSP, and we've got about 30 different managed clients. All of them had an Auvik collector at each site to monitor the network for changes or infrastructure health. We have an RMM solution for remote monitoring and management of our workstations and servers, but that tool doesn't monitor network infrastructure. 

Our use cases would be mapping our network automatically, monitoring events to get stats and trends, spotting any impending issues before they get noticed by our users so we can address them, and doing device reconfiguration. 

We're in the healthcare industry and in our organization we have what we call a "backup machine" to be used in emergency scenarios. Should there be a brownout or internet service provider disruptions or any major catastrophe, we can move digital charting to paper charting for a certain duration of time. We have the Auvik probe installed on those backup machines, and it sends feedback back to the main Auvik dashboard where we monitor such things as ISP latency, devices on the network, and certain network elements like switches and access points.

We also have a probe sitting in one of the servers in the data center and it performs a similar function, helping us review our network infrastructure within the data center and to see where potential bottlenecks are, at what times of day, and to analyze trends.

We use it for basic troubleshooting as well because you can see everything on the network within a particular facility. At sites that don't have Cisco Meraki within the building, we use Auvik to isolate which ports' devices are connected to and for general troubleshooting. If, for example, an uplink port on one of the switches goes out, we can see, "Oh, that was port 26. Please switch it to port 25." We can duplicate configurations from one port to the next port and make sure that the facility is up and online.

It's been a very useful tool for us.

We used Auvik to monitor the networks of our two separate companies. Each company operates on its large network, with approximately 100 to 150 employees.

We implemented Auvik for better visibility of the network.

We are demoing Auvik to see if it makes sense for us to implement. As a managed service provider, we are utilizing it to monitor our clients' networks, perform inventory of devices, and diagnose and troubleshoot network issues.

We use Auvik to monitor configurations, devices, and discovery.

We are a small company of about 15 people. We do open-source kernel development for lab machines. We have about 100 of these machines and they are all connected using smart routers. However, it is hard to monitor the routers' states.

We do open-source driver development as a contractor for other companies that may have licensing issues. We write the open-source network drivers for Linux and other open-source operating systems. That is the reason we need good network monitoring software: so that we know where there are problems in our network drivers. If the network drivers produce very bad network traffic, we need to know the first time. We have a lot of test devices, laptops, running in our lab, and they are currently monitored by Auvik, and we are very satisfied.

We use it to monitor the network infrastructure and assets of our clients. We are a managed service provider and it fits neatly into our role. We also use it to keep configuration change records, which is something we didn't have before. It's nice to have that in one platform.

We use it as our network management tool and configuration backup utility.

We use Auvik Network Management to monitor the networks of our clients who subscribe to our network monitoring service. This includes everything from backing up and restoring configurations to maintaining a complete network map.

I have 21 different locations in different networks that I have to manage. It gives me the ability to see the devices on the network, to see any troubles, to diagnose and support end-users or get into the network devices that are having issues.

As an MSP, we monitor all of our clients with Auvik, specifically to monitor their network devices and connectivity, and to generate tickets. We also use it to back up configs for network devices, and it's where we get warranty information since we deal with life cycle management.

We can even push changes to devices through the terminal. Anytime there's a disaster, it's the first thing that we'll go to, to see what may be down or what may be inoperable. It's a really quick way of seeing what may be broken in a network. That's really handy. It's our network monitoring management go-to.

We mostly use it for network monitoring. We also use it for configuration backup.

We use it for insight into an entire network, all the devices on it, and for monitoring their health. We also have it hooked into our ticketing system for automated ticket generation from any of the devices that we need to manage.

We use it for monitoring network infrastructure and network servers.

I use Auvik for managing my two most complex networks with multiple locations and diverse routing.

Auvik is primarily for monitoring network devices to see which ones have gone down. Another use case is tracking bandwidth utilization on the interfaces.

We manually use Auvik for network monitoring, configuration backups, and syslogs.

We implemented Auvik because we wanted to have a redundant monitoring solution that has a cloud component.

Auvik utilizes a cloud component that centralizes all data collection and aggregation. Additionally, we employ multiple on-premises collectors to gather data from individual devices. Therefore, our deployment will have a collector at each site, supplemented by a secondary collector at our main site. This configuration ensures redundancy and seamless data transmission to the Auvik cloud.

I am an MSP and I use Auvik to monitor my client's networks.

When we experienced network issues, we simply lacked the visibility to understand the underlying causes. Auvik provided us with much-needed visibility into our network, enabling us to effectively diagnose and resolve problems.

We are using Auvik's SaaS platform with an on-premises connector.

We utilize Auvik for monitoring our clients' environments. 

We manage IT infrastructure for 400 companies, and Auvik allows us to monitor it remotely. We have a portal to monitor these companies' servers, devices, routers, and APs constantly so we know when something is down and needs to be repaired in real-time. It's nice. We have it implemented in our Autotask and service desk portal, so it can automatically open and close tickets.

We use Auvik mainly to monitor switches and firewalls but also use it to monitor VMware. We also utilize the extra monitoring that Auvik provides for desktops.

Auvik helps us manage all our devices on the network.

We use Auvik to manage our network, infrastructure, and servers across various locations. We don't use the automation portion of Auvik except for automated integration with our ticketing system. Auvik sends alerts, but we haven't set it up to resolve issues automatically.

We're an MSP and we deploy Auvik for every single customer that DP Solutions has. We use it for network monitoring and infrastructure provisioning alerts. We also use it for troubleshooting, and for backups and configuration.

We are an MSP. We've got about 500 clients. So, multitenancy is pretty important to us. We're only interested in monitoring and managing network devices, and we define that as switches, routers, access points, and ESX hosts. Even though some of the things that we traditionally consider to be a computer—such as a laptop, a workstation, or a server—appear in Auvik, we do not do any management of them there.

The RMM platform that we're currently using is wonderful when it comes to servers, laptops, desktops, and all that, but it is absolutely horrible for properly detecting or identifying a network device. In other words, SNMP to properly identify a device flat out did not work and does not work in our other solution. Auvik fills that gap and does a pretty good job when it comes to that. We have always used multiple applications, and it comes down to finding out what the strengths are of a particular application. Auvik does a great job when it comes to networking devices, but we couldn't do nearly as much as what we do for servers and workstations. So, we use it according to its strengths and our other tools according to theirs.

Auvik is a SaaS-only product. There is no on-prem version. There are some definite pros and cons to it. Having to rely on someone else to handle all of the security aspects of something that's SaaS, especially in today's world, can be a little bit nerve-racking. When it is on-prem, you've got full control of ingress and egress. You can lock down the firewall and do all of that good stuff, but at the same time, not having to mess with all of the infrastructure and the things that are required to make a product function is pretty valuable. So, we don't have to worry about storage space, server speed, etc.

We primarily use Auvik for network monitoring and occasionally to remotely access some devices. It helps us monitor clients with a multi-site setup. We can monitor the network and overall network connectivity. The configurations of the devices we monitor are synchronized into IT Glue for documentation.

Auvik was part of the company's toolset when I joined as an engineer, and we have been perfecting it. We had a couple of big clients when I started. Everybody was under one site even though there were multiple sites. There was a site-to-site VPN and more. For some projects I worked on, we got directions from Auvik's account managers on how to implement multi-site within Auvik properly. That helped us manage these individual sites efficiently without creating too much burden.

We use it for network monitoring and for configuration backups.

We used PRTG as our network monitoring stack and SolarWinds network configuration manager. SolarWinds has hacked a couple of years ago, so we have been left with PRTG but no configuration management. PRTG doesn't do network monitoring very well, but it's suitable for server monitoring. I had known about Auvik for quite some time and decided to give it a look. We tested it and got insights into our network we had never seen before. We have three disparate physical networks, which provide insight into how everything is interconnected.

We have 55 users spread out over all our locations. Our sales staff is remote, but we have a primary site with two physical networks and a disaster recovery site co-located with one physical network.

I'm one of the biggest Auvik fans out there. I have used it personally, and I have brought it to every single company since 2015 as a product offering or for the internal use case. I currently own a firm, and I am yet to talk with Auvik. When the time comes, I will absolutely be doing its implementation for my company, and I will be offering Auvik to my customers.

I did its implementation for a company in the November of the last year. NetFlow was one of the biggest use cases, and it was for monitoring the type of traffic inside the network. We were also able to do a lot of Syslogging, and with one pane of glass, we were able to remote into the various routers and switches that we had.

It was deployed via Windows services and not as a virtual box inside VMware, which is probably better. We also had a cloud collection point, which was also a failover in our Chicago environment. I was deployed for five different sites along with the NetFlow application.

We are a multinational company in almost 55 countries. One of the reasons why we selected Auvik was we wanted to have insights into our networks. Ultimately, we can control them at a central level. Auvik was the best fit because it has:

1. A cloud-based solution using a SaaS model. 
2. Visibility into end users using tools. 
3. Terminal auto-connect, where we can connect devices from Auvik. 
4. Some sort of an audit. 
5. Backup consultations in the tool, which it maintains. 

It has really eased our life in terms of network operations.

We primarily use Auvik for managing and monitoring devices, including network devices, access points, and printers. We utilize Auvik's alerts to notify us of offline devices or any unusual behavior it detects, such as high interface utilization or low disk space. Additionally, we employ Auvik to automate the backup of our network switches.

We implemented Auvik because we lacked visibility into potential network issues, such as switch or access point utilization. While I have a wireless controller that provides some insights, Auvik unifies this information into a single, comprehensive view. This centralized visibility enables us to proactively identify and address network problems.

Auvik is deployed in a hybrid model because we have an on-prem collector that sends the information to the cloud.

I'm a technical team lead managing other engineers and specialists for several clients. I utilize Auvik for strategic discussions, escalations, and support tickets. I'm on the backend trying to coordinate responses to outages, feature requests, etc. 

We use multiple applications to manage our network. Auvik is our network mapping and discovery tool that creates alerts in our ticketing system. We use ConnectWise Automate and that suite of products for ticketing. It's not like Auvik is a ticketing help desk system with remote control, but it can do just about everything from a monitoring standpoint. We still use AppNeta for board mirroring or finding latency in network traffic.

We mainly needed a tool for managing or monitoring our firewalls and switches. We do have other tools for general server environment monitoring and applications monitoring, but they are not as good for managing and monitoring firewalls and switches. We specifically needed monitoring and management of firewalls and switches for our data center environment.

We use Auvik to map out networks and to view device health, meaning not just if it's up or down but also if there are any system-generated errors that can be listed via Simple Network Management Protocol (SNMP).

We use it for our clients that have managed network services. We monitor their networks to see if there are any anomalies or unknown devices, and we use it for troubleshooting as needed.

Our use case is to monitor and maintain not only our corporate headquarters, but all of our remote sites and embedded sites across our company.

It's a SaaS application.

We use Auvik for networking and security-related purposes.

We implemented Auvik because we wanted to have mapping based on different physical locations, especially for remote locations. For us to be able to track the traffic properly in and out of both of those environments.

Auvik is cloud-based with an on-premises collector.

We use Auvik to manage our network devices and get alerts about what's happening on our systems. We've deployed it across our showroom office network. We have 140 devices.

We're an MSP, and we use it to manage our customers' networks.

The industries of our customers vary. They are from healthcare, manufacturing, finance, education, etc. It's mainly used to monitor switches, firewalls, ISP connections, and Wi-Fi, such as controllers, etc. It does do some additional monitoring on workstations and servers, but we don't rely on it for that. It's just not what their bread and butter is. So, even though it does that, we don't really focus on that.

We have an MSP portal for accessing all of the different customers. Auvik has an integration with ConnectWise which we never used. We just log in directly to the Auvik portal whenever we need something with Auvik, but they do offer an integration with ConnectWise that we don't take much advantage of.

I use the monitoring on a daily basis. I receive the alerts. We have two monitoring software solutions and Auvik complements the other one. We use Auvik to cover the gaps in the other one. We get alerts from both sides.

I used to work at a managed service provider, and we needed a network topology mapping solution and discovered Auvik. So, we tried it out, and then we used Auvik until that MSP was bought out. I left the MSP world and became a network engineer at Greater Nevada Credit Union, where I'm now.

We pretty much use it for topology mapping. We use it for mapping out the network and then monitoring the availability of the network infrastructure devices. There is also alerting whenever there are problems. So, we basically use it for monitoring, alerting, and troubleshooting. We also use it for configuration management and automated backup.

It is a managed solution, so they handle all of the platform upgrades and all that stuff. We have got whichever version they have got.

We really needed something for reading logs, so we can go back in time, and also something to monitor our network and our infrastructure in real-time. I use it for everything as far as monitoring in real-time goes, to see what's going on in our network, along with Kace. 

It's deployed on-premises, but it's using the cloud to get to you. You can use it on-premises, but we prefer the cloud.

We use it for managing our inventory of assets and for receiving timely alerts from our servers.

We use it to onboard new clients to get a baseline idea of what their network looks like and a picture of what we potentially need to upgrade or replace or get rid of entirely. And for existing clients, we use it for network troubleshooting to figure out if there are any loops in the network or, if we're seeing high packet spikes on specific interfaces, to track down the lags in the network.

We use it for small business networks, mainly SonicWall firewalls and HPE networking gear.

We use it for monitoring our entire network. We head off a lot of problems with some early alerting on either storage or high utilization, thus we can get in front of problems before anybody notices. We have the solution tied into our help desk system so the alerts open up help desk tickets, then the guys look at it from there. We use it for troubleshooting devices that are not reachable. We also use it for backing up our firewalls and logging into all of our network equipment.

We use this solution to monitor our network devices and servers, get alerts if devices go down, and get alerts when they come back up, which is important. Auvik alerts us about abnormal network traffic and certain ports on certain network devices or high utilization and high bandwidth. We're going to use it to monitor our virtual servers and virtual systems that of which our servers run. It gives us good visibility into our network.

We're a resort and have about 800 employees. It is a single network with multiple VLANs. It is relatively straightforward, but we have a lot of remote buildings connected by fiber lengths. Therefore, it's spread out over about 1600 acres of property.

We're a managed services provider that caters primarily to movie theater clients. Most of our Auvik collectors are deployed at active movie theaters and point-of-sale environments.

We use Auvik to get alerts on network activity and server resource utilization. We monitor firewalls, interfaces, traffic bandwidth utilization, and VPN usage. Auvik alerts us when a VPN or other device goes down. We monitor aspects like port utilization and which switches are being used for what or how much traffic goes across ports.

We don't automate anything through Auvik. We have other tools we use for automating tasks on our systems. We're utilizing Auvik specifically for visibility into the networks and SNMP-assisted log alerts and functions like that. When those are triggered, other tools outside Auvik run the daily automation routines.

It provides a single integrated platform for monitoring, but we use some other RMM tools to log into our servers and things like that. Those have some monitoring built into them, so we get duplicate alerts along with those. If a hard drive on a server fills up, I'll get an alert from Auvik and our RMM solution. But there's no other platform offering more monitoring or alerts that Auvik's not giving us. Auvik gives us more than what all of our other platforms give us, and it's all in one spot.

The primary use case is for monitoring networks, traffic, etc. 

We install the product on all of our customer's endpoints. As an IT services consultant and provider, we depend on it to help us monitor the SaaS applications in use in customer environments. This includes monitoring for shadow IT, but equally important is being able to monitor license usage of approved apps and report that usage back to our customers.

Our customers' environments range from a handful of users to hundreds. Most of them are heavy SaaS users, and most work in at least hybrid environments, if not completely remote. Many of our customers are highly regulated or work with highly regulated customers themselves. All of them have intellectual property they're concerned about safeguarding, as well as customer information. 

This solution is one of a set of tools we use to control and protect these environments. It's one of the most important. Knowing about and stopping data from being stored or otherwise transmitted to unapproved SaaS applications is a primary concern for our customers, as it can cause regulatory violations or data loss and exposure - of both their customers' data and their own IP. It works quickly and proactively, allowing us to prevent these problems.

I am the network administrator for our company, and we use Aruba Central but we're looking into Auvik to see what else we can do with it. We're seeing quite a bit of difference.

We're an MSP, and we have deployed it to monitor the customer network and environment and make sure that the configurations are backed up and know when things were done.

Our primary use case is to have a monitoring solution for our managed service clients. That was something we were offering, but we weren't really doing well on that front, in terms of having a proactive monitoring solution. That was the primary pain point we were trying to fix.

We're a cloud service provider, so we wanted a solution that would proactively be able to notify us of potential issues. We have four core cloud platforms that we provide. We wanted something that could look at both the network connectivity as well as the infrastructure and storage layers.

The primary use case is network monitoring.

Auvik is an excellent tool for monitoring all our infrastructure devices, particularly network switches, servers, etc. We also use it to manage assets such as printers and workstations.

We use multiple products in our system, and Auvik is one of the top tools when it comes to monitoring; it does its job well, and we're pleased with it.

We originally purchased Auvik to map our network because I didn't have any kind of network diagram. I thought this would provide a better view of our network. 

I use Auvik every day for everything. I can remote-terminal in, meaning I can be anywhere and jump in from my phone and make any changes I need to on switches.

We use Auvik to monitor two different domains and to review any trouble that might come up. It's opened our eyes to some problems that we've had on the network and now we're working to fix those.

We're using it just to monitor customer equipment and make backups for network device configuration changes. We're using maybe one percent of what it's capable of doing. We're trying to get some of our stuff straightened out since whoever set up our Auvik did not do a great job of organizing it.

We are an Auvik reseller, and we manage Auvik instances for our clients. We use Auvik to monitor our customers' network infrastructure and troubleshoot any issues that may arise. Auvik is typically deployed on the data center side of a company. If they have multiple branches, we will deploy an on-premise jump box running the collector. We usually manage the corporate data center for each client and the network infrastructure for remote branches.

Our company has between 500 and 1,000 employees, and we have around 150 customers using Auvik. Those companies range in size from 50 employees to thousands.

It is used for network monitoring.

We use Auvik for monitoring and alerting on customer environments.

We lacked visibility into specific aspects of our Local Area Network. Therefore, we required a solution capable of monitoring and alerting us about port activity and other relevant information at the switch level.

Our use cases are around network monitoring. That was our biggest challenge.

We're an MSP using Auvik to deliver a service for our clients. It's good at monitoring switches and networking infrastructure overall.

I do internal IT for a company and I use Auvik for most of my daily tasks as they relate to firewalls, switches, and routing.

I run an engineering team with a dynamic cloud-based environment. I was interested in tools that can help me understand what we have deployed. 
There are about five people administrating it. In terms of the number of locations, it's hard to say. We're a distributed remote team, but we have multiple cloud environments. We don't have locations in the physical sense of the word anymore.

We use Auvik to create a graphical representation of our network. It's easier to trace issues when we know what's connected at a glance. Auvik gives us alerts when a device goes offline, and we use Auvik to identify the place in the network path where the issue lies. Was it a core switch? A downstream switch? Was it not a switch at all?

We needed a solution to monitor all of our systems. We were using another system, but it wasn't up to par. Auvik gives us everything we need plus some. Right now, we're using it to monitor all of our virtual machines and switches. We can do configurations on any of our switches directly through Auvik.

Right now, another engineer and I currently use the solution. We're going to allow other IT staff to view it, but nobody else will have access. There will be another five staff members who will see all of the data.

We use it for monitoring clients' networks.

I use it on a daily basis to monitor the portion of my network that is backbone.

I have cloud access, but the collectors are on-prem.

We use Auvik to monitor if our network equipment goes down.

We implemented Auvik to be proactive in case the internet connection or equipment goes down.

I use it as a first line of information gathering. When properly configured, I am able to quickly diagnose and troubleshoot issues from the network's infrastructure level and go up to servers and other devices.

Its main use case is network monitoring, specifically for some of the essential elements of our network. It monitors more, but we're really after those essential elements.

I use it to monitor all the activities in our office, including printers and the internet. It gives notifications for each device.

The primary use is for notifications and alerts, but also to get a feel for the network because I can see it all on a map, and it looks nice. We don't only use Auvik. 

To paint a picture of our environment, we deploy Auvik for some of our clients, and some of them own multiple facilities, so we have sites for them. Within our company, different individuals have different access levels, some with read-only. We also give some of our clients read-only access so they can see their network if they are curious.

I'm a system administrator. I use it to monitor and automatically draw a network map of our network.

We use it to monitor network devices, and for alerts when things are down and when devices need to be fixed. It lets us know about outside-facing IP addresses, external and internal MAC addresses. We use it to monitor everything on all our clients' networks.

We are a managed service provider, but we look after a couple of thousand customers all over Australia. We look after their total IT solutions, and we use Auvik as a network monitoring platform and alerting engine. 

We use Auvik to manage our customers and collect configurations, diagnose issues, trace cables, and access devices remotely. We also use it internally for our own support purposes.

We're an outsourced IT company, so we provide IT to other companies that don't have their own departments or don't have the skills. We might go into a company with an IT department and do projects for them that they don't have the skills or resources to do.

I use Auvik to monitor, check, and access all network licenses for different companies, including firewalls, servers, and other devices. The Auvik collector is deployed on the servers and in the management station. The agent collects all the information in the network and sends it to Auvik. Auvik's network map will display all of the devices. If a device is offline, it won't show, but the collector will automatically add it to the Auvik platform when it comes online.

We use it for visibility into remote sites. We use it to fix misconfigurations that come up, investigate network issues or network slowdowns, and alert us if devices go down.

In terms of deployment, it is pretty much all cloud-based. There is an agent that you put on a server for your site.

We are on MSP with multiple clients. We set up a site for each client, and that way we can review and verify all their network equipment: firewalls, switches, routers, even servers, and VMware ESXi. We also get alerts and notifications when everything is disconnected so that we can quickly find the reason and make sure clients are not affected.

We initially got Auvik to monitor our network devices and equipment mainly for outages and that sort of issue. We have integrated its alert system and email-to-text solution from a local New Zealand telecommunications provider so that our IT staff can get text alerts to their phones. It's quite handy because you're not constantly monitoring your email. So for our different alerts, we get texts now as well as part of that. It might be on the weekend or something like that, and you're not sitting there monitoring your emails, so texts are a bit easier for our on-call IT person to get a text, and then they can check out what's going on.

One of Auvik's services we use is TrafficInsights. It's reasonably new and wasn't around when we first got it. We can feed all the logs into there to see what connections are going and where things are connecting to the environment. It's pretty useful from a security perspective. For example, you can search and see when a specific IP address might have come into your environment if you need it to do an audit or a review. We generally use it for audits or checking where certain things are connecting from around the world. It's a good security feature we can use when we're worried about a device talking to a particular IP address. We can see how long it may have been talking to that. We haven't actually used it for network bandwidth as such.

Auvik also acts as a config register, connecting and pulling the configurations of switches. It's good to have that stored there. If we need to restore or roll back to a particular config, those are saved somewhere else in addition to saving it manually before we make changes.

Auvik is a monitoring solution for our infrastructure. We needed a tool to monitor the network, tell us when something is down, notify us when resources are low, and functions like that. 

We use it mostly for monitoring. Also, we're pretty big on getting device configs from it, but I don't know if we have used any of those configurations to roll anything back. For a lot of our network equipment, whenever you update the firmware, part of the feature of updating it is that it backs that up automatically for us. 

There are around 20 or more clients in Auvik that we monitor. Mostly, it's just for alerts if things go down, but with firewalls, we specifically have alerts that monitor memory because we have a problem with a couple of firewalls that go into the conserve mode if their memory hits a certain percentage. It's a huge part of our monitoring. Half or more of the alerts that come in, come in through Auvik.

We are using it for monitoring and troubleshooting. It is cloud-based, but the collectors always have to be on-premise. We must be using its latest version.

We use it for network monitoring. We don't do a lot of systems monitoring with it. We predominantly use it for core switches, external network adapters, and other similar things but not for the endpoints or server hardware.

We are currently not using any of the automation functions.

I have access to Auvik as the system administrator to use it to view my network and manage the various pieces of it. 

I needed a solution like Auvik because I wanted real-time network mapping. At the time, we were using Visio diagrams, which are obviously very hard to keep updated. And so to have something that is running the cloud in real-time on what our network looks like was something I really was interested in.

We use Auvik as a network scanning tool so that we can detect devices that are connected to our office network. We can get information from those devices and track them down. It's a network monitoring and scanning tool, so we can detect rogue devices and network traffic as well. It's essential to see what's on our network.

Auvik provides a single integrated platform from a network monitoring perspective. Having a single integrated platform is important for our organization because we obviously don't want to check multiple systems.

It's deployed in a single location with multiple networks for different departments. There are 200 endpoints in our organization.

We are using it for more visibility on our network devices.

It gives me an overall idea of our network. It shows me where things are at. It tells me about devices being down, e.g., printers. I also use it to see web usage, e.g., what sites people are going to. It has a lot of uses. I check to see the overall network topology, when things go down, or whenever I get alerts from Auvik.

I use the reporting part of it. Every day, I take a look at the reports every day.

We are using the latest version.

Our primary use cases are for monitoring the network and backup for the switches and firewalls.

We're a managed services provider using Auvik to monitor our clients' infrastructure. It is part of a set of tools that keeps us informed when something goes wrong, and we use it to build network maps. You can get an idea of what's happening on-site even if you're unfamiliar with the client's setup.

Sometimes it's the only thing on the network. It's competing with Ubiquiti if we have a Ubiquiti network. Not all the time, but sometimes. 

We're an MSP, so we function as the IT company for multiple clients, and we primarily use Auvik for monitoring and troubleshooting network issues. It's deployed across various locations, from small to medium-sized businesses, plus one school system.

We use it for our small and medium businesses, specifically for data collection. We also use it for network mapping.

Auvik is our monitoring solution; we're an MSP, so we use it to monitor multiple medium-sized enterprise clients. It's primarily used by the network team, though other teams log on occasionally. We have five users in our company. 

We primarily use Auvik for network discovery, visibility, management, and minor monitoring.

We are a managed service provider, so we use the solution to monitor our customers' network environments.

Auvik provides a single integrated platform for network monitoring, but we integrate with other platforms for ticket generation and another dashboard we use, BrightGauge. 

We use it for alerts, to a degree, but we mostly use it for networking, monitoring, and triage.

We use Auvik as a dashboard in our service desk department to monitor the network status of our clients, as it helps us with real-time connectivity. We use the solution for our service desk and applications and infrastructure team, including all the managers, so we have it across almost the entire technical support team.

It is our primary monitoring tool for devices.

We have virtual machines running the Auvik application. The collectors are also installed on the virtual machines.

My company is a managed services provider managing network infrastructure for multiple clients. We use Auvik to monitor firewalls, routers, or switches. When network devices go offline, get instant email notifications so we can investigate the issue. We also use it to manage devices directly through a web browser remotely.

We're an MSP, and we support small to medium businesses from end to end, including printers, servers, and networks. We use Auvik to manage our clients' infrastructure. Our customers include companies running factories and hotels.

Our initial purpose was to look at network data from our endpoint protection units. We wanted more visibility into the traffic coming into and out of the organization.