Auvik Network Management (ANM) Reviews

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

One of the things we noticed is that our wifi access points were throwing a bunch of errors. So we're in the process to replace those access points.

It is also very good at notifying you if the network goes down, and then it'll tell you if it's cleared or if it's come back up. 

Auvik started providing value right away. The APs immediately started sending alerts. It's really important that the wireless network works properly over at that location. Looking at the alerts, it's got big problems, and it's just because of old devices.

The alerts that it sends out are the most valuable aspect of this solution. The maps are okay. The interface is okay, but the alerts are what I really like.

Auvik is easy to use. The first thing you see when you open it up is a map of the United States or wherever you are, and it shows the locations of all of your network endpoints. For discovery, you set credentials and manage the credentials and it tells you when it needs a new credential. So you just click the "Manage Credentials" button and it takes you to the right spot. You enter in a new credential and then it starts looking closer at the device. It can give you all kinds of information from inside the device's log. We use it for CIS logs and we use it for just regular logging. The CIS log was something I was looking for in the other products, just so we have a place for the CIS logs to congregate so we can look them up.

The menu on the left-hand side is very straightforward and clear. If you want to see it, just log on to a certain endpoint, bring up that endpoint, click CIS log on the left-hand side, and you'll see the CIS log.

It's easy to navigate. Everything is intuitive and easily accessible.

The network discovery capability is very good. Last week we refreshed one of our locations, and while an employee was out there refreshing the location or replacing devices, I could sit and watch Auvik find the new device and start mapping it. It automatically updates our network topology.

There's only one other team member and he doesn't use it. So it's just me that uses it. And I use it to make sure that there are no loops in the network or the network is not configured wrong. Every once in a while, the map will do something funny and we'll have to try to figure out what it did. You are better off if you physically document the ports that things are plugged into and then put those into Auvik, which is not hard. You just click on the connection line and go ahead and edit it.

We never would have known that the access points were a problem until Auvik came along. The location that has the bad access points was running slow and we could not figure out why without Auvik. The network was basically configured wrong. Something was plugged in and created the loop. Within hours, we could have somebody go onsite to fix it.

We use the TrafficInsights feature a little. It shows us network bandwidth usage without the need for expensive inline traffic decryption. The part that's important to me is the application breakdown. It breaks down the applications that are running and taking up bandwidth. It lists all the applications that are taking up bandwidth.

The map would be the first thing I would like to see improved because sometimes the maps get really odd-looking and the automated placement of things on the map, devices on the map is sometimes not right. In fact, I was just looking at the map and something got moved. I'm sure it didn't get moved, it's just that Auvik realized it was supposed to go somewhere else. So the map could be better if there was a little bit of manual manipulation that you could do.

Everything else is pretty simple and straightforward and easy to use.

I have been using Auvik for six months.

It's always been stable for me and available. They do have scheduled downtime, but that's usually in the middle of the night and it's usually pretty quick.

We have a small network. We do have two domains, which a lot of things don't work well with as far as network tools, but Auvik works great. It just picks out both networks and we go from there. 

We're monitoring 575 devices with Auvik. We've maxed out on our network. We might add other devices.

It requires zero maintenance from our side. 

I've used support once or twice and they were efficient, quick, and solved the problem. I don't remember what the problem was, but they were quick and efficient about it.

The initial setup was very easy. We use VMware, so we set up the connectors that we needed and Auvik just started working. It started going through the network and building maps at each location. It was very simple. The setup took a few hours to a day.

It's too soon to have seen ROI, but I'm sure we will.

The value is there. It's not that expensive per device and it's licensed per device. Unlike some of the other tools that I use, it's not really expensive. It's a good value for the price.

Out of those 575 devices, 49 of them are billable. The non-billable devices are workstations and printers.

Everything just worked. The important thing is to set up your devices properly so that there are passwords and ports that Auvik can use so that it can get in, get the configuration, and also flag any alerts.

I would rate Auvik an eight out of ten.

