Auvik Network Management (ANM) Reviews

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 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 primarily for monitoring network devices to see which ones have gone down. Another use case is tracking bandwidth utilization on the interfaces.

Auvik has improved visibility across our entire network. We don't want to wait until a user calls to tell us a switch is down. Auvik enables us to be proactive, not reactive. We realized the benefits almost instantaneously. 

The solution speeds up our resolution time. When we're troubleshooting, it's easier to see if a device is down or the utilization is too high. That is helpful. It makes the whole process faster. If I didn't have this solution, I would only see whether the network was up or down. 

I couldn't, for example, see that the bandwidth utilization is 100 percent. Auvik sends notifications when the bandwidth utilization passes 80-85 percent. We get an alert telling us that it's something we should look into. Otherwise, I would need to rely on customers and application owners complaining that sessions are dropping. 

I appreciate Auvik's traffic insights. The network map provides solid visibility in real time.

Some things about the interface were a little hard to set up, and it was difficult to figure out where to find information. The Auvik team did a great job helping us get started. If I had to figure it out by myself, I would have probably gotten frustrated. You need to go on the device first to enable it. If you don't, then traffic insights won't start working. It's pretty intuitive for most stuff, but some things are tricky if you don't have someone tell you how it works. 

I have used Auvik for roughly a year.

I rate Auvik eight out of 10 overall. 

Auvik is easy to scale. It covers thousands of servers. 

I rate Auvik support nine out of 10. I can't complain. They solved my problem quickly. 

Positive

Setting up Auvik was pretty easy. It was a little tricky to get some of the things set up correctly and working, but it was fairly straightforward overall. Deployment took about a month or two because we have more than a thousand locations.

We did it in-house with Auvik's help. They assigned a team to us, and they did a great job. When we had questions or issues and needed help, they assisted us almost immediately. Four departments were involved. After deployment, Auvik doesn't require much maintenance on our end unless there are significant changes to our environment. 

My boss makes the purchasing decisions, but we're happy with Auvik's overall pricing. We had some issues with the licensing. You need to pay for premium to use NetFlow, and we had a problem with them counting the same device multiple times for licensing purposes. It was a little frustrating because the Auvik database in the background didn't see it as a single device even though it came from the same critical hardware and only had one serial number. However, it was in different groups, so it was counted two or three times. It took a while to work with the accounting team to get that sorted.

We looked at a few different solutions. We went with Auvik because it was the best fit for our requirements, security standards, and budget. The security department didn't approve some of the alternatives.

I rate Auvik eight out of 10 overall. We had a few hiccups here and there that we couldn't fix easily without help. With Auvik's assistance, we got everything fixed. 

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

Auvik provides an intuitive interface that supports ease of use. We got all of our locations clearly defined. Everything is laid out well and labeled well. Several people know how to use it. It is something that I picked up on pretty quickly.

Auvik's network map along with its dashboard gives a real-time picture of our network. By using the filters, we can filter down to see what we want to see. We can see just the Layer 1 devices. It is very handy. With a couple of clicks, we are done. If we want to monitor WAN interfaces, we add them to the dashboard. If we want to monitor VPN interfaces, we can add them to the dashboard. It is fantastic.

Auvik's network map dashboard gives full network visibility. Whatever you give the collector access to, it takes that apart and dissects every bit of that.

Auvik has empowered our entry-level technicians to solve more tickets on their own. I do not want to give them access to it because it makes things too easy for them and they do not get challenged, but it has definitely helped in closing more tickets faster.

Auvik has absolutely decreased our mean time to resolution. Instead of days of hopping around on switches and hoping that the logs still include some information about something that is pertinent, it now takes minutes.

We can monitor our VMware environment with Auvik at no charge. This is absolutely important for us. It makes the product more important for people outside of my department. I am just worried about the infrastructure. Whatever happens on a server, I do not care, but it makes the product valuable to people outside of my department and the infrastructure team, and they get to reap the reward of having this product in our environment.

Auvik allows us to spend less time on the setup and maintenance of the solution and less time on issue resolution. It very much takes you away from a break/fix to make you more proactive. You do not do as much of a break/fix because you are seeing the warnings and the alerts. You are able to see that you have got a physical issue out there that you need to correct, or you find that you do not have redundancy, whereas you thought you had redundancy. This free time is still focused on security.

The biggest draw for me is the flexibility of being alerted. If something happens with my critical infrastructure, I get real-time alerts on it in Teams. 

For pulling up the devices, the dashboard is a little bit sluggish. I know there is a lot of data, and I am starting to get nitpicky here, but this is the only thing. The dashboard is a little sluggish, and you have to keep the filter on sometimes.

In terms of the things or features that I wish it had or has is the Wi-Fi visibility. They are pulling that into it from their newly acquired product. I am excited about that, and that is the only thing that is missing from the suite. That is a big piece to me. I would like to see that sooner rather than later.

I have been using Auvik for two years.

Any stability-related issues are very infrequent. They have a pretty rigorous maintenance schedule, and they notify you when maintenance is happening. The maintenance windows are pretty short and infrequent as well.

It is enormously scalable.

I never had to contact their support.

We had N-central. I tried to use it, and it was not great. There have been half a dozen that I have tried. They are all okay, but after using Auvik, everything else seems not so good.

We could see Auvik's benefits during the trial. The product that I was using at the time was pretty outdated. I had updated it recently, and I was pretty unhappy with the performance and the feature set that it had even after I updated it. I had inherited the product, but I started looking around immediately. We popped in an OVA for the collector into our VMware environment and had it going. In less than 10 minutes, we were already scanning our network and had more information built out than the product that we had been using for years. 

It is on-premises. I was not involved in its deployment. I handed it off to one of the guys on the infrastructure team. He had the setup instructions, and he added it up in ten minutes. It was pretty straightforward.

In terms of maintenance, it does require maintenance for major release versions. About once a year, we have to deploy a new OVA, but for the most part, it stays up-to-date on its own.

It was all done in-house, and there was just one person. It did not take any time.

It is a little more on the expensive side, but I feel that it is a premium product. It is good.

To those evaluating Auvik, I would advise making sure that they have all the credentials they need before they start the trial for your equipment. Make sure you have SNMP set up, and you are good to go.

I would rate Auvik a nine out of ten.

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.

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

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

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

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

Auvik helps us be proactive versus reactive. We stay ahead of the curve by getting alerts and knowing that a problem could potentially occur. The ability to resolve potential issues before they become a problem is a massive benefit for us.

The visualization is excellent, and our customers will speak to that too. We often export the map it creates and hands it off to customers, so we don't spend lots of time manually creating these things in Visio or Lucidchart. We don't have to use any of those kinds of tools anymore.

I might have had trouble with the visualization if I hadn't had all those sessions with them to walk us through all the technical points of it. There's a lot of information, so it's like trying to drink from a fire hose. They handed all that information about filtering and using the solution in those technical calls. I think they know that you'll get hooked and become a long-term customer once you get familiar with it and understand how intuitive it is.

The visibility into remote networks has been immense. It's quite a big project to swap out some network switches for a new customer. We weren't familiar with the current network. We deployed Auvik on the web and scanned the switch ports to understand what was on the other end of each switch. It helped us replace those switches and plug everything into their new destinations on the correct VLANs. It's a huge deal for us.

We have it set up so that various alerts go to different teams. If an alert comes in for hard drive corruption on a desktop, that will automatically go to the manager of the help desk team instead of the server infrastructure team. That works pretty well. 

Auvik keeps our device inventories updated, saving us time because we know what is deployed and what has been decommissioned. It's also helpful from a billing perspective. It was a manual process of exporting reports from our RMM solution to do billing per device. We can do it all through Auvik because we can see what is active and what isn't.

We're a pretty small shop, so Auvik has helped us a ton. I would spend two to three hours a day manually doing this if we had to put it down to an actual number. With Auvik, it takes no more than 30 minutes of just browsing through alerts in one spot, creating tickets, assigning them to our resources, and taking care of things that need to be done.

Auvik is easy to use. It took some time to set it up, and they were pretty good to us. They offered us around six sessions with a technician to help us set up the monitors we wanted. After we were trained properly, I had no issues using it.

It has been crucial for us to have all these monitoring capabilities in one place. That's why we've been willing to shell out the monthly expense. It's helped us tremendously.

Configuring alerts is pretty tedious. It would be nice if they had a wizard who walked you through instead of having everything turned on or off from the start. 

For example, it could have some radio buttons and ask you, "When this kind of alert happens, where would you like the alert to go?" Is it push alerts to a cell phone or an email address? Is it simply alerting? I think an initial onboarding wizard would help you to build out Auvik and get more out of it from the front end.

We first used Auvik when it came out or when ConnectWise started pushing them. That was in 2019. We used it for about a year. I don't remember why we stopped using the product, but we picked it up again eight months ago and have been using it consistently since.

We've been with Auvik for eight months, and we've had a few alerts that Auvik collectors are not communicating with the solution. We had three of those in an eight-month period, and they were fixed within an hour. I'm pretty sure some of those came in overnight while they were doing maintenance. The uptime has been reasonable. 

It's pretty easy to scale up Auvik. We cater to movie theaters, so many of our sites are cookie-cutter from our end when we set them up. It would be nice to have the ability to copy a site and apply the template to another site. 

This may be a solution that they offer, but I don't know. We've never been able to do that before. In terms of deploying the collectors, the scalability is fine. After that, you need to go in and approve all the networks you want to scan. That takes at least an hour.

I rate Auvik support nine out of 10. I needed some help setting up an alert to monitor the VPN. I needed to get an alert if a specific VPN tunnel went down. I had no issues with that. They sent me a quick knowledge base article on how to configure the alert.

Positive

Previously, we used some open-source solutions called Observium and Libre. They're both SNMP and sys log monitoring tools hosted internally. We had to maintain the servers and do the updates. A lot of time went into that, and it would break frequently. When it broke down, we'd lose a lot of data and dedicate significant resources to maintaining the solution. That's the main reason we switched back to Auvik. Once we got into Auvik, we realized we got so much more data through it.

Auvik's cloud platform was a critical reason why we switched. When you're hosting an on-prem solution, you need the resources to maintain it. You have to apply patches to the software and maintain the infrastructure it's running on. In terms of capabilities, Auvik is like a hybrid solution. The platform is on the cloud, but you have an on-prem collector agent running these scans. There aren't any gaps in the data that it can obtain, and it's much easier not to have to maintain the infrastructure.

The deployment was straightforward. You create a site on the web portal, and it gives you an installer. You download the collector onto the device you want to monitor, and it starts collecting data. After deploying the collector, the network map takes 15 to 30 minutes.

We have Auvik deployed to around 25 sites, and our networks are heavily segmented. We have to create extensive rules on our end, which isn't necessarily an Auvik thing. We want one device to see everything on every network segment and VLAN. You have to have a rule specified for that. It took an hour at each location to get Auvik fully deployed. We started with those technical calls to understand the controls needed in the firewalls. Now we have a template that we use to deploy.

Configuring the alerts took four to six hours worth of technical calls. A lot of those were global. Those alerts could trickle down through each customer site as we had them set up. Our previous solution probably took the same amount of time to onboard a new site. At the end of the day, we have no internal resources dedicated to maintaining the infrastructure whatsoever. It runs and collects the data. We just log in and review it from there. It saves us at least two to three hours per week in the long run. It doesn't require any maintenance after deployment. 

In our experience, you get what you pay for. Everything is priced based on its actual value. I think Auvik is on the pricey side, but it has been worth it for us. It depends on how much you will use this and the level of visibility you need into the networks you're monitoring. Some managed services providers don't do much monitoring, while others monitor extensively, so it depends on how much it means to you. If you go with a low-end solution, you'll miss out on quite a few capabilities. On the higher end, you need to justify that cost.

I understand the pricing model with it, but I don't know the details about how much we pay monthly. I am not usually the one that handles it within our organization.

We did not look at any other solutions this time around. Initially, we were a ConnectWise customer, so we got a free trial to test it out. After we left, we decided to come back because it was a project where we needed visibility into a customer site. I knew Auvik provided that capability, and we did it. Once the owner of our company was able to get in and poke around through that, he was like, "Oh wow." So, he decided to sign back up for it.

I rate Auvik nine out of 10. To implement Auvik, you must understand what you're trying to monitor. If you don't know where you're trying to go, it's much harder to pave the road. You must understand how to allow that monitoring within your infrastructure before trying to get it. 

We ran into a problem when we were deploying the collector and were only getting limited amounts of data because particular ports are closed on the firewall. We weren't getting alerts within Auvik saying something wasn't happening because it was blocked. It just wasn't working, so we had to figure out the hard way to create rules in our firewalls to allow the collector to get its data.