Auvik Network Management (ANM) Reviews

Auvik helps us manage all our devices on the network.

Because we can do different things in one place, like investigate network issues, it has definitely saved us time; something like 20 percent. It gives us all the necessary data to make a decision in an instant. In addition to saving us time, it saves us work.

It also helps keep device inventories up to date. We are a small team but it helps us delegate low-level tasks to junior staff. And the fact that it tracks inventory gives us visibility into all devices and that obviously helps us keep everything up to date. It saves us about 20 percent of the time we would spend on that otherwise.

We've got visibility into all our devices, starting with routers and switches—networking devices—through to printers and user stations as well. It gives us an account of what is currently connected to our network.

And with the TrafficInsights option, I have information and statistics regarding our traffic and what is currently being utilized in terms of bandwidth. I use it quite often to establish if our bandwidth is fully utilized or not and whether there is any slowness on the network.

Another helpful feature is that you can remotely connect to a device directly from Auvik.

Apart from that, it's monitoring software. Obviously, you get alerts and you can configure them, which is a useful feature as well. You don't need to look at the dashboard all the time. Instead, you can rely on the alerting feature. If something goes wrong, you simply get an alert via email.

It provides us with a single, integrated platform. We can do quite a few things from Auvik. We can connect to different devices and we have visibility into what's connected to the network. There is a lot of useful information, like IP address, network address, as well as insight into traffic, time, date, what protocol is being used, and how much bandwidth is being used. It definitely gives us one platform where we can investigate quite a lot of stuff.

Another good feature is the network mapping and topology. It's clearly depicted on the dashboard, so you can see what's connected to what. It's designed well.

I would like to see improvement in terms of its integration with other applications and systems. I know that they are adding new systems. However, there is still work to be done there, such as integration with MS Teams. That is not working great for us. And integration with ticketing systems would be helpful. There is an integration module for the big systems, like ServiceNow, but we're using something else and it's not integrated.

I have been using Auvik for around two years.

It is stable. We haven't had any problems from the Auvik side. Updates haven't broken anything. There has been no Auvik downtime. It's all working pretty well.

It's definitely scalable. I don't know what the maximum is but we are adding new devices all the time. It depends on how many devices your license covers, but apart from that, there are no real restrictions.

We have one main site with up to 1,000 users at the moment. We also have about 15 external locations, which are like shops, but the majority of our users are working at the main site. We also have some remote solutions, VPN, for the users. It's a hybrid environment with Microsoft Office 365. Most of our stuff is in the cloud along with some on-premises solutions.

The solution's technical support is really good. There are different ways to contact them, including phone, chat, and email. You can easily contact them. They also have a really good knowledge base system where you can actually find resolutions yourself.

Positive

We still use multiple applications for managing our network, but nothing specifically like Auvik. Auvik gives us one place to do different things. It's easier to see the information because it is displayed on the dashboard in a nice way.

I was involved in the deployment of Auvik to some degree. It was quite straightforward. They gave us good guidelines and we just followed what was requested of us. If we were in doubt, we could always go back to them, and they would guide us through the process. Overall, the process was quite straightforward.

I don't remember how long the onboarding process took. I think it was about one month. It involved two people from our side. One was our senior infrastructure engineer, who is my colleague, and me, as IT infrastructure engineer.

It doesn't require any maintenance. Everything is in the cloud. Apart from updates from Auvik, we don't really have to touch it or maintain anything.

I'm not involved on the cost side of our solutions, but the price must be good enough because we have renewed the license.

I wasn't involved in the decision-making process, but I would guess that cost was really important, as we are a charity. If not the most important, the cost of the system would be one of the deciding factors.

I've used SolarWinds in the past, and Auvik is definitely a good system to have on your network. It helps with your work and saves time. I would definitely recommend it. 

It's not too difficult to use Auvik's monitoring and management functions. There are quite a few settings and a lot of information. In the beginning, it can be a bit overwhelming. There are a lot of tabs on the left-hand side. But, the longer you use it, the easier it becomes. Ease of use is definitely not the first thing we look at. It's a bonus feature. The primary purpose of Auvik is to monitor our network. As long as that's being done, that's our priority. If it's easy to use, of course, that's more convenient. It is a big plus. But it's not our first priority.

I would advise going to the Auvik Training Portal where you can go through a lot of videos and short modules. You can learn more advanced techniques for using Auvik, and maybe a little bit about the more advanced settings you can use. The solution has many options and settings, so it's good to do some reading and a bit of study to use it to its full potential.

It's a very good solution to have, with loads of information in one place. It helps us in our investigations and saves us a lot of time.

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.

It has made monitoring a lot easier. It has made finding devices and charting network maps for onboarding companies easier. If you are a tech and looking at a company for the first time, you can just look at the network map and quickly get an understanding of how big it is, how complicated it is, how many network tunnels there are, and what's the main firewall or the center of the network stack. It's super easy to quickly acclimate to a new network and troubleshoot up or down a network stack. I find that fantastic.

