Auvik Network Management (ANM) Reviews

As an MSP, we install Auvik on our managed service clients' networks to gain a comprehensive view of their network layout. This allows us to monitor overall network health, receive performance metrics, and identify outages across all SNMP-manageable devices like firewalls and switches. While Auvik excels in network device monitoring, we rely on other tools for managing aspects like Windows systems.

In larger environments, we typically deploy a dedicated agent directly on the network for comprehensive scanning and monitoring. For smaller environments, a cloud-based agent provides a more efficient solution.

Auvik provides a close to real-time picture of our network.

Integrating with a network map might seem straightforward, but the complexity depends on the network size. Larger networks require more effort. Fortunately, most of our clients have relatively small setups, typically one to two sites, two to three firewalls, and five to six switches. This keeps our integration time to a maximum of thirty minutes, making it a quick process to get them up and running.

While entry-level technicians don't heavily rely on Auvik for troubleshooting itself, they do benefit from its automated ticketing system. Auvik alerts them to device outages, allowing them to perform basic troubleshooting. If the issue persists, they can escalate the ticket to an engineer, who can then leverage both the technician's initial efforts and the information provided by Auvik for further diagnosis.

Auvik has significantly improved our ability to resolve issues quickly. It saves me at least 30 minutes per ticket because I no longer need to remote into individual network environments and run diagnostic tools manually. With Auvik, I can pull up an overview of the network, saving valuable time on troubleshooting, updates, and other tasks.

Auvik allows us to spend less time on setup, maintenance, and issue resolution.

I like Auvik's detailed device dashboards that show everything from uptime to configuration revisions. The new Northstar feature is particularly useful for troubleshooting network path issues. When someone reports slowness or connectivity problems, Northstar quickly maps the device's connection path, helping pinpoint or narrow down where the problem might lie.

Auvik's interface can appear cluttered at times, reflecting its feature-rich nature, but despite some occasional messiness, it remains fairly intuitive for new users.

It would be helpful to suppress credential prompts for specific sites in Auvik. Currently, we have to dismiss the "enter credentials" or "new devices found" alerts for each site, which can be repetitive. An ideal solution would be a per-site checkbox to indicate that we've discovered all the devices we expect on that network and don't want to be prompted for credentials again. This would streamline our workflow and eliminate the need to dismiss repetitive messages.

While Auvik offers good integrations with SNMP, WMI, and VMware, there's room for improvement with Hyper-V, a platform we heavily rely on. Additionally, enhanced UPS integration would be valuable, particularly for alerting on critical events like a switch to battery power, which currently seems to be missing. This limitation may be specific to our UPS setup, but improved UPS monitoring within Auvik would be beneficial.

The speed and performance can be improved.

I have been using Auvik Network Management for two years.

Auvik Network Management can be a bit slow at times, causing us to wait for it to fully load information. While it doesn't crash frequently, occasional lags can interrupt the workflow.

Our experience with Auvik's scalability is positive. While very large networks with many sites and devices can experience slow loading times, this isn't a concern for most of our clients, who typically have just a few sites. For the handful of larger clients we do have, sub-dividing their networks into smaller groups has mostly addressed performance issues. Even our largest client, with its complex network of eight core switches, 20 labs, and a main firewall, only experiences minor slowdowns when loading everything at once. Overall, Auvik's scalability seems well-suited for the needs of our client base.

In the past, I reached out to Auvik support a few times regarding general SNMP issues, where I had trouble getting Auvik to communicate properly with some devices.

My communication with Auvik technical support was via email, a back-and-forth process with replies within a few hours, which is fairly typical. While it took a few days to resolve and initially involved directing me to the knowledge base, the support escalated to someone who identified the specific fix needed. Overall, it wasn't exceptional but certainly not substandard either.

Neutral

The overall setup of Auvik is straightforward. One person is enough to handle the deployments.

I would rate Auvik Network Management nine out of ten.

Having used similar network monitoring tools in the past, I was already somewhat familiar with the core functionality of Auvik when I joined the organization.

I recommend Auvik Network Management. While the training and documentation are helpful, hands-on experience is key. In my case, after reading the manual, I dove right in with a client's network and spent a few hours exploring the software. This practical learning made a big difference during my first rollout, as I had a much better understanding of Auvik's capabilities. Having prior experience with network monitoring tools like Nagios and OpenNMS helped as well, since they share a similar core concept of agent-based monitoring and network mapping. This familiarity made Auvik relatively easy to pick up.

We use the solution pretty much for what it was designed for. We use it for network monitoring and its dashboards. 

We were trying to solve for visibility more than anything else. The monitoring we do is more preventative than remedial. In the time we've used it, we've migrated a lot. It's helping us more on the understanding and project management side rather than monitoring. 

The ease of setup is one of its most valuable aspects. 

The visibility and topology diagrams are great. The dashboarding is quite useful.

Its integration with ConnectWise has been the most beneficial for managing our network performance. 

Auvik is a bit of a capturing tool. For us, we can highlight the high-level elements and problems. Our network is relatively secure, so we haven't actually used it for alerting. However, it is there as a preventative and monitoring measure more than anything else. 

The interface is great once the configuration is done. 

We do get a real-time picture of our network. The visibility we get is around 95%, with the remaining 5% our fault, based on the way we're set up.

The solution has helped decrease our mean time to resolution. However, it varies, depending upon the severity, for example. It's reducing any networking tickets time to resolution somewhat. For example, we are moving some clients from one subnet to another, and in those circumstances, it's taking half the time for us to do that in a process way. 

If it's purely network monitoring, it's absolutely brilliant. It shows ups and downs, and provides a lot more information than you generally need. However, since we know it provides a lot more information, we use it for lots of different things.

It reduced our mean time to resolution by 20% to 30% across the board. 

For our second line, third line, our network teams, it has increased productivity and reduced time source solutions by about 10% to 15%. 

As with all SMP's monitoring tools, it's a little difficult to get exactly where it needs to be until you've completed your desktop.