We're an MSP, and we handle and monitor the network for many different organizations. So, we use Auvik for any client that has on-prem resources such as firewalls, switches, and servers. It's basically for any client that has a physical office.

We used it mostly for alerting and to have visibility over resources on a network. It's centralized oversight over what's going on.

The network map is really good. It gives us a good idea of the topology for new sites as we deploy the software. The ability to remotely connect the network devices is great. If we don't have direct access we can pretty much just do it from anywhere that we have an internet connection to. That's really helpful.

My team does the knowledge training. They have a university, and when we have new staff, they take the Auvik certification course. Otherwise, there is a lot of stuff to do in the solution and a lot of things to see. Without training, people will have to guess their way around it. Maybe they will see some basic features, but to actually leverage it to the fullest, you do need to take the training.

The dashboard and the network map give a real-time picture. It is really good so long as you have the credentials for everything. I don't really have any complaints. I think it's really helpful. It has been a lot of use for us in the past. Regarding things such as suggestions, it tells you where you have devices you do not have credentials for. That's something you can see if you go to the discovery settings. 

The benefits were realized pretty immediately. The benefits are very self-evident. The only thing you have to do to see the proper benefits is make sure you have a good setup. It's important to know how to deploy things, which credentials to add, etc. Otherwise, the topology will not be of much use. You will not get the configurations. However, if you have the proper knowledge of how to set this up, it's great.

We do not give our entry-level technicians access to Auvik most of the time. It's usually for tier-two technicians or our network engineers. However, it does help them with the Epic training. Before we are going to give entry-level permissions, we have them take training, and the training gives them a lot of information on the network on how to use the platform. 

Auvik helps decrease our mean time to resolution. What's good about Auvik is you can define thresholds where you can close alerts. So, if something goes down, you can see the condition. That definitely helps us take time out of the resolution process and lowers our oral ticket numbers.

In terms of the dashboard, maybe seeing on the map, for example, if you have an access point that's connected to switch one, and the access point you do not have credentials for, that could help us make management a bit easier. However, it's not terrible. It's just something to make it easier.

It has a monitoring feature. Besides just monitoring the network, you can tell Auvik to monitor a host name, like a domain name or an IP address on the cloud, and it just pings the IP address and gives you information. I feel like that's something that could potentially be improved a bit. For the service monitoring feature, we can check for port status or cloud ping checks. We can check against domains and against IP addresses in the cloud. That's a feature that has been of a lot of use to us. However, it is a little bit lacking in some features compared to other solutions that we have also used in the past. We used to use another solution, and we wanted to transition this service over to Auvik since Auvik does largely the same thing. However, as we were migrating, we noticed specific features were missing, and we could not add some of the monitoring back into Auvik since there were some technical limitations. For example, if Auvik has an IP address for the domain you want to monitor, and if the domain does not respond, it will take it as the services down, and it's going to trigger the alert at that point. It does not check when giving out a ping request. It checks by just making an HTTP request to the website. However, basically, some websites that we manage do not respond back to ping requests based on safety settings and so on. So, we have to do HTTP checks to check if the service is up. However, Auvik does not support that at the time. 

I've used the solution for two years. 

Mostly, it works well. We do have some sites that seem to stress the platform a bit. We might have been over the edge when it happened, and that's the only time I have seen performance issues. 

It's really easy to scale. Previously, and I'm not sure if this is true any longer, you could not turn a single site over to a multi-site and vice versa. In that case, you may need to delete your current site, or sites, and migrate things over. 

Technical support is really good. They are really quick. I have no complaints. 

Positive

I've also used Datto. However, Datto provides actual infrastructure, whereas Auvik is just monitoring. They aren't quite the same. 

Setting up the solution is not difficult. We just have to make sure we have credentials for everything on the network. However, that's something that comes from our clients. As long as we have the credentials, it's pretty quick to set up. We had everything set up in about two weeks. 

However, if someone is not tech-savvy, they will see many unfamiliar terms. If someone has knowledge of API integrations, they'll have an easier time.

We tend to need two people for each deployment. Someone will take care of provisioning and collecting, and someone will do the technical setup within the platform.