Being able to visualize the network mapping/topology for the organization is its best feature. It's very reliable. It'll more likely add a device that's not important than it will miss an important device. It does it so quickly and automatically, and not a lot of time is spent managing the network map. Every once in a while, once or twice a year, there'll be an alert, and we investigate it and we find out that it's just an obsolete device that was never removed from the map. So, you just delete the device. Other than that, it takes care of itself. It's fantastic. I don't have a lot of criticisms of it other than just keeping it up.

It's very intuitive when it comes to network visualizations. It is very easy to pick up, and it's great that there's a little key there that always tells you exactly how it's connected. It was probably the easiest thing to learn. If you aren't accustomed to Auvik, you can just look at it for 5 or 10 minutes, and you can absorb it. You're then good to go. You can very quickly and easily understand what you're looking at.

It has helped reduce repetitive and low-priority tasks through automation. It takes a lot of tweaking to get the alerts just right, but a lot of the repetitive tasks that we do have been automated. They've been automated for a long time, and they exist in very niche parts of our business that aren't really related to Auvik. The reduction is hard to measure, but it's a good percentage. In terms of the after-hours calls, with the emergency issues coming in, after two or three guys who set up Auvik went through the alerts and optimized it, with the number of things that took care of themselves and alerts that took care of themselves, we started getting fewer calls. Percentage-wise, there is a 20% or 30% reduction. It wasn't a huge chunk at the beginning, but it was noticeable once they got everything ironed out with Auvik.

It has affected our IT team's visibility into remote and distributed networks globally. We're a service provider. We manage a lot of networks. They range from a single network stack to multiple locations with multiple distribution frames that are all tunneled into each other. Before Auvik, it was pretty difficult to get an idea of how something was set up because we were just looking at configurations and talking to other people. It took a lot of experience to get used to a single client. Now, when everything is set up, if we want to understand the network, we just go into Auvik, and we can see the whole network.

It's a big part of our networking and monitoring. I'm in Auvik a couple of times a week. I don't specialize in networking, but I still end up looking at Auvik a couple of times a week to solve something, or I have to work on an alert that came specifically from Auvik, and I have to investigate. Aside from the UPS battery alert issue, which is obnoxious, most alerts are pretty easy to understand, easy to follow up on, and easy to resolve.

It has had an effect on our IT team’s availability. It makes the work of the IT team easier. We spend less time troubleshooting, and we are more available to work on other things. It has saved a considerable amount of time. We only have one network engineer, but everyone else is capable of working on networks. Auvik has made it easy enough to point to the issue. So, the network engineer can just focus on the really important and really intensive things, and everyone else can work on the intermediate things by using Auvik. Previously, it would take twice as much time for somebody like me to figure out a network problem.

It's very easy to delegate low-level tasks to junior staff. The API is integrated with ConnectWise. So, the alert comes in, and the dispatcher lets everybody know, and then any of the techs here can work on the alerts. With the information that we have in Auvik, we're able to very quickly assess the first thing that we need to do. We almost always get it resolved in time unless it's an ISP issue.

I really like the network map. It's probably the most useful feature because we have monitoring set up in other systems too, but seeing what's connected to what and where it is makes a lot of things a lot easier to troubleshoot.

The uptime and downtime information is valuable. It is pretty reliable to know when something goes down.

I find it pretty easy to use the monitoring and management function of Auvik. I passed the test on the first try, and it's all very intuitive. I like the menus, and it's pretty easy to get through things. There are some things that are a little bit more complicated, but there was nothing I wasn't able to figure out. Rarely, I would have to reach out and ask somebody to show me how to find something in Auvik or how it works. In terms of accessibility or how easy it is to get into it, it's pretty easy. Even setting up devices for configuration polling and SNMP is pretty easy.

When it comes to monitoring, Auvik provides a single integrated platform, but I feel it could do more things. If it could facilitate device upgrades, that would be great. 

It also has a feature where it passes alerts along. So, a device will have an alert, and then Auvik will pick it up, and then the API will create a ticket through Auvik, but the alert will be very vague. The one with which I had the biggest problem, more than anything else, is the alert specific to a UPS. There is a specific alert when a UPS's battery hits five years old, which means it needs to be replaced regardless of whether it's alerting or not, but the way the Auvik finds the UPS and gets the alert makes it almost impossible to tell which UPS it is. If the UPS has a web portal or a web GUI that I could go into and take a look at the battery, life is great, but we had one tenant where all the UPSs didn't have that. It took forever to figure out which one had a battery that we had to replace. Its monitoring is great, but the integrations could be better.

Overall, it hasn't provided a single integrated platform for us. We still have to use other tools to shore up where Auvik is lacking. For the most part, Auvik helps keep device inventories up to date, but it's not perfect. One of my least favorite things is that people bring in devices, their devices get retired, and then they just go off. A lot of times, we wouldn't know if it is something that we need to get back online as soon as possible, or if it's something that just went down. There were times when little switches that are under people's desks would be mislabeled with critical network infrastructure. Someone kicked a switch or something like that, and it went offline. We got the alert, and we wondered where it is and how could we get it back online. We called the company, and they were just like, "Oh! It's this little thing in here. Just plug it back in." It was just used for the printer. There would also be devices that were being retired, but the service desk or other teams wouldn't know about it. They would spend half an hour trying to figure out what was going on. So, even though it takes care of the inventory, there is a small amount of auditing that we still have to do. That's normally done because we're getting a lot of false positives, which probably is a good thing. It's better to get a false positive than for it to not alert when something important has gone down.