We're a bit complicated as a use case as we've got data centers and clients. We're mixed management with multiple subnets. If the network was simpler, it would work perfectly. There are a couple of overlaps. Things could be clearer.

Things are easily confused if there are multiple data feeds. So, if we have a server with three of our network clouds, it won't necessarily get the hierarchy accurate. Being able to drag and influence them in the network map would make a lot more sense. Therefore, being able to influence the map manually and overwrite it or customize it would make a lot of sense.

I've been using the solution for about a year and a half. 

We have the solution in multiple locations, for example, in data centers, client sites, and offices. We don't have a huge amount of endpoints. We do have a cloud platform and use it to monitor that. Our clients are largely SMBs.

We've had no requirement to be in touch with support just yet. 

The only instance of reaching out was when we raised a query during the first time installation. It was a deployment query, and it resolved almost instantly. If we understood the solution a bit more, we could have solved the issue ourselves. 

There is good technical support documentation. There are elements that need to be kept up-to-date, however. They could refresh it a bit more. That said, it's not really a problem or enough to complain about. There are too many changes happening in the industry for any documentation to be perfect. 

Positive

We've used all kinds of solutions. We do have SolarWinds instances, for example, however, we don't tend to use them much. We've also used PRTG. Auvik is faster to set up.

The deployment was simple. We implemented it in half an hour. 

We did have a vendor assist us with the deployment process. 

While I couldn't quantify it at this time, we have definitely seen an ROI. 

It certainly helped out with one of the projects that we're involved with. Whilst we've had it for 18 months, we've really only embraced it over the last six and we won't really see figures from it until the end of next quarter.

We've likely saved five to six hours a week so far.

The solution is a little on the expensive side. That may be skewed for us since we use it more as a monitoring and preventative tool, and largely it's meant to be a remediation tool. While it is expensive, it's not so much so that it makes me want to switch.

We're an Auvik customer and partner. 

While the solution has not yet empowered our entry-level technicians to solve more tickets on their own, they will be able to soon. We're just moving across to utilizing more alerting and bespoke alerting. We're telling Auvik some of the things that we want to know and don't want to know. That is now starting to power the help desk. That change has been happening over the last week. So, by the end of this week, it will be.

I'd recommend the solution to others. Its ease of deployment and ability to provide basic information about a network, and monitoring basic information about a network, is actually very good. It puts things on the screen almost immediately. When alerts fire, it points to those alerts, and you can literally click through and find the problem almost instantly. The only negatives are around some things that you would expect. That said, overall, absolutely, I would recommend it. The peace of deployment and ease of information are worth it. It's very, very easy to understand. It's very, very easy to see where your problems are, and it's very, very easy to use that information to remediate the problems. However, for my advanced monitoring, it's a little more difficult to understand exactly where the information is coming from and how it's utilizing the information. 

I'd rate the solution nine out of ten.

We set Auvik up on several of our sites to monitor different devices, including computers, printers, and the network. We used it to collect data to see what's going on in our network.

I wanted to try it out to see if we could have all of our devices managed in one place.

The reporting that they have available was good. The options to customize the reporting and the depths to which the system worked were helpful.

The interconnectivity and ease of use were good. It's not very confusing. It's pretty well laid out and easy to understand.

The network map in the dashboard gives you a real-time picture of your network. It did a really good job of showing you an overview of everything.

Our networks weren't weren't very large, so we had no issues with the network map.

Overall, it gave you a pretty deep in-depth view of what was going on. 

We did see the benefits of Auvik immediately. It started pulling data within minutes of implementation. 

It actually did empower us to be able to solve problems more quickly and to stay on top of them and be more proactive rather than reactive.

It helped with our mean time to resolution. We noted a 50% decrease.

The solution allows us to spend less time on setup, maintenance, and issue resolution. 

With the time savings, I've been able to work on other projects and have been busy with other issues. 

We might have encountered a bug. We notified Auvik when we had an issue with every single installation of their controllers. Using the normal uninstall process was not able to remove any of the controllers from any of the devices. 

I just started using Auvik. I went through the free trial just to test it out to see if it would be something that we could use at our organization. I've used it for 14 days.

I haven't had any stability issues. Other than factors that were outside of the control of the controllers, like the Internet going down with the ISP, it was up the whole time. 

The scalability felt clean. It was easy. If I need to add more sites, it is really simple. 

While I didn't contact support directly, they had a support specialist who had multiple Zoom meetings with the sales team. One of their support specialists or engineers jumped on the Zoom call and asked me about the uninstall problems that I had. They walked me right through the process of uninstalling it, however, I had to go into the registry to do it. It was a little bit more complicated of a process than just a normal uninstallation.

Positive

We do use Ubiquiti. It's similar. However, it only deals with Ubiquiti devices. 

The initial deployment was easy for me. Since we had multiple sites, it took me a couple of days. 

After deployment, I'm not aware of any maintenance needed. 

I handled the setup by myself. I didn't need the help of any integrators or resellers. 

The pricing is a bit more on the higher end. If you are paying by device and you have a hundred billable devices, the pricing can get high pretty quickly. 

Based on the overall usefulness and ease of use, I'd rate it seven out of ten. However, we are already suffering from a bug, which knocks off a few points. 

I'd advise new users to read up on the setup process and familiarize themselves with the way the system collects data and what's required on all of the devices in order to properly pull the data. 

We primarily use it to monitor our clients' networks. We are also using it as a monitoring tool for some of the clients for whom we manage VMware clusters. We are utilizing Auvik log gathering and alerting. It is like a poor man's VMware monitoring tool.

Auvik's network map along with its dashboard gives us a real-time picture of our network. It is nice. I like how it changes. Based on how big your screen is, it expands to fill in the free space, and as it understands the environment better, it gives you a nice topology. You can see that this device is connected to that device through this port and everything else. It gives you a lot of information in a very clean, concise manner.