There isn't really any maintenance needed. There may be alert tuning. Auvik does come with a lot of alerts that are already pre-built in. Some we disable, some we modify, and some we just create from scratch. 

I do not handle the licensing aspect of the solution. 

I'd rate the solution eight out of ten with my biggest complaint being the documentation and knowledge base, which is difficult to navigate.

We use it for monitoring clients' networks.

One way it has improved our organization is with respect to managing switches for clients. We didn't have a solution before that would back up our clients' switches. So if a switch failed, and we didn't have a safe manual backup somewhere, we were scrambling to figure out what was configured on that switch: Were there VLANs, was there some advanced configuration that we don't have now and that we have to rebuild? With Auvik, we just grab and restore the config file.

There are fewer steps for us to do as an organization. We set the tool up and it does all the work for us. It's taking a lot of that manual leg work out. It has recaptured some time that we can give back to other tasks. I wouldn't say it's a huge amount, but it's still a good chunk of time.

And it has been extremely useful when it comes to visibility into remote and distributed networks, especially managing devices. Being able to log in to a switch without having to log in to a client-server, since you can do that from Auvik, has been extremely helpful for our IT team.

And our MTTR has been reduced by at least 50 percent because, as a switch goes down, we get the alert without having our client call us. We have the alert and we know what's wrong, which is great.

I like the switch device configuration backups.

Also, the monitoring and management functions of Auvik are pretty straightforward. I haven't really found too many issues with them. The ease of use is pretty valuable for us.

It also integrates with our ticketing system. We use ConnectWise and having that integration is valuable for billing and for all-around general management. Having one product that can integrate with everything is valuable because we don't have to worry about building out APIs or custom maps to do that for us.

Overall, it's very intuitive and very easy to find help on how to configure things. Their knowledge base is very deep. There are no issues there.

There is room for improvement on the development side. As new devices and models come out from different manufacturers, they aren't always supported by Auvik right away. For example, Sophos switches came out within the past year and we only have CLI support right now for those, so obviously Sophos configs cannot be backed up at this time through Auvik. It's an issue of being more proactive before products are released. I would like to see the manufacturers working with Auvik in advance, before new products come out, to make sure they're supported.

I have been using Auvik for three or four years now.

The stability has been great. Obviously, there are planned outages but they warn you about them ahead of time. There has been no issue where we needed to get in there and it was down.

The scalability seems great. We're still a small business and if we had larger clients our experience might be different, but for what we have it has been great.

We have it deployed in multiple locations. Each client's site has a collector installed and they have one, or maybe two, offices.

Auvik's technical support is a seven out of 10.

Neutral

This is really the first product that we've had that does full network monitoring. We used ConnectWise for machine management, but its network capabilities were somewhat limited. That's one reason we chose Auvik. The dynamic map of the network it provides and the ease of troubleshooting were additional reasons. It helps in pinpointing where issues are. When a switch is down we get that alert from Auvik and it definitely saves a lot of time for our help desk.

The initial setup was pretty straightforward. It's definitely gotten better, but I didn't have any issues setting it up for our organization or for clients. The experience has been the same.

Out-of-the-box, it worked just as it should. After the collector is implemented, within the day the network mapping starts to populate. It's pretty much instantaneous.

Setting up other products was a lot more involved. Another product we used was SolarWinds, but it was something of a bear to set up. It's not really straightforward, out-of-the-box like Auvik. With Auvik we definitely saved on having to research licensing and then install software somewhere. We don't have to do any of that. It's all hosted.

For the most part, maintenance is handled by Auvik. Obviously, if new devices are added to the network, they have to be configured to talk to Auvik. But other than that, you just set it up and it's good to go, unless you change the credentials. Overall, we just set it up and sit back and watch it.

We did it in-house. It was just my boss and me involved.

The pricing seems fairly competitive with what may be out there. We haven't looked around too much, but the pricing is very reasonable.

We were set on Auvik right away.

Make sure that the networks you're going to be managing with Auvik all have managed switches and that those switches or devices are supported by Auvik.