It's as good as anything else out there. It isn't better or worse than the systems that we already have in place. We don't use it for device inventory because we have other systems that keep track of devices and configurations. When I think of device inventory and Auvik, it is to know whether something that's currently online needs to be online. I would never look at Auvik to determine how many computers are currently at a location. I have two other systems that already do that for me, and they do a better job than Auvik. For the systems that we use, we have agents on computers. So, they give us an enormous amount of information about computers and things that are available at a location, or just an asset list for a client. Things that we can do remotely through them are pretty incredible. If Auvik wanted to be competitive, they would have to get into an area their competitors or the other companies do in terms of putting agents on things. That's a whole different thing than just SNMP polling.

We started Auvik at the beginning of 2020 because I remember taking the Auvik test while working remotely during COVID.

Their support is fantastic. If I have a problem with Auvik, I just open up a chat to interact with somebody, and they get to me in a minute or two. They almost always get it resolved just through chat. I don't remember ever having to call Auvik.

The central services people tell me that Auvik has quarterly reviews with our company. So, they follow up with us all the time. 

I would rate their customer service a 10 out of 10. They get to me immediately, and they always help me solve the problem, and they're always nice. I've probably talked to the same three guys every time.

Positive

We were using Audit API, which was pretty useful, but they were mostly Windows machines that had our agent servers and workstations. So, a server workstation would go down, but all you would know is that the server is down, or the whole site is down. We would have to do a lot of digging on our own to piece together:

• Which devices are there?
• What does the stack look like?
• What's the first thing that we need to troubleshoot?

We definitely tried to make the Audit API work, but the consensus was we needed something better to get these things done faster so that we weren't spending so much time during discovery especially, or we weren't spending so much time chasing alerts after hours.

Once we got Auvik, that became way easier. Instead of having to dig to figure out how it's set up, we could immediately look at Auvik and determine what the first step needs to be. It has cut off a huge amount of discovery. We have so many clients, and you have to be here for a long time before you know everybody, and even then, some clients don't really have problems. You're only looking at them a couple of times a year. So, if you have a great memory, good on you, but Auvik really made it a lot easier for service desk techs. We're not in the network all the time, but we troubleshoot networks frequently enough, and it's important that we are able to do this quickly and correctly.

For us, it's better that it's a cloud-based solution. I don't know about other companies, but we're remote to almost all of our clients. So, it's all cloud.

I did a lot when it comes to getting configuration polling working for firewalls, but other than that, I haven't been a part of its initial setup. The central services and networking teams got it set up, and then once it was ready, the techs like myself took the Auvik test. Once we passed, there was some tedious work that needed to be done at first setting up SNMP on networking equipment and making sure configuration polling was working, but that was about it.

It did take a while to set up Auvik, but that's because we have a lot of companies that we monitor. Everything was running smoothly within about six months we started working with it.

We have absolutely seen time-to-value with Auvik. It has cut down after-hours support. We're spending less time in the middle of the night trying to figure out why a network is gone so that we'll be up in the morning by the time people arrive for work. That was just huge for us. There are fewer tickets on the board during the day, or we can resolve the tickets we get faster.

We have seen a reduction in our mean time to resolution. In my experience, it has just cut that in half. We can just look at Auvik, and we know what a network stack looks like. We can begin planning how we want to approach the problem.

I don't know anything about its pricing, but I would say Auvik is worth it.

I would rate it a 9 out of 10. It works superbly. It has made my job a lot easier. It made me understand networks so much better and more quickly too. I love Auvik, but they could do more with integrations. If we could just do everything through Auvik, such as push firmware through Auvik, and if Auvik was better at telling me which UPS has a battery that needs to be replaced, I would give it a 10 out of 10. 

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.

Before we got Auvik, we had to write scripts to get every device's state, to see the upload speed and download speeds, and whether there was any abnormal download or upload bandwidth. Because we develop network drivers, these are very important metrics for us, so that we know if there is any bad traffic in our network. Previously, we had to update our scripts every time there was an update to our routers' firmware. And if we had to update our requirements, we needed to rewrite the scripts and redeploy them on all of our routers. That required a lot of manual work. Auvik helped us eliminate that work.

Previously, when we managed the system, we needed to write our own script to run a single command on all the routers. Now, we can do that on the console. We can select everything and run a single command for all the devices with a single click.

A lot of tasks used to be repetitive work, like for new-device support. One of the really great points about Auvik is that it helps to reduce all that toil, including debugging scripts and maintaining them for the latest version.

The most important thing is that you can control everything, every device, all at once. As a unified platform, it handles all kinds of devices and all kinds of brands. If we decided to buy a new brand of router, we wouldn't need to check the manual and write new configuration scripts or record configuration macros ourselves. Auvik handles everything for us.

Before Auvik, we used multiple applications for managing things. Every week, we save hours. Previously, we spent a lot of time watching dashboards to see what went wrong. When a bug would occur, we would need to dump all the logs and look at everything. Now, we can usually diagnose everything within 30 minutes to an hour. It is saving three to four software-engineer-hours per week. That is a lot.

Auvik saves time and effort for our IT team. We can automate more things with the help of Auvik. It makes our team more available, always. It not only helps with availability of the software engineers on the IT team but with the availability of all our IT people. It has eliminated a lot of low-level tasks. And sometimes, it could be reducing work for senior engineers. Some of our issues can be hard to resolve, especially when dealing with the in-lab hardware. It can be hairy. Those weekly hours can be better used for the introduction of new devices or maintaining the high availability of our devices better. We can focus on expanding our labs a lot. It makes us more scalable, overall.

One of the most valuable features is the remote monitoring. It monitors the egress and ingress bandwidth and you can add custom rules to monitor if something is wrong. You can also add your own metrics if needed.

Auvik provides us with a unified management console. It is a website that displays all your routers, network switches, and devices connected to that router. You can easily see everything in that single dashboard.

You can use rule-based or simple, program-based monitoring to see if there is any abnormal traffic. 

It has good support for our devices, including our routers and Ethernet switches that come from the major brands. We are using Ubiquiti EdgeRouters, and Auvik has very good support for them. And it has pretty good support for other major brands like Netgear and TP-Link, as well. One of the reasons we choose Auvik is because the devices we currently use overlap with its list of supported devices.

Overall, the monitoring and management functions of Auvik are easy to use, but at times they seem oversimplified. Sometimes, we need more complicated scripting. Only using the basic logical rules like AND or OR or NOT is not enough. It can make the rules too complicated.

Also, when you load the Auvik website, it shows the topology. From my experience, it is mostly accurate. When we configured our network, there were some mismatches between the automatically-detected network topology and the actual topology. Some of the devices were not detected or were not supported by Auvik. We were able to manually modify things and everything has worked well since then.

Another issue is that to use Auvik you have to have a dedicated machine, either a virtual or Windows machine. Auvik continuously listens to the devices to look for all the devices on the network. This is a problem because it is a single point of failure. If that machine fails, all the functionality of Auvik stops. We can have redundant nodes, but it is still a problem.

Another problem is that it only works on Intel processors. Some of our machines do not use Intel processors. This was a problem initially because we had to get a new machine that runs the Auvik service. I would like to see it support more platforms and operating systems.

We started the 14-day trial plan this summer, and then we decided to purchase a license. So we have been fully using it for four or five months.

So far, the uptime has been really ideal.

Performance-wise, it's also good. For our use cases the monitoring machine is just a server, but it is not that powerful. It uses a lot of networking I/O, but it hasn't caused any network congestion.

It is scalable.

We have not been in touch with their technical support that often, but on occasion. Most of the team is in Toronto or the Eastern Time Zone and we are located in the Pacific Time Zone. But they are pretty responsive and their technical support team is pretty professional and reliable.

Positive

We didn't use any solution other than our own scripts to maintain the network.

As the head of IT, I led the work of deploying Auvik. It is straightforward because you use a new machine to run Auvik. It still needs to be part of the same VLAN as the other devices, but we didn't see any real glitches.

Our deployment is just a single location and we only use it for our lab devices. The lab has multiple layers of switches, Layer 3 switches, and routers, and all the test devices are managed over SNMP and Intel vPro.

After the collector was implemented, the network mapping went pretty fast. After it started running, it populated almost immediately, within minutes. But to get it fully propagated and have every device fully scanned took a while. That was expected.

We did our test of Auvik in a physically isolated, small testing network during the trial period. When we actually deployed it in our prod environment, it went pretty smoothly. We followed the playbook and it worked well.

The time that Auvik takes to search all the devices and get everything propagated is average or slightly above average. If there is a device update, for example, and a router reboots, it could take a while for it to be rediscovered by Auvik. I think that is because the frequency with which Auvik checks devices is pretty limited. If it worked otherwise, it would make the whole network congested. So the speed of checking devices is throttled and that means it could take minutes to get the latest state of devices. But once everything is online, you get real-time information.

We haven't had to do any maintenance on Auvik itself.

We did it ourselves and we didn't run into any issues. We had two software engineers involved.

We have only used it for a few months, but in the future we are going to expand our testing-devices fleet. We are going to double our number of testing devices. For most of the tests, the waiting time will be cut in half. Developers will spend less time waiting for tests to finish running everything and spend more time on actual development.

It is on a monthly subscription plan and it's charged by the device. We decided to use it for a year, first, to see how good it is.

PRTG Network Monitor and LogicMonitor were quite a bit more expensive compared to our current solution. Some of the other solutions we looked at are one-time purchases, but they are longer-term investments. For our projects, Auvik is more elastic. Per router, per month, it is a fixed price. We negotiated and got a more competitive price.

We did shop around for other network monitors to see what the best option was before we decided to buy Auvik. We tried PRTG Network Monitor and we tried LogicMonitor, but both are pretty focused on automatic network monitoring using protocols that are common to all devices, like SNMP. 

Auvik attracted us because of two things. One was that it is easy to configure. You don't need to set up your own web server or something like that. There is a trade-off there. If you do everything yourself, you own all the data within your network. However, that scenario is more vulnerable to external threats. But if you give all the network topology to websites like Auvik, there could be some privacy or security concerns. We did an evaluation and it seemed that Auvik would be a reliable partner for us.

The second thing that attracted us was Auvik's pricing, which is pretty competitive.

In terms of deployment, Auvik is a mixed model. You don't need to buy a dedicated machine from Auvik, but you need something that can run the Auvik monitor, whether it is a Docker instance or just a physical machine. We chose to use a physical machine mostly for security. That gives us better physical isolation from the rest of our network and makes it easier to manage and monitor if an attack were to occur.

As a very small company with a limited IT team, we found that Auvik is really helpful when you don't have a large IT team to do a lot of things. A lot of tasks can be done by Auvik and it will really help automate things.

The overall intuitiveness of the network visualization provided by Auvik is an eight or nine out of 10. There are some glitches, but it is easy to handle.

On the whole, it is a good solution. There are some issues, but I'm really satisfied.

We use it for network monitoring and for configuration backups.

Auvik makes it much easier for techs to diagnose issues. And the automatic configuration backups are a game-changer. In addition, the ability it gives us to see more accurately what's going on inside our networks is very important to us.

It has also reduced our MTTR by about half.

The monitoring and management functions of Auvik are as easy as they can be for the functions they do. It's definitely the easiest product I've ever used. That ease of use is a nine or a 10 out of 10 when it comes to importance. If I have to hire somebody specifically to do those functions, it's very expensive to keep that person. If someone who has general skills can use it, it's much more affordable from a business standpoint.

It gives us a single integrated platform for networks and that ranks as a seven or eight out of 10 in importance.

And it's a tool we use every day for visibility into remote and distributed networks. That too is very important.

We also use it to keep device inventories up to date.

The network mapping is just okay when I consider what I would typically see in a network map. It doesn't fulfill what I would expect, but it does some other things: dynamic port information and VLAN. But that whole overview map in a single pane of glass can be pretty messy and a little bit of a performance hog on computers. The network mapping needs improvement in Auvik, as a whole.

I've been using Auvik for about three years.

It's very stable. I can't remember a single time when we've had an Auvik outage.

Other than the network map becoming a little bit of a performance hog as you get into bigger networks, it seems very scalable.

As an MSP, we provide IT for about 50 organizations, from healthcare to manufacturing to education. That means we have Auvik deployed with collectors at single sites and at multiple sites with multiple collectors. It covers a broad spectrum for us.

We weren't really doing Auvik-type functions on any kind of scale. We've used SolarWinds or PRTG, but we weren't really using anything, before Auvik, for all of our clients.

The initial setup was very straightforward. Once the Auvik code was implemented it took a couple of minutes for the network mapping to start to populate. It was very fast. We have about 50 clients, and the overall deployment took about 20 hours, when all was said and done.

There is no comparison between Auvik and previous solutions I've used when it comes to setup and maintenance. With other solutions, I would literally have to touch every single networking device to monitor them. With those solutions, it probably took at least five times as long to set up. For deployment, we quote three hours, and for ongoing maintenance, we don't even think about it. It just works.

We did a pre-sales call with Auvik for the basic training, but outside of that, we did not use other help.

Our time-to-value with Auvik was right away.

I would love to be able to get into the tier with the sys logging and the NetFlow/sFlow. That tier is a little bit expensive for us. If that could come down a little bit in price, we would be using that everywhere.

We looked at SolarWinds, but Auvik was really the only fit for our business model, since we are an MSP. I couldn't find anything else that met the needs of a multi-tenant environment the way Auvik does.

If a comparison is being done among network monitoring solutions and there are concerns about pricing, I would tell them to look at the amount of time it takes to set up and maintain other solutions, as opposed to Auvik. Also, having to look at a MIB or do an SNMP walk for our devices, functions that would require a high-level tech, are things you don't even have to think about in Auvik. You put in the device, you tell it what you want to monitor on, and it does it for you. It honestly saves money.

As a cloud-based solution, Auvik is reliable and easy to use. I wouldn't even consider an on-prem solution at this point.

I would recommend it to anyone who would ask me about it.

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.

Auvik has made things more accessible, and we're much more agile in dealing with problems when they arise. It has also given us an extraordinary amount of visibility into the connections of the physical network. We've found many issues that we didn't know existed before.

We've probably saved around an hour each week using Auvik, but it varies. We're typically looking at the network stack to troubleshoot a problem, which doesn't happen that often. I usually log into Auvik when there are alerts unless something is misbehaving. However, I log on to Auvik at least once or twice a week to look at some of the net flow things or get a feel for what's going on in the network in general.

Auvik helps us keep our device inventories up to date, which has saved us time. We're a company in the financial sector, so we regularly go through compliance audits. Having a centralized location for configuration management is helpful because we don't need to spend time doing that manually throughout the year. The cloud solution enables us to have our configurations offsite in case of a disaster. That is a benefit. 

Network mapping is the most valuable feature. It's handy to see which devices are connected to what ports. The net flow stuff and traffic insights are also helpful. The network mapping is a little better than average. That's one area where PRTG falls short. It's tough to use. Auvik makes that a bit easier. 

Auvik's initial setup and discovery were effortless. Tuning the alerts takes a little bit more work. Ease of use is essential. Usually, there has been some alert, or we need a specific piece of information promptly. It must be easy for us to find that information.

The integrated platform is a nice-to-have, but it's not essential because we only have three sites: primary, guest, and DR. I only use Auvik for the primary site. For an MSP, the integrated single pane of glass would be a huge deal. 

I would relegate the network map to its area instead of being the focus of every page. The network map is in the front and center of the UI. I would rather have the option to look at it when I need it instead of having it on every single page. It's beautiful, but I don't need it on every page.

We've been using Auvik for about four months now.

I have found Auvik extremely stable. They do a lot of scheduled maintenance, but it's almost always on the weekends, so it doesn't impact us. 

Auvik looks incredibly scalable. We scaled it out to three sites without any problem.

I rate Auvik support seven out of 10. I want to give them an eight, but eight seems too generous. 7.5 is kind of where I want to be.

Neutral

We previously used PRTG and SolarWinds Network Configuration Monitor. SolarWinds got hacked, and their software was janky at best. It worked, but only because we didn't put a lot of load on it. We finally decided to find a solution that worked. We got along without it for about a year before realizing we needed a solution.

PRTG is an excellent server monitoring solution but a poor network monitoring solution. It does the job, but it's not good at it. Auvik is a fantastic network monitoring tool that does everything PRTG does, plus all the things that SolarWinds and CM did. It took the place of two different products. PRTG is usable, but it would take me 10 minutes to do something Auvik can do in a minute. Auvik is light years better in terms of usability and simplicity.

Setting up Auvik was surprisingly easy to do. The initial installation took a day or two, but it took a couple of weeks to start seeing the results I wanted.  The network map started to populate within 24 hours. It was so much easier than PRTG was and a lot faster.

I deployed it by myself. The involved tasks included setting up virtual machine collectors, modifying the firewall and ACL rules, setting up accounts, doing SSO, going through the training, and training my team.

I did the setup myself with a little bit of help from Auvik support.

It took a little time to get it up and running, but now that it's running, it hums along and does its job. I don't have hard data about our ROI, but we've seen value from Auvik. For example, say we had a bandwidth problem where traffic was slowing down on one of our guest sites. It would take me 15 to 20 minutes in PRTG to look at the net flows and figure out who was doing what. It takes me a minute or two in Auvik. That is a huge time saver.

I was under the impression that it was costly in a larger environment, but I was very wrong. It's pretty reasonable. The pricing is much better than I thought it was because it's based on network devices, not devices. That was a key thing that I did not know.

I like that it's flexible. If we have a device that we need to spin up for a month, we pay a little extra that month, and it goes back down. We don't have to renegotiate the contract or pay that amount forever.

We also considered Zabbix, but that seemed like a ton of work.

I rate Auvik nine out of 10. I've heard of Auvik for 10 years, but I always shied away from it because of the size and complexity of the networks I work with. I figured it would not be cost-effective because Auvik is a big name. However, it wasn't as bad as I thought it would be when I looked at the quotes. The value for the money is high, so if you think you can't afford it, look into it anyway because you might be surprised.

We use Auvik Network Management to detect devices on our network.

We implemented Auvik Network Management to gain the exact visibility I needed. This allows us to see devices on the network that might not be company-issued laptops, or even managed devices at all, such as unauthorized routers or access points plugged in by employees.

The UI is easy to use. There are a lot of different menus but they are not difficult to navigate.

While Auvik's network map excels at linking most devices, some manual adjustments may be necessary depending on the situation. This could include scenarios where the map struggles to identify which devices are connected to specific switch ports.

Auvik's network map provides as close to real-time visibility as we can get.

We saw the benefits of Auvik immediately after everything was set up.

The most valuable feature is device discovery through SNMP. This allows the tool to automatically gather detailed information about connected devices. For instance, it can identify a printer and determine if it's low on ink, out of paper, or experiencing a jam.

Auvik's network map, while helpful, could benefit from improved clarity. Currently, the amount of information displayed can become overwhelming. Zooming out provides a wide view of all devices, but compromises detail. Conversely, zooming in allows for closer inspection of specific devices, but sacrifices the overall network layout. This clutter makes it difficult to find a balance between seeing everything and seeing things clearly.

I have been using Auvik Network Management for three months.

Auvik Network Management is stable. We have not had any lagging or downtime issues.

Auvik Network Management is highly scalable.

The initial deployment was straightforward. I completed the deployment myself by following the easy-to-follow setup guide. The deployment took one hour to complete.

Auvik tends to be on the pricier side. Unlike some competitors who charge per site, they bill based on the number of devices they discover on our network. This per-device pricing can lead to costs quickly adding up for larger networks.

We evaluated one other solution, but Auvik had more features and was easier to use. The platform layout, overall functionality, and detail stood out with Auvik.

I would rate Auvik Network Management seven out of ten.

No maintenance is required from our end.

I would recommend Auvik Network Management to others.

For a smoother and faster setup, Auvik users should have a good understanding of their network devices beforehand. This includes identifying firewalls, switches, and access points. Preconfiguring SNMP on these devices would be particularly beneficial.

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.

The product significantly helps us; the real-time updates and alerts, and the rapid response time those facilitate, are beneficial. It gives us a lot of confidence knowing that if something goes down and needs to be fixed, Auvik will notify us immediately, and we can start working on a solution right away.

The solution's automation had a significant effect on our IT team's availability, especially when it comes to issues that may arise on the network. Automation provides us with real-time information, which allows us to resolve quickly.  

We've seen a massive reduction in our meantime to resolution (MTTR) with Auvik; having real-time problem alerts is a game-changer for us. 

The alerting is fantastic; if something goes offline, we're notified right away. It gives us a lot of peace of mind knowing the solution will alert us to issues automatically 24/7.

Once the solution is set up, the monitoring and management functions are straightforward to use. This is important because we want our systems to be as easy to use as possible for our daily operations. 

Overall, Auvik's network visualization provides us with a lot of information. The interface, icons, and mapping showing the icons and labels for particular devices are intuitive; the solution does a good job of providing us with the information we need in this respect.  

The product helped reduce repetitive, low-priority tasks through automation, which is a game-changer for us. Automation benefits our team and department, as well as other departments and business units because we can integrate their systems into our Auvik system. 

Auvik provides good visibility into our remote and distributed networks, although most of our infrastructure is local. We have data centers in different locations, and all our network devices are visible on the Auvik interface, including VMs, servers, and workstations. Everything can be integrated into our system.  

Comparing Auvik's cloud-based solution versus on-prem network monitoring solutions, being in the cloud is another game-changer. There can be some advantages with on-prem, but we prefer cloud-based, so it's great that we have that option. The cloud is the future, and everyone is moving in that direction, so that's a big plus for Auvik.  

The ability to subcategorize our inventories, between physical and VM servers, for example, would be a welcome addition. 

We've been using the solution for six to seven years. 

Auvik is very stable; we've experienced 99.99% uptime. It always provides us with the accurate information we need.

The stability could be better. Auvik can cater for many units and devices, but adding subcategories would make scaling easier.

The product has been steady since implementation, so we never needed to contact technical support.

I arrived after the solution was implemented, and before the implementation, I assume everything was done manually.

I wasn't at the company when Auvik was implemented, but as with all systems, the implementation can be tricky.

Auvik sometimes announces maintenance on their end, which is all done in the cloud, so the solution doesn't require any maintenance on our end. 

The pricing is fair; it's just the right price for what the solution provides.

To someone comparing network monitoring solutions but concerned about pricing, with the features and automation Auvik provides, it's on top of the game. There are some cheaper options, but Auvik is one of the top tools, and I recommend it to anyone with the budget.  

I rate the solution an eight out of ten. Auvik could be better, but overall, I highly recommend the tool.

We don't currently use the solution for managing device inventories. 

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

Auvik helps us troubleshoot, providing another way to look at a problem. Clients call in to tell us when something is working, and the cause of the issue is often unknown, so you need to attack it from different angles. Auvik offers another means to go in and look at the problem. If I know it's a network issue, Auvik will typically be the first tool I use to troubleshoot. It also provides excellent alerts. Auvik has reduced our resolution time by 25-30%

It has helped us with some low-level tasks. For example, if it's configured correctly, Auvik can monitor the age of VMware snapshots. Old snapshots can use up space on your server disk. Automating that task has been helpful. You can also automatically back up device configs. That's a level of automation that is hard to get in any other products, and I don't see ConnectWise Automation doing that. It can use WMI, too. 

In the past, we probably weren't backing up the configs as often as we should have. Typically, we would only back up the configuration when we upgraded the firmware. If you have the config, you don't need to rebuild it from scratch, so that saves hours of work. Previously, we had to check the VMware snapshots manually. We also tried an automated script that would send out an email. It didn't work well. Auvik was a significant improvement. Automation equals a roughly 50% improvement in our efficiency. 

The more complex the network, the more critical visibility becomes. Auvik helps a lot. We also use it for some smaller clients, but it's not all that beneficial for them. It's more crucial when you have multiple switches and a larger client.

In terms of delegating tasks to lower-level staff, Auvik seems like a tool that requires a certain level of networking knowledge. I don't think they need to be a Cisco-certified networking expert, but you need to know the basics like Ping, Traceroute, etc. It's okay for a level one engineer, but I think some were intimidated when they first saw it. Someone with extensive experience could get more out of it. However, they'll get more proficient once they start to use it.

Auvik does automatic device discovery, which is essential because you can pick up devices that are out there but unknown. I check it against ConnectWise Automate, which can automatically install things, but it's a more complicated operation. It's a little heavier. It's fitting for the devices to see if something responds, so it can inventory the device. If the SNMP networking is set up correctly, it will automatically add and monitor the device. 

It saves time because you don't need to add all the devices manually. That's the number one benefit. With Automate, you can automatically install the agent in a domain controller environment. However, some customers don't even have domain controllers, so you have to install the agent. We save 15-20 minutes per agent. It doesn't do as much as the other agent because it doesn't allow remote control, but it does allow us to inventory the device.

The stand-out feature is the automated config backup on networking devices. This automation is handy in a bind when a machine crashes, and you need to pull the config out of Auvik. 

The monitoring and management features are somewhat challenging to use initially, but you can figure it out after digging. It isn't hard for those with a high level of networking and computer knowledge. However, it's going to be difficult for some people.

Auvik provides a single pane of glass for all our customers in one portal. It's essential because many platforms are out there, and we can't have one for each client. 

After Auvik inventories a Windows device, installing a lightweight that would allow a remote connection would be excellent. A technician could use that agent to gain remote control over the client's computer, allowing us to troubleshoot remotely. 

If Auvik started doing that, it would be more competitive with ConnectWise Automate, making it more popular. They could probably charge more, too. More organizations would consider abandoning ConnectWise Automate altogether and only use Auvik.

The network visualization is a little plain. Still, I think it's okay for what it does. It's hard to script that to make it work properly, but I think it's getting better all the time. It has improved over time, and I think it's relatively significant, but not the end all be all. It is an excellent place to start because you can see where the connections are on the network, so you sometimes need to look at that. 

I have been using Auvik for four or five years.

I haven't heard of any significant issues or vulnerabilities. I know that Kaseya has had an enormous vulnerability, and SolarWinds had a huge one that affected governments. I haven't heard about anything like that with Auvik. So, I think it's pretty good overall.

Auvik scales well. You can always add more collectors. One of our clients had collectors at different sites, so it seemed to be quite scalable.

I rate Auvik support eight out of 10. I contacted them with a question a while back. It took them a couple of days to respond. The question related to a collector no longer supported on the OS. I had to install a new one. 

Positive

We used ConnectWise Automate, a competitor that offers some degree of automation for networking, but it's not like Auvik. ConnectWise is good at remote management. If the PC has an agent, you can connect to it quickly and monitor the particulars of the Windows PC.

Automate has some ability to monitor SNMP network devices and the like, but it never worked well. They have a probe that you have to install in a regular Windows system, but it's meant to be installed on a domain controller. You put it on a Windows box, and it runs these periodic polls to identify some of the networking devices. But it had some significant limitations. For example, sometimes, it was unable to go onto another network. If you had another subnet, it often wouldn't work for that, and they never improved that. 

I've done some deployments at the client level, where I've hooked them up in the collector. I've done some of that but haven't done the complete setup. I've configured nodes and endpoints. However, I haven't done the initial design for the whole tenant. I've only been involved with client setups.

It's relatively straightforward if you read the documentation, which is pretty good. The Auvik collector can get outdated and require an update. It was all relatively easy. If you get stuck, you can typically Google the answer and find it in a knowledge base. Auvik also provides internal training. 

After the collector is installed, populating the network map usually takes a couple of hours. It's ready to go in about two to four hours after. It also depends on the complexity of the environment and what you need to set up in terms of credentials and everything you need to pull the devices. 

Auvik does require some maintenance. Much of that is automated. However, if you're deploying it on an ESXi host, those collectors will shut down when the host is rebooted for Windows or VMware updates. Overall, it's a pretty low-maintenance product. 

Auvik gives us the ability to assess problems quickly and address them. We can also restore services faster with the backup configs and alerts as long as you have a mechanism to address alerts and someone watching them as they come in. If you have a system in place to monitor and respond to alerts, you can get a good return from Auvik.

I don't know Auvik's exact pricing, but I hear it was competitive. We provided Auvik-based monitoring for nearly free to a few of our clients to get them to sign up. A lot of these MSPs are monthly contracts, and they make the numbers work behind the scenes. I'm not in sales, so I don't know exactly how that works, but I think the contract is enough per month that we bundle it in.

The sales team tells the client that we'll give them Auvik so we can monitor our network and make our support a little more stable. It's a fantastic way for a company to get the necessary visibility and not worry about something going down. The story you're getting from the client is often inaccurate because they don't fully understand what's happening. 

For example, we had an issue the other day with a client who didn't have Auvik. They had some weird networking stuff and weren't onboarded properly. Auvik could help you onboard in an area where it would be beneficial when you're bringing on a client to figure out what they have because it's going to go in there. It will do a lot better with inventory and the devices there. It might find some that are unknown, but if you see something strange, you should figure out what it is and what it's doing on your network before ignoring it. So, that's a good example.

There are a lot of solutions out there, but I don't think there's another solution as good as Auvik. I've used Kaseya and ConnectWise, and I've had some exposure to N-able, so I'm pretty familiar with a lot of these similar products. I'm more familiar with the older version of Kaseya. PRTG is another one. I found PRTG difficult to use, but it worked pretty well once installed. 

I rate Auvik 8.5 out of 10. It's a good product. The more effort you put into Auvik, the more you'll get out of it, so do the work up front, and it'll pay off down the road. You'll see a switch that goes down, and then you'll know there's something wrong with the switch. You can either get someone onsite or try troubleshooting that switch remotely as best as you can. 

Whether it's a power cycle or whatever, you need to work with what you have. Auvik provides some powerful tools, but you need to do the work initially to ensure it's configured correctly and you're using all the product's functionality.