The network map does get cluttered if you have a very large environment and you are not tearing it down to smaller sites or smaller chunks. I know early on when we started using it, we would have clients who had MPLS connections, so we were scanning all seven sites in one Auvik site. It was definitely unwieldy because of the number of devices there. Once you get an idea of how you can search and filter, it gets a little bit easier. In our experience, it was better to start creating multiple sites and breaking out each of our clients' sites into a sub-site. Even then, some sites were quite large, so we had to delve into it. It can get messy, but it is something that we worked through.

It gives you full network visibility assuming that you are setting up your devices correctly because, with the bad data in, you are going to get bad data out. You need to get into all your switches, firewalls, and everything else and make sure that SNMP is configured correctly. You need to ensure that your logging is pointing to the right IP and that creds and other things are correct so that Auvik is able to ingest the data correctly. Auvik can then provide a good map of what it is seeing and where all your devices are. It is definitely not a quick and easy setup if you have a fairly large environment. If you have an environment where maybe you have never set up SNMP, there is a little bit of heavy onboarding, but once it is in and Auvik is collecting the data, it is a good product.

We could see its benefits within days of having all the environments configured correctly, sending logging data, and having SNMP configured correctly. Within days, Auvik was able to collect the data, connect to all the devices, and see how switches were connected back to the core and how the traffic flowed. We started getting good data and performance metrics on port speeds and things like that fairly quickly. It was pretty quick.

We are still rolling out access to the solution for different levels of our support team. Those who do have access to it have found it beneficial to be able to see the data that they would not normally have access to.

Auvik has helped to decrease our mean time to resolution. We are not tracking that per se, but for the few issues that came up, we went to Auvik to review performance metrics. That minimized the amount of time it took to resolve whatever we were looking at because we had the data given by Auvik. We were not blindly trying to figure out what was going on by using a device's features.

Auvik allows us to spend less time on the setup and maintenance of the solution and less time on issue resolution. For some of the clients that we have brought on and utilized Auvik with, there has been a little bit of onboarding. We had to go and change SNMP settings or just enable SNMP, community strings, etc. We had to repoint the syslog so that it is pointing to the Auvik collector. There has been onboarding time there, but in the long run, because of the data that we get out of Auvik, it reduces the amount of time it takes to look into issues. So, there is a wash and probably a net positive, where we take less time to deal with issues because of Auvik than the time it took us to get it set up.

I love the ability to remote into network gear such as switches and firewalls directly from the Auvik dashboard. We do not have to get into a jump box or VPN to a client. We can get a nice, secure terminal session straight to any network that we are monitoring and managing through Auvik. I can access that directly from the Auvik dashboard. That is probably one of the biggest benefits since we got it. It saves time. We do not have to look up passwords for a random jump box in a client's environment.

Most of the past frustrations have either been resolved or were more about how I was trying to figure things out. They were not necessarily an Auvik problem. I have been pretty happy with the usage. I have not come across a pain point that was a deal breaker.

They can maybe provide some more best practices or guidance around how large a network should be. They can provide some cutoff points, such as, if you have 30 network devices, you might want to chunk that into a smaller subset or site. They can help you better plan and design how to create your Auvik sites, especially if you have a large environment. Most of our client environments are less than a dozen devices, but we have come across a few where they have had 60 switches. It has been interesting dealing with so many devices and seeing all the data that Auvik can provide with so many devices in one single pane.

It has been about a year since I have been exposed to it, or maybe a little bit longer.

I have never experienced any lagging or crashing with the product. With the amount of updates and the communication that they have about when they are doing updates or when they are having issues, it has been easy. Everything is well communicated. They do a good job with it. I have not experienced the product crashing on me or something like that.

The scalability is pretty good because right now, we have maybe 40 or 50 base sites in our environment. A lot of those base sites are multisite sites. We probably have 60 to 70 total sites that we are managing through Auvik. There have been no slowdowns or hiccups. Everything has been good.

I have contacted their support. There was a problem trying to get a device recognized in the dashboard or send data to the dashboard. It might have been a networking issue, not necessarily an Auvik issue, but they were helpful from what I remember.

The quality of their support was good. It was not necessarily a system-down type of scenario. It was not a high-priority ticket that I put in, but from memory, they responded in an adequate amount of time to the question I was posing. For the scenario, their support was good.

Positive

I have not used any similar solution. The closest thing I have used would be Meraki, but that is Meraki-centric. It is not something that you can use with anything. That would probably be the closest thing to the single pane of glass and seeing how everything is interconnected. It is a hard comparison because the Meraki dashboard is made for Meraki software. I like Auvik a little bit better just because it does not necessarily matter which network equipment is there. With Auvik, we are utilizing clients that have multiple kinds of network hardware such as Aruba, FortiGate, Cisco, etc. They have anything and everything. Auvik has been very good at giving us that guidance into what is going on in the environment.

It is cloud-based with on-prem collectors at all of the different client sites. There is usually a service installed on a virtual machine somewhere unless we have a physical management device in their environment, and then we put the collector on that. Aside from the collectors in the actual environment, the service is cloud-based.

Its initial deployment was easy. There is obviously a learning curve when you get new software. It took us a while to understand all the features and abilities that Auvik provides, but the initial standing up of the site, getting the collector spun up, and adding network devices was pretty quick. It probably took thirty minutes.

The implementation took a couple of days the first time. Now, when we bring on new clients, the time depends on how large an environment is, how many switches and other devices are there, and whether they have already configured SNMP across the LAN. On average, a normal new client takes 8 to 16 hours to stand up, set up the Auvik sites, get collectors posted, and start ingesting data after setting up all the settings on the switches to point to the collector. It is a decent amount of time. It is not too much, but it is not necessarily super quick.

We did it all in-house. A few technical people from Auvik assisted us, but I do not believe we pulled a third party in on it.

For a new client that we bring on, it is usually a one-person job. We assign a tech, and they get it going. It is simple enough that a single engineer can handle it unless you are organized a little differently, and then I could potentially see multiple people being required. Generally, a single person who understands Auvik management and dashboard has basic networking skills, can go in and change SNMP settings, and set up logging can easily handle it on his or her own.

For us, it has been good. I do not get too much into the pricing side. We are an MSP, so we have a number of clients, and we are utilizing Auvik as a way for us to be able to better manage and support our clients. The more clients we bring into Auvik, the better the pricing, so we have been happy with how it is.

There are critical devices in our network that are monitored by Auvik at no charge. That is why we have been using Auvik for some of our VMware cluster management clients. We can add VMware servers to the Auvik dashboard and get basic monitoring and up/down alerting by utilizing Auvik, but we do not pay for them because they are not network devices. That has been a nice additional feature. We have way more network devices that we are monitoring, but being able to add those in and not having to worry about additional costs has been nice.

The data you get out of Auvik is only as good as the data you put into it. So, you need to make sure that you are scanning the subnets that you need to scan. Ensure that you are scanning everything in your environment, you have all your devices configured for SNMP, and you have syslog set correctly out the gate. That will set you up for the best usage of the product and get the best data out of it.

It is pretty good in terms of ease of use. Over the last year or so that we have used it, it has improved here and there, not drastically, but in terms of little annoyances that I cannot even think of right now. It is definitely easy to understand once you go through basic training for how the dashboard is laid out.

I would rate Auvik Network Management a solid nine out of ten.

We use it for network management. We use SNMP to get notifications about various issues on our network.

We implemented it because we tried out a free trial. The goal was to get more visibility into our network. I get notifications on everything from printers being low on paper to network cards that are dropping packets. It does a lot of things that otherwise I would not have known about.

It is very easy to use. After you do the initial setup, it is kind of set-it-and-forget-it.

The network map is pretty straightforward. It is like a lot of other discovery applications that I have seen. The network map gives a good visualization of our network as an overview. We can make it larger, and it is easier to see. Our network is pretty well segmented. It shows different switches and things coming out of it. We have got everything segmented very well, so we have not had any issues with it not being able to fit everything in.

I had to have a couple of support sessions to get everything configured correctly. The simple SNMP monitoring was pretty easy for devices using a public tag, but I did have to get some support with the firewalls to get them correctly into the system. I had to make a few configuration changes on the Fortinet firewall to get it to work, but after I got that worked out, the benefits were immediate. Within two days of implementing it, I realized that I had a lot of packet loss on one of our Hyper-V servers, and I was at a loss for what the performance problems were. I immediately found a lot of packet loss on one of the network adapters. I was able to swap that out. That immediately fixed the performance issues we were having with our Hyper-V server.

Auvik has not empowered our entry-level technicians to solve more tickets on their own because this is a one-man shop here. It is just me. I do not use it as much for resolving tickets, but it prevents some tickets from being created because of the notifications I get for various issues. I simply would not know about them otherwise.

As long as everything is cooking along fine, I do not get any alerts. I do not have a lot of false alerts that cause me to waste time. When I do get an alert, it is usually something that is pretty important, and then I can look into it. Oftentimes, it gets resolved before tickets are created by end users.

Auvik allows us to spend less time on the setup and maintenance of the solution and less time on issue resolution. The initial setup took a little bit of time, but it was not anything outrageous. It was not super complicated. For the most part, all the devices were plug-and-play after they were discovered. Firewalls were the only ones that took a little work to get working, but after that, the notifications that I get do save me a lot of time from responding to tickets because oftentimes, I can get things resolved before end users even notice it.

The notifications for events are valuable. If a copier is low on toner, I can get the toner ordered instead of being surprised when it runs out. It saves me from running around and having to check a lot of things. I get notifications based on the alerts that we have configured for it.

There was an issue where I did not have the ability to turn off certain notifications or noise that I did not care about. I worked with the support guys. They showed me how to do it, and I was able to silence notifications on a specific device, which is something that I was having trouble with. I had one device that was getting non-stop notifications about one issue that could not be fixed. It just had to be that way. It was a legacy machine. After working with support, I was able to turn those notifications off specifically for that one device and that specific problem, which I could not find on my own. After they showed me how to do it, I have not had anything to complain about this product.

If anything, the spacing on the network map can be better. In the network map, we have one switch crammed in there. Some improvements in the spacing on the network map would be good.

Their documentation and knowledge base can also be improved.

We have been using Auvik for about a year and a half.

I have seen a couple of emails come through about them doing scheduled maintenance, but other than that, I have not had any issues with any downtime. If they did have any downtime with their cloud application, I did not notice it. I might not have seen any alerts for that short period of time. If they were down, nothing has been to the level that I noticed it.

We only have 150 devices here. We have not had any issues with scalability because we are not that big of a shop.

I have called them two or three times, and each time, they have been able to resolve my issue very quickly. I always try to do things myself using their documentation, but I had a little trouble finding the documentation for my Fortinet FortiGate issues. Another thing that could be improved is their documentation and knowledge base, but in terms of their support personnel and time for them to get a resolution for me and get me up and running, they did a great job.

Positive

I did not use any other product previously. This is the first time I have used this type of product. I do not have anything to compare it to, but I have nothing but good things to say about Auvik.

It is deployed in the cloud. It was super easy to deploy. The Fortinet firewall required some configuration changes on the firewall itself. I did that with the support folks on the line. I was able to do the rest of it on my own without any problems at all. I just had a few issues with the Fortinet firewall.

It was all deployed within one day.

I did it all myself except for the two firewalls. I had to have a support call to get that done.

The pricing is good for what it does. It has been a few months, so I do not remember exactly how much it was. I believe for our network here, it was about 2,000 a year, so the pricing was good.

A lot of printers and things of that nature are not one of the charged devices.

We went directly to Auvik. I got an email about a trial. I installed it and thought how useful it would be to be more proactive than reactive with the types of issues that it spots.

The only advice I have for new users is that if they have Fortinet firewalls, they will have to do some command line configurations to their Fortinet to prepare it to be able to send the alerts to all of it.

I have heard of Auvik's SaaS Management product. They sent me an email about it recently, but I just read the headline of the email and moved on. I do not have a solid understanding of what it does other than maybe keeping track of your software as a service license. I am not familiar with it that much.

I would rate Auvik Network Management a nine out of ten for what we use it for.

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.

Auvik's interface is one of the most intuitive interfaces I've used.

The ease of use makes troubleshooting network issues easier and faster.

Auvik's network map and dashboard offer a real-time overview of our network. I rely on it daily, starting my workday by checking it for any potential issues and then adjusting my priorities accordingly.

I found the dashboard very easy to understand and easy to manipulate and customize.

The network map dashboard typically provides me with full network visibility. I haven't encountered any instances where something wasn't displayed within the network from Auvik's perspective. Even for devices where I haven't explicitly provided credentials, Auvik still manages to identify and display them, ensuring comprehensive network visibility.

I am the only technician that uses Auvik in my organization and it has empowered me to come up with better solutions to solving our tickets.

Auvik has helped decrease our mean time to resolution.

Auvik's value became immediately apparent when we needed to investigate an issue causing a server cluster to intermittently shut down. Auvik accurately detected and reported the problem, pinpointing the exact location and nature of the fault, including the specific port experiencing instability. This information was invaluable in resolving the issue quickly. We have encountered other scenarios where Auvik's responsiveness surpasses even our power distribution units. For example, in an instance of power loss within a specific room, Auvik alerted us significantly faster than the PDU itself. This enhanced speed significantly improves our ability to react to critical situations.

Auvik allows me to spend less time on setup, maintenance, and issue resolution. 

The cloud monitoring portion of Auvik that provides visibility into each piece of my infrastructure is the most valuable feature.

The use of a mobile app would be very beneficial because sometimes I cannot access a computer. Additionally, I believe that more monitoring could be done on certain devices, especially since we have credentials for them. Ideally, there should be more comprehensive monitoring for endpoints, such as switches, firewalls, workstations, and even servers. Support for other hypervisors would also be valuable.

I have been using Auvik for just over one year.

The Auvik website experiences occasional stability issues, which may coincide with their frequent maintenance windows. Although they perform maintenance at least once a week, my monitoring has not identified any significant delays in reporting.

Auvik is highly scalable. While the price does increase as it scales up, it is remarkably easy to deploy, even to new sites. I have done this myself. I have also restructured the network topology twice since I started using Auvik, simply to improve organization, and it remains very easy to scale or adapt the configuration.

Previously, I used PRTG. The main differences between PRTG and Auvik are the user interface being much easier to navigate, and Auvik being much more intuitive in indicating what it can and cannot scan, as well as what it is currently scanning. With PRTG, we had to manually select and choose what we wanted to be monitored, which required a significant amount of setup time. In contrast, I found Auvik to be much easier to set up and get running quickly.

The previous solution lacked many features that Auvik provides. For instance, it didn't offer bandwidth or power consumption monitoring. We needed to go into specific devices and enable reporting for each one individually, like for power devices such as rack-mounted APCs or PDUs. Usually, configuring these devices requires manual intervention. Auvik automatically discovers and monitors them, allowing me to access reports directly through its interface. This information, combined with other reports like server power-down events, helps me map the order of events during a system crash. I can analyze which devices failed first and work my way back using the network map and alerts. No other tool offers such ease of use and diagnostic capabilities as Auvik's built-in features once a device is connected.

Furthermore, Auvik provides extensive functionality for firewalls and network switches. The configuration backup feature, which was a key factor in our decision to purchase the software, is unparalleled. It securely stores configurations in the cloud, enabling quick redeployment and comparison between backup points to identify changes. Additionally, it allows for easy reversion to previous configurations if necessary.

We encountered a scenario where an older switch in our server room lost power. Auvik notified me of this event, and the switch automatically reverted to an older firmware version. Recovering the lost firmware required redeploying a configuration file, which was readily available through Auvik. Restoring the configuration was a simple click away. This incident highlighted how Auvik goes beyond mere monitoring by actively facilitating troubleshooting.

The initial setup was incredibly simple. I was brought into an onboarding meeting with just two or three others, and within a couple of weeks, I had a firm grasp of the platform. I also took advantage of the excellent training offered. 

The integrator would answer any questions I had, but for the most part, I was directed to their knowledge base. This prompted me to take the courses they offered, including a certification for the tool. Completing these courses on my own proved to be much more efficient than waiting to schedule meetings with the integrator. Consequently, I was able to learn the tool independently.

The implementation was completed in-house.

The pricing is very good. It's extremely competitive and I've shopped around on Auvik to see if there were cheaper solutions like Traverse, and there's no comparing the pricing. No one can beat their pricing right now.

Auvik monitors my core switches free of charge. I only pay for my firewalls.

I evaluated SolarWinds and another solution, but neither met my needs because they required extensive setup. Auvik, on the other hand, simplifies the process significantly. As a single person in my department responsible for the entire infrastructure, networking, cybersecurity, and other tasks, I rely on efficient tools. Auvik allowed me to seamlessly integrate into my new workplace and gain immediate visibility into the entire environment. Implementing the other tools would have been a much more time-consuming process. Auvik offered a smoother, faster, and easier implementation within my company.

I would rate Auvik a nine out of ten.

Maintenance on Auvik is only performed when we are aware of downtime. The only reason I have ever needed to perform maintenance on Auvik is to unmanage devices that are looping alerts. While troubleshooting, I may occasionally need to make changes to Auvik, but there are very few day-to-day tasks required. Once configured, Auvik requires minimal maintenance.

For anyone evaluating Auvik, my advice is this: understand that while this tool won't fix problems on its own, it will help you diagnose and solve issues more efficiently and logically. It provides a visual representation of your network that you wouldn't normally see unless you were physically present in the server room. But with Auvik, you have this vital visibility from anywhere you have a computer. That's a major benefit in itself. Additionally, Auvik is very quick to set up and easy to deploy. You can be up and running in as little as a week, which is a significant advantage over other network monitoring solutions.

Our network infrastructure is monitored by Auvik Network Management. This includes firewalls and network traffic. By using Auvik, we gain data and analytics that fuel our diagnostics, alarm systems, and overall network environment insights.

We decided to implement Auvik after struggling to find a network monitoring solution that ticked all the boxes. We needed a cost-effective option with a user-friendly interface, backed by a responsive company committed to ongoing product updates. Unfortunately, the market seemed to offer outdated, once-great products or solutions prohibitively expensive for small businesses and MSPs like us. Thankfully, our experience with Auvik has been good. Both our dedicated sales representative and the onboarding technical support team have been phenomenal.

Despite the usual setup time – an hour or two for getting things connected and entering credentials – the platform started pulling data from our devices almost immediately. It was practically instantaneous, aside from the standard management deployment time. Interestingly, the network map took a bit longer to figure itself out compared to the platform itself. The platform started showing me interface details, traffic information, and even automatically identified our WAN connections. We did have to set credentials later, and thankfully, we had backups of our devices ready beforehand, since it seemed like the platform wanted that information before the network map fully visualized everything. Overall, the deployment process was remarkably quick and easy.

Last Sunday, I encountered an issue that the dashboard interface helped resolve quickly. I could easily locate the specific device on the map and clicking on it brought up all relevant information. This allowed us to directly investigate the problematic port, view its traffic status up or down, without the need for a more cumbersome process. Traditionally, we would have had to VPN into the network, log in to the switch using its credentials, and then identify the specific port involved. The dashboard streamlines this process, saving time frequently. While it may not be a massive improvement, it offers a noticeable efficiency gain in our mean time to resolution.

Our company is still in the early stages of adopting Auvik, a monitoring platform that can be used for all of our customers. This means that we will eventually have one platform for all our alerts and for our technicians to access. This will simplify things internally for our company by reducing the number of platforms our technicians need to be familiar with to support our clients. It will also reduce the amount of documentation we need to maintain. With Auvik, our technicians will spend less time on maintenance and troubleshooting because they will only need to learn and use one platform. Currently, our technicians haven't started using Auvik yet, but the plan is to move away from all the various monitoring solutions we've been using for different customers and consolidate everything onto this one platform. Once our technicians are using Auvik, it will make our jobs significantly easier and faster.

Auvik stands out for its ability to combine network and per-port traffic inspection with log aggregation and data flow analysis in a single platform. This comprehensive approach is rare in network monitoring solutions. Even more impressive is that Auvik offers these high-end enterprise features at a cost-effective price. Traditionally, such capabilities are only found in expensive products. The combination of powerful features and affordability made Auvik a very attractive choice for us.

The Auvik interface has a modern look and feel in terms of its color scheme and layout. However, some elements are arranged in a way that I find counterintuitive. As a company with a web and application development team, we have a strong focus on user interface and user experience. For some features in Auvik, the placement of buttons and functionalities doesn't feel optimal. We've had to consult our representative several times on how to find specific options. For example, editing a device requires navigating through the sidebar to a specific category and tab, then selecting the device, line item, and checking a box before finally reaching the edit button. Additionally, the placement of buttons seems inconsistent across different sections, making the overall workflow less intuitive and requiring more training to become proficient.

My ideal real-time network monitoring would involve seeing all my data at once, including connection speeds and throughput. While Auvik's automated network map is visually appealing and generally accurate compared to competitors, it lacks some key features. For example, unlike a competitor's recent feature that shows traffic between trunk connections, Auvik only displays a single color for connection links, indicating wired or wireless status. This doesn't provide vital information like link speed or potential problems. Additionally, connections with momentary issues simply disappear from the map, which is frustrating. Auvik could integrate valuable alerts and insights from other parts of the platform directly onto the map. This would highlight potential issues with specific devices and their connections. While I acknowledge ongoing development efforts, there's still a significant gap in desired features. Another limitation is the lack of manual map editing. For instance, our server has multiple Ethernet connections entering a single switch, but the map erroneously shows them spread throughout the building. With no way to manually adjust this, the map's accuracy suffers. While Auvik's map is aesthetically pleasing, I wouldn't rely on it for complete accuracy.

I've had some trouble using Auvik's device proxy, which allows technicians to connect to network devices through Auvik's platform. The Mac software I need isn't fully functional yet, so I might be doing something wrong, but other products like Domotz work flawlessly. One of the main reasons we chose Auvik was to eliminate the need for VPNs, on-site PCs, or network tunnels for technicians to access devices. This would reduce our equipment costs. While the pricing is fair overall, the jump between plans is significant. For instance, their higher plan offers features like NetFlow statistics and analytics for firewalls, which require more data and rightfully cost more. However, the entire client site is included in that plan, and there's no option to pay extra for specific devices. I'd be happy to pay more for those features on select devices, but the current pricing structure prevents me from getting them. This seems like a missed opportunity for both Auvik and us. Not all my devices need the extensive logging and data collection offered in the higher plan. Network switches and access points, for example, have their own controllers that handle SysLogging, so I wouldn't need Auvik for that. However, I would like to pay extra for those features on our firewalls and routers. In the current situation, neither side benefits. If we pay for the higher plan, our costs increases, which will eventually impact our customers' prices. However, convincing customers to pay for this one additional feature within the entire monitoring platform is difficult.

I have been using Auvik Network Management for one year.

Throughout this process, I've primarily relied on my representative for assistance. While I haven't directly contacted their technical support line, my representative has involved them on my behalf. This may be a slight deviation from the usual procedure, but it has still allowed me to reach the appropriate people.

The technical support team has been very responsive in identifying and resolving any technical issues I've encountered. They were able to quickly understand the situation with minimal questions. Additionally, I appreciate the granular control I have over their access to client data. I can grant them temporary or read-only access, which allows for collaborative troubleshooting without compromising security or hindering our learning experience.

Overall, I've been very impressed with the technical support team's knowledge. We understand they aren't responsible for diagnosing internal network issues; their focus is on supporting their platform and ensuring our connection to network devices. So far, their responsiveness has been excellent.

Prior to implementing Auvik, we experimented with a number of network management solutions. These included PRTG, Domotz, LibreNMS, and the built-in NinjaOne option. We also evaluated SolarWinds. We've explored a wide range of options. Our goal is to find a standardized solution, and we believe Auvik fits the bill. PRTG was expensive so we could only use the free version that only allowed for 1,000 sensors, proving too restrictive for our needs. LibreNMS required a high level of technical expertise for deployment and maintenance, which wasn't feasible for all our technicians. SolarWinds simply didn't meet all our requirements. While NinjaOne is still in active development. We may revisit it in the future. Overall, Auvik strikes the perfect balance between functionality, ease of use, and scalability.

The deployment of Auvik requires installing an agent and some information. The deployment took around one hour. 

Although Auvik is a cloud-based solution, it requires software installation on a computer or server within our network. This initial process can be cumbersome. In our experience, the provided API key wasn't functional, and creating separate API keys isn't an option. Instead, we need to create full user accounts, which feels unnecessarily complex.

Once the connector is installed, the user interface presents challenges. Management credentials and network scanning configurations are located in separate areas. While the deployment section attempts to consolidate these settings, it becomes irrelevant after the initial setup. Ideally, the interface should streamline the initial configuration process, instead of requiring users to navigate through various menus.

Another concern is the requirement for generic credentials. Instead of specifying credentials for each device, we must provide generic ones that are simply tested for functionality. This raises security concerns. These generic credentials are tested against various devices in our environment, even those for which they are not intended. While we trust our security measures, a compromised device could potentially allow the Auvik connector to expose these credentials to unauthorized devices. Ideally, the system should allow for specifying credentials on a per-device basis, eliminating the need for generic credentials and the associated security risks.

The implementation was completed in-house.

I came to a surprising realization about Auvik's pricing. It turns out they only charge for routers and switches! This means all our access points, security cameras, camera servers, and other infrastructure are monitored for free. While the client understandably wanted the server on-site, most other devices are a bonus. This is a huge advantage – with a typical network, we might have one firewall, three switches, and 60-70 access points. With Auvik, we only pay for the four core devices, bringing the cost down significantly. In my opinion, Auvik could advertise this benefit more clearly. Many other platforms charge for every device, so Auvik's free monitoring for a large portion of the network is a game-changer. It not only helped us make the decision but also benefits non-profits we support. The fact that they're confident enough in their platform to offer this makes Auvik a truly valuable and supportive solution.

In the end, we were deciding between Domotz and Auvik. Auvik's initial pricing structure was a concern. Their tiered system required a minimum number of devices per tier to get a reasonable price. While their desire to be profitable is understandable, this presented a hurdle for us. However, Auvik impressed us with their willingness to work with us. They emphasized that they wouldn't lose a customer solely on price, as long as open communication existed. This flexibility in finding a solution was a major factor in our decision. Another reason we chose Auvik was the user interface and user experience. We found Auvik's interface to be superior to Domotz's. Additionally, Auvik's pricing based on individual devices, rather than NetFlow, was a significant advantage. This meant we wouldn't be penalized for devices with minimal traffic or high port counts. From a business standpoint, this eliminated the need to constantly monitor billing for small variations in device usage. With Auvik, we pay a fixed cost per device and receive all the necessary features, regardless of its size or complexity. Consistent and predictable billing was another key consideration in our choice.

Auvik Network Management gets a solid eight out of ten from me. While the network maps and user interface could be improved, the software delivers exactly what we need out of the box. It connected to our devices seamlessly and provided valuable analytics data and information logging. The setup process was straightforward, and the learning curve wasn't steep.

We're currently in the early stages of implementing Auvik, which means our existing software is still operational. To ensure a smooth transition, we typically allow a three-to-four-month overlap period for new software before fully integrating it into production. While I've been the primary user so far and can provide initial insights, our help desk technicians haven't yet been granted access to Auvik.

There is a minimal amount of maintenance required, primarily for alerts. The default settings include alerts for all devices, but not all of them are relevant to our needs. We simply need to adjust these defaults. Aside from that, the system is truly "set it and forget it." It will notify us of any problems, and as an IT company, we have internal procedures to log in and investigate any alerts. However, there is no ongoing maintenance required after the initial installation.

Setting up Auvik is smoothest when your network devices are already configured for SNMP. If you're unsure about your equipment's SNMP settings or lack a configuration altogether, take some time to familiarize yourself with your devices before proceeding. Having your device credentials readily available will also expedite the process. As long as both SNMP logging and credentials are prepared, Auvik deployment becomes a breeze. However, investing a few minutes to learn the Auvik interface beforehand will pay off in the long run. A grasp of the interface will make Auvik exceptionally user-friendly and position it as a powerful and functional solution for your needs.

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. 

Auvik allows us to get on top of issues before they become an outage. It alerts us about when dropped packets on an access point get out of hand, so I know to look at that. It speeds up the remediation time for network issues by about 25% to 50%. I get a heads-up about all the potential issues in my network. 

I don't have to worry as much about the network because I have something telling me when issues are happening, so I can be proactive. If a situation is happening, I know where to look because I've gotten emails about what's going down before the problem hits my desk.

I know about power outages at our facilities before somebody calls me about it because Auvik sends me a report that the network at one of our facilities is offline. I can investigate and find that the power went out long enough that the battery backup for the switch gear ran out. 

I have peace of mind because Auvik constantly records the state of the network configurations on all of my devices, and it provides one place to find everything. I don't need to waste time searching a million different settings in a million different pieces of software and endpoints. It's given me back some time. It has saved me time because I don't need to create Visio drawings of our network. That was massively time-consuming, and everybody does it differently. Nothing ever looks great, but Auvik's printout of the network map looks phenomenal.

We don't have a global footprint, but we utilize multiple buildings. Auvik has given us a lot of visibility by allowing us to see what's going on in other buildings a lot easier. We can remotely log into networking devices through Auvik, so you don't have to manually open a window and remember the login credentials. Everything is stored inside the app on the cloud. It's easy to jump in and hit the ground running instead of trying to look up an Excel document or a OneNote with information on how to get into the device.

We use a product called PDQ Inventory to keep track of our software inventory, but Auvik helps us manage our network inventory, letting us know what's on the network, and where it's located.

The network flow piece is the most useful. We can identify the busiest parts of the network based on the reporting from the switches about what is utilizing the most bandwidth on specific switch ports. I can narrow down which segments of the network might be having issues.

Auvik has everything I need in one place. I don't feel like I need other modules to use the product. In the past, we had about five different pieces of software, none of which did anything like what Auvik does. It provides a whole network map breaking down all the connections and ports so that you can drill down. I had nothing like that in the past that let me track everything. It has helped to see the state of my network at any time.

I like Auvik's cloud-based solution. I prefer to have a collector that pulls all the information and sends it up to the cloud so that I can access that from basically anywhere. It's all multifactor authentication, so I don't have to worry about people hacking that. At the same time, I also love that I don't have to tie up computing resources here in my data center locally. I like that better than setting up something that collects it on-premises. Then I have to back that up somewhere. It creates a larger overhead to maintain.

I love the network visualization because drawing the network out in Visio was becoming almost impossible because of our network's size. The ability to show a dynamic, updated view of our network has been a huge help. I enjoy that because you can drill down into visualization and focus on different segments of your network

When I change IP addresses on a device or on a server, I have to wait for Auvik to figure out that change. It will tell me the device is offline until Auvik scans the whole subnet again and finds it. If I change 25 devices, I'll get 50 emails in a short time because they've gone offline. 

I'd love the ability to change that where I can update that device with the IP address without it going offline. That goes against the idea of a system that dynamically scans. It's information overload sometimes when you need to change a bunch of factors. You get inundated with emails. I would almost love a button whenever you first log in that says maintenance window, and then it would maybe take some of those alerts away.

It's fairly intuitive but sometimes you have to search for things because it's hidden in the user interface, so I think that could be improved a little bit. The search could be better because they have these strange search terms. Instead of being able to look for what you want, you have to lay out the query in a specific way to get results.

We've also been dealing with some weird bugs lately. We get alerts on miscellaneous items that go offline and online all the time. I've reached out to support, and they said that they've got a fix that they rolled out. However, we're still experiencing the issue, so I've got to work with them to fix that. They seem to be on top of the support.

I've used Auvik for a little over a year. 

Auvik is pretty stable. I often get emails about preemptive maintenance outage windows, but there's never been a time when I needed to access it but couldn't. My computer also struggles with visualization because it's a little older. I'll usually remote into another computer that handles it better.

It seems to be like they would be able to handle quite a bit, especially being cloud-based. I feel that if I had to triple or quadruple the size of my network, they would be able to handle it really well. It doesn't seem like it would be tough for them.

I rate Auvik support eight out of 10. There have been times when it has been excellent. However, I still have some issues where things go offline and come back online. They reached out after the ticket to ask, "Hey, would you recommend Auvik to your colleagues?" That was the first time any company has reached out to me, so it sounds like they care about that score.

Positive

I used a free solution from a company called Spiceworks. It was a network monitoring software that listened to SNMP traffic. However, it got overloaded with the size of our network and wouldn't function how I needed it to. The alerts were out of control. It was too much for me, so I turned it off and looked for something else.

We set up Auvik over a demo call, and they said they would set me up with a production-ready environment. I would have 30 days to play with it. After that, they got me into a little bit more in-depth setup. It took me and the technician 30 minutes in total. About 15 minutes after the installation, we were collecting data and setting up alerts.

It's phenomenal how quickly Auvik was set up. It reminded me of another system that I used called Action1, a remote endpoint management solution. We installed the collector for that, and within 20 seconds, it had installed its agent on every machine with a domain login in my environment. Auvik was very similar to that. It was up and running and collecting data within minutes.

The network map started to populate the same day. It takes a while to get most of the map worked out, but it started populating within an hour or so. My previous solutions were fairly easy to set up. Still, I never got them to work in a way that served my purpose, and I ultimately uninstalled them because the features weren't good enough to justify the amount of time it took to set them up and get them working. 

The majority of them were free tools that I had looked at before going with Auvik. I  generally understand why they were free, which led me to the point of needing to buy a service where I had support. I need support to fall back on if I don't know what I'm doing rather than just sort of meandering through a free tool.

Auvik doesn't require much maintenance. Suppose I'm looking for some information on why something's happening or what a device is, and I don't have any information besides spreadsheets. In that case, I go to Auvik to get an idea of that device because it has some good guesstimates based on a MAC address. 

We saw value almost instantly because of the visibility we get into the network. If I'm curious about why a device is dropping offline, I have a map to see what devices are offline and dig into what's going on. I can check to see the state of the network if a lot of things are going offline. We didn't have that before. We were able to get value out of it within the first week.

Auvik is affordable. The license was under $4,000 annually for our setup. That covers a lot of switches, firewalls, and integration. It was well worth the price.  I think it's around $20 per device per quarter.

It's the best monitoring software we can get at that per-device cost. They get pretty aggressive with pricing. When you add network switching that will be managed by Auvik, you'll see it on your next quarterly bill. You have to choose not to manage it whenever you install it if you don't want to be billed for it. You can keep your costs under control if you don't want to manage a device you're adding to the network.

I looked at SolarWinds. Their problem was that they had just been hacked at a pretty high level, and I didn't want anything to do with a vendor that had any hacking going on. The other one was called Netwrix. We had a demo of ManageEngine, but setting it up was like pulling teeth. I was in the middle of the demo with the people, and nothing was working right.

With Auvik, we were up in 15 minutes after downloading the collector and getting it on the network. It started populating data without the need to provide a lot of information. It went so smoothly. That sold me on it.

I rate Auvik eight out of 10. My advice would be to try the demo and kick the tires as much as possible to find out if it's the right tool for you. Annual pricing is cheaper, but I believe they do monthly licenses if you're still not. Utilize it as much as possible before signing a contract.