Auvik does a fairly good job of mapping network topology. It's about 90 percent of what we need. There are some inconsistencies with port mapping. For example, it will discover that this switch is connected to this switch in this port, but sometimes it's inaccurate. There's some work to be done there, but overall, it's been extremely useful for us.

Auvik helps keep device inventories up to date, although that's not generally a time-consuming task with our clients. As an MSP, we handle small to medium-sized businesses. But if we were to grow, that feature would definitely help more.

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

Auvik has really improved our time of response when a client is down, or there is a problem with a firewall server. Before, we didn't know when a client was down, or it was really difficult to know. We pretty much had to wait for the client to tell us, "Hey, we are down, what's happening?" One or two hours could pass while we worked on finding out what was going on. But now, if anything happens, we get the alert and we get everything resolved. It has helped us to make efficient use of our time and to act more quickly.

It is also very useful because one of the low-level tasks is monitoring. Because everything is up to date, high-level managers and employees can focus on more important things.

There are a number of features I really like. One is the graphical map where you can literally see all the connections: where they come from with respect to the firewall, when they go to the switches, and how the network is set up.

That network visualization is really cool. I've been working here for a year now, and the first time I saw it I said, "Whoa, this is so cool." Sometimes, when you start working with a client, you don't have a visual representation of anything. Your boss tells you, "Okay, they have several switches and firewalls," and you have to draw that in your mind, and it can be inaccurate. With Auvik, the map is accurate. It is great and always updating. That's definitely one of the best features of Auvik.

Another feature that I really like is the fact that it's very easy to remote into the firewalls, switches, and ESXi, to manage the appliances. It's also really easy to use the monitoring and management functions. Everything is shown very well. You can immediately see the options for the appliance, including the documentation and the remote management. It's really easy to use.

That ease of use is extremely important to us. It is one of the cornerstones of our operations, in addition to our tickets which are on another platform. With Auvik, we monitor the heart of every client's operations. It's really important for us that the Auvik is working well and accurately, and that we don't get any false alerts, because that would make us waste money and time finding out what's happening. So far, it has been great and a very important part of our operations.

And I really like the alerts. They are very accurate and fast. The moment that anything is down, we can act right away.

I don't know if it has integrations with ticketing systems so that alerts would get to the ticketing system right away. That would be a good feature to add.

I've been using Auvik for about eight months. I use Auvik every day.

The stability is good.

The scalability is great too. It's really easy to add new infrastructure, new appliances, and they will show up because the collector is already installed.

I've only used their support once, and it was fine. It's okay but not perfect because I would prefer that they have longer operating hours. That's an area for them to improve on because sometimes, on the weekend, we have problems and technical difficulties and we cannot reach support. If we could have extended support on the weekends during normal hours, and even a bit more extended, that would be great.

Positive

The initial setup is pretty straightforward because the tutorial is very good. It gives you several options and it guides you. And their knowledge base, if you have any kind of problem, is pretty comprehensive. You can get it to work, even if, like me, you are not an experienced technician. I have implemented Auvik for five clients now, and it's all good.

Depending on the size of the client, it takes 10 minutes to 15 for the network to start populating. For a midsize client, it might take 30 minutes to have it completely set up, but even that is an extreme amount of time. Generally, it's even better, about 10 to 15 minutes.

The deployment can be done by one person, no problem. It could be a junior technician. They just need to install the collector, set up the correct services and ports, set up the credentials for the appliances, and that's about it, as an overview. The technician needs the appropriate permissions and credentials for the appliances.

Almost all of our clients have a firewall connected to a modem with one or two switches, most of the time Cisco, connected to those firewalls. Then everything else is connected to switches, including servers, printers, computers, and workstations. The switch will have VLANs so that we can segment the networks and do a proper installation, but that's pretty much it. And on the servers there will often be VMware ESXi that we monitor with Auvik.

There hasn't been any maintenance, as far as I know. We have never had to manually update the collector.

The time-to-value is right away. When you set up Auvik with your very first client you see its value with the graphical interface, the ease of remoting in, and the alerts.

Try all the features, investigate it and be curious about everything that Auvik can offer. I've been using it for several months, but I don't think I have used all the features. If you test it, my advice would be to try all the options.

We use the tool for network diagrams and troubleshooting, which has been helpful. One of the main issues we had before ANM was the lack of up-to-date network diagrams. With its dynamic function, we solved this problem. We also use it to troubleshoot network incidents such as APs going down and for automatic backups.

There are many things I like about the product. It's cloud-based and automatically refreshes the network container. We like the automatic backups and the comparison between backups. It's straightforward to set up, and it integrates with many protocols.

The tool provides an intuitive interface that's easy to use. The search box is particularly helpful—we can search for everything from MAC addresses to IP addresses to interface names, making it easy to find any device.

The network map and dashboard give us a real-time picture of our network. It's pretty easy to use these features to gain visibility, though we've had some minor issues with Meraki devices due to their lack of support for SSH and SNMP.

The solution has helped us automate our processes and integrates well with ConnectWise so that we can get alerts in our CRM and via email.

We noticed the full value of ANM after a few months, as we needed time to train and understand the system. It has helped our technicians due to its many capabilities and the data it collects. After about a month of training, we were able to share some of the senior team's workflows with junior team members.

ANM has helped us decrease our mean time to resolution by about 20 percent.

I'd like better integration with Meraki and a history feature for network diagrams. If a device fails on Saturday, we can't find it by Monday. A history or PDF export of diagrams would be great to see how devices should be connected.

I have been using the product for eight months. 

I rate the tool's stability as nine out of ten (it gets cloggy with large diagrams). 

We use the product on the cloud. Deployment was straightforward with the setup guide, initially taking about one month with a team of five people. Now, each new deployment takes about 15 minutes. We use it across many client enterprises and sites, with Windows, Mac, and Linux devices and multiple network brands. About ten people in our organization work with it. The cloud version needs no maintenance, but on-premises agents need checking.

The tool has saved us about 15 percent in return on investment.

The tool's pricing is reasonable. 

I recommend ANM for its updated network diagrams, ease of use and implementation, and high availability. Overall, I'd rate it nine out of ten.

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

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

I occasionally use the network map to identify new devices connected to the network. It provides a real-time visualization of our infrastructure. Additionally, the map initially displays a collapsed view, requiring expansion for detailed information.

Auvik significantly reduces our Mean Time to Resolution, especially when devices malfunction. Now, I receive immediate alerts, eliminating the need to wait for phone calls or emails from someone reporting a downed access point or camera. This was especially helpful in a case with our D-Link access points at one of our sites. When these devices fail, they don't completely shut down; they keep rebooting, broadcasting the Wi-Fi network, and then disconnecting users. Before Auvik, this repetitive cycle could go unnoticed for days, leading to frustrated users and disruptions.

We see the benefits of Auvik fairly quickly. 

The quick alerts in the event the equipment goes up or down is the most valuable feature.

When port utilization rises beyond a set threshold, an alert will be sent to allow for proactive network planning and distribution adjustments. This could also help identify heavy data users.

The user interface is not intuitive. For example, when a device fails and I need to replace it with a new one, I'm required to delete the old device from the system to prevent recurring alerts about its downtime. While I was able to find instructions on how to do this in the knowledge base, the process itself is illogical. It necessitates navigating to the "Discovery" menu, which seems counterintuitive for deleting an existing device. A more intuitive approach would be to enable deleting a device directly from the list of all devices, eliminating the need to access a separate menu labeled "Discovery" for an already discovered item.

Some device placements appear inconsistent with their logical locations, like network switches. For example, I might see devices related to the same switch cluster scattered across different areas of the map. This inconsistency in positioning for co-located devices confuses me.

Setting up a new site or viewing device configurations, particularly those involving SNMP and similar protocols, often requires significant technical knowledge. I believe simplifying this process would be a major benefit, but I'm unsure if Auvik can do so.

I have been using Auvik for almost one year.

Auvik is stable.

Auvik is scalable.

One of my sites experienced an issue where the internal internet connection port on the firewall had been changed. Consequently, our Auvik agent wasn't capturing any traffic data, affecting our utilization reports. I contacted tech support to troubleshoot, but the email-based communication proved ineffective. While I appreciate their attempt to help, I would have preferred a phone call or a remote session for a quicker resolution. The back-and-forth emails with unclear instructions simply became time-consuming, and eventually, I had to prioritize other tasks. This made me realize that offering a remote session option early on in the support process would be incredibly beneficial for customers like myself. I am unsure if it's a language barrier or the location of the support team, but encountering this email-centric approach with several companies has led me to believe it's a preferred communication style for some tech support teams. However, for me, it's not the most efficient method. While I give their technical knowledge a high score of nine or ten, I feel their support delivery falls short at around three or four. Instead of sending me emails with links to lengthy documents, a 10-15 minute support call could have resolved the issue quickly. Ultimately, spending hours reading manuals and troubleshooting without success feels like a waste of valuable time. Therefore, I recommend exploring the implementation of a remote session option for enhanced customer service and increased efficiency.

Neutral

The initial deployment was straightforward because it was done by the Auvik techs.

Two Auvik techs implemented the solution for three of our sites.

The price is reasonable.

I would rate Auvik an eight out of ten.

No maintenance is required.

The biggest requirement to use Auvik from a technical perspective is having SNMP knowledge. The rest is straightforward.

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

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

Auvik provides an overview of a company's infrastructure that helps you identify and solve problems from a single pane of glass. Without Auvik, you would need two or three times as much work to log into these devices individually and look at the back tables. It's great for identifying when things go offline if the spanning tree has identified an issue. You can pinpoint where in the series of commands something has broken. Overall, we've probably reduced the related network monitoring work by one-third. 

Auvik is automating aspects that we hadn't even considered because it was too much overhead. Rather than reducing the time spent on tasks, it has enabled us to perform new operations that we weren't doing in the past. It's added a benefit in that way.

The visibility into remote and distributed networks globally Auvik provides is essential. If something goes offline, you can go back through the alerts, even if you can't access that device to look through the logs. It has saved me hours of time troubleshooting. I can do something that would've taken me an hour in 15 minutes. From my own experience, I've been able to resolve problems much faster and made myself more available for something that could have taken a lot longer.

Auvik keeps device inventories updated, especially if a new network element is added that we are unaware of, like an end user plugging in a switch at their desk or endpoints in general. We don't use Auvik often for endpoint management or visibility, but it's great for network infrastructure visibility.

Auvik allows me to filter by network elements, so I can get a quick glance at a customer's infrastructure without looking through handmade diagrams. It provides me with an overview of how everything is laid out. From there, I can really drill down into individual inventories and switch ports. For example, I can determine what the issue is, but I don't need to be on the premises and log into customer equipment. It saves a lot of time. The network visualization is pretty and fun to look at. 

Monitoring and management in Auvik are relatively easy once you've had somebody show you how to do it or you've taken some classes. It's not entirely intuitive initially, but I find it relatively simple to use now. 

I would like to see some better training or public resources. It's not just Auvik's fault. Our company has a responsibility to explain the toolset and everything it can do. Many of our engineers don't realize how powerful it is. Due to a lack of documentation about Auvik's capabilities, so much can go over the heads of engineers who don't spend much time with it.

Most engineers are fine with taking some time to learn how to use it properly, but there are several engineers who don't know how to use it without spending the time. Auvik misses out on the wider base of engineers that could actively use it.

I don't know how long the company has been using it, but I have been using it at my current job for roughly a year and two years at my previous job. 

I've never really had a stability problem with Auvik, and if there ever is an outage, it won't be the end of the world for our clients.

The scalability is pretty good. It depends on how your company is scaled, but I believe Auivk can scale well. At the same time, our environments don't change too much, so I can't speak about huge enterprise environments.

We had a homebrewed solution that I've used before. I don't remember what it was called, but it also used SNMP credentials for monitoring networks. We also had a platform called ConnectWise Automate that managed some infrastructure, but it does not manage the networking part of the infrastructure. It mostly managed servers and hosts and some endpoints. It's huge that Auvik can reach all of those.

The previous solution was on-premises. Auvik's cloud-based solution makes it a lot easier, especially for a distributed enterprise. We have so many different customers with data centers, so it's crucial to have the ability to monitor and manage the solution remotely and switch through different tenants under our primary client login. It's a pain if I have to log in to someone's network and pull up their on-premise monitoring system, especially if part of their network is down and that tool is not accessible.

I am involved in deployments of Auvik for new customers or when customers open up new sites. Deploying Auvik is straightforward. It was initially implemented before I started with this company. When we acquire new clients, I set up the network probe and pull their tenancy into ours. The network map populates about two hours after you deploy the connector. 

It takes about 15 minutes to install the collector, then you need to ensure that you have all the correct device login information and SNMP credentials. That can take a long time depending on the number of devices, and the type of credentials. You also need to ensure your documentation is correct. That process can take anywhere from half an hour to a full day.

Auvik requires some maintenance, but it mostly just works. You need to comb through it once in a while if you're swapping out device infrastructure or spinning up sites. If things are being added to or removed from the network you need to ensure that it's representing your environment accurately.

To make an educated comparison, I'd need to know the other tools' capabilities in pricing. I'm not in management, so I didn't evaluate competing products, but I do know that Auvik saves a lot of time for critical responses and maintaining network inventory.

I rate Auvik eight out of 10. I recommend first deploying Auvik in a scaled test environment, so you can break things without impacting the customer. You should see what it can do and how you can troubleshoot using it. I was sold on it once I saw the value in the response times.

It is used for network monitoring.

Auvik hasn't really improved things for us. We tried Auvik, but it didn't meet our needs.

I found the ease of setup to be a helpful feature. The appliance was quite quick to get running. The fact that Auvik is a cloud-based solution, as opposed to an on-prem solution, meant there was one less thing to worry about. I didn't have to configure another device or provision a server and support it myself. It was easier having it supported by someone else.

The interface is also quite nice. Another part that is very easy to use is the monitoring and management functions. Ease of use is awesome.

The overall intuitiveness of the visualization was very good.

I require the monitoring of Linux devices and it doesn't support them. Although we've done a trial, we're not going to carry on with it. We've already gone with another product.

Also, seeing the topology is quite useful, but it's not really suitable for a large enterprise.

It also wasn't able to inventory everything. We're using Lansweeper, which pulls the serial of every single IP device, but Auvik only seemed to be interested in SNMP. It didn't care about non-SNMP devices. The solution needs to move past just having SNMP. If it could have other ways, like an agent, that would make things easier. The lack of being able to communicate with non-SNMP devices was the issue.

I used Auvik as a trial for a couple of weeks.

It was very stable. There were no outages that I was aware of.

Because it's cloud-based, it scales almost infinitely.

I didn't need to contact their technical support. The documentation was quite good. It was quite easy to get going.

Our current product was out-of-support, so we were looking for alternatives.

The initial deployment was very easy. We used the VMware template. It took under an hour after the collector was implemented for the network to start to populate. The actual deployment took about 20 minutes.

We deployed it in a test network. Obviously, we were not going to let an unknown product loose on the entire enterprise network.

It was just me involved in the deployment and there was no maintenance required.

If you're a small company, Auvik is probably quite reasonable. But we've got 500 servers, so pricing suddenly became a lot more of an issue. There needs to be better bulk pricing for it.

We evaluated Nagios and Spiceworks as well. We decided to try out Auvik because we were looking around and wanted to try everything we could.

Make sure that all your devices are SNMP-capable before implementing it.

Auvik was quite good at what it did, which is monitoring SNMP devices, but it didn't have enough there to monitor an IP generic device. If it wasn't SNMP, it didn't really work. It needs more agents and more monitoring methods.