Auvik Network Management (ANM) Reviews

Auvik helps us manage all our devices on the network.

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

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

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

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

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

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

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

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

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

I have been using Auvik for around two years.

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

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

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

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

Positive

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

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

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

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

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

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

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

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

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

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

We use it for network monitoring and for configuration backups.

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

It has also reduced our MTTR by about half.

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

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

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

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

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

I've been using Auvik for about three years.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Positive

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

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

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

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

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

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

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

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

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

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

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

As the IT manager for our two-building campus, I collaborate closely with our Managed Service Provider to leverage Auvik Network Management for comprehensive monitoring of our network infrastructure, including switches, firewalls, access points, and other typical small business network devices.

We chose Auvik Network Management to gain better visibility into our network, with real-time alerts for any device going offline, while also providing a centralized location for backing up all our device configurations.

While the dynamic map's initial behavior took some getting used to, the UI itself is fairly straightforward. Once I figured out the filters and other controls, I've found it to be quite user-friendly.

The clear network map with hover-over information for nodes and connections has been a big help. It not only visualizes the network layout but also provides details on how the connections function. Auvik's insights helped in pinpointing my VLAN misconfiguration earlier on, making troubleshooting a breeze.

Auvik offers a near real-time view of our network allowing me to diagnose traffic issues based on patterns or user reports. However, it seems Auvik double-counts traffic on our core switch's stacked lag links, making it unclear if we're seeing total traffic or just lag traffic. This is because Auvik reports on the virtual lag ports, their member interfaces, and the switch's stacking ports, which can sometimes be misleading when mixed with regular traffic data. Overall, Auvik is still helpful for monitoring historical traffic trends.

The network map and dashboard offer full visibility of our entire network's health, including any current issues thanks to the integrated central alarm station that displays known outages and potential problems.

While I wasn't involved in the initial deployment, Auvik is a significant improvement over my prior experience with open-source management platforms. It offers a much more centralized view, making it easier to see all devices and their connections.

Auvik allows us to spend less time on the setup, maintenance, and issue resolution. Pulling switch configurations simplifies tasks like replacing equipment or troubleshooting. Having the configuration readily available allows us to see things like traffic patterns, which can help pinpoint issues like port misconfigurations, without needing to delve into switch menus and trace information through tables.

I love that Auvik manages all of the credentials for me. It's incredibly convenient to have both SNMP monitoring and remote terminal access available through the web interface, no matter where I am. This gives me great visibility into my network devices.

It would be useful if network monitoring tools could differentiate between traffic on individual physical ports and traffic on logical interfaces like LAGs or bonded interfaces. Ideally, the tool would also recognize and remove duplicate traffic counts within the overall flow metrics. While solutions like Auvik might not currently offer this functionality, tools like NetBox can be helpful for documenting physical layer connections. It would be interesting to see if Auvik would consider incorporating features to document these physical layer details alongside the logical network configuration, especially for long-term network management within an organization. This could provide valuable insights into how physical infrastructure translates to network behavior.

I have been using Auvik Network Management for two and a half years.

Auvik Network Management is a reliable system with occasional minor login issues that occur infrequently.

Auvik has responded fairly well as we've made changes to our network, but we haven't grown rapidly enough to see it try to scale.

While I wasn't part of the initial network setup, I'm familiar with adding and modifying devices. Luckily, Auvik seems to catch these changes automatically.

Our Managed Service Provider used a consultant to implement Auvik for us.

I would rate Auvik Network Management eight out of ten.

Auvik is generally low-maintenance. While I occasionally verify switch imports and credentials when adding new devices, I haven't encountered any need for regular, active maintenance of the product itself.

Auvik Network Management offers filtering views and adjustable time scales, which are valuable features once you discover them. Additionally, you can manually add devices that the discovery tool misses, such as unmanaged switches, for full network visibility. This covers most of your visibility needs.

We use Auvik for network troubleshooting and monitoring.

We needed more visibility into the networks we manage. Auvik's automatic network mapping was something that helped us visualize the Management Network. The benefits were immediate. We quickly identified a few problems and resolved them quickly. For example, some links were slower than expected, and we remedied those issues fast.  Without, Auvik we would need to spend more time troubleshooting.

Auvik has helped our junior technicians solve more tickets. We've encouraged them to use Auvik, which enables them to navigate a network visually. I think they would have trouble without that visualization. 

Auvik's visual mapping and search features have been very useful. We can locate precisely where each device is on the map. The network map provides a real-time picture of the network that offers total visibility. 

The interface is good, but it can be sluggish and difficult to use on a small screen. I usually need a large screen to navigate it when monitoring more complex networks.

Also, the points on the network map will sometimes shift. They will be connected one way, but they will be connected a different way after I refresh. This doesn't happen often, but when it does, I question the reliability of our network map. 

We have used Auvik for nearly two years.

I've never seen Auvik crash, so I think it's 100 percent stable.

Auvik scales to where we need it to be, so it's perfectly scalable.

I rate Auvik's support seven out of 10. We contacted them about an issue with the mapping. The problem was complex, so it took a while to resolve.

Neutral

Before Auvik, we had another tool that was difficult to implement, so it wasn't deployed in many places. We also used UniFi's built-in network mapping, but that requires you to use only UniFi hardware. Auvik can integrate multiple vendors and do the same thing across the board.

Deploying Auvik was straightforward. It has an agent and uses SMP for the devices. We already had SMP enabled, so it was easy. We did it in-house, and it took about two months to fully deploy. About eight people were involved, including Auvik's support. It doesn't require any maintenance aside from onboarding devices. 

Auvik's pricing is decent. I forget exactly how much we pay, but we've never been dissatisfied with the value we get from this. The licensing model is palatable to us. I haven't looked at the licensing too closely, but I believe Auvik only charges for some devices, not based on the number of endpoints at each site. 

They also have an add-on product called SaaS Management. We did a demo but didn't purchase it.  While it's useful, I think there are too many drawbacks. We thought it was a little expensive and didn't feel we could get enough value from it to justify it. It was interesting but somewhat invasive and a tough sell to our customers. Considering the potential invasiveness and price, we decided not to deploy it. 

I rate Auvik eight out of 10. Auvik has a very short learning curve, so you can jump in and start using it.

Auvik's time-saving features allow us to focus more on critical projects and business initiatives, particularly during our company's renewal phase. Instead of spending time on setup, maintenance, or issue resolution, we can now dedicate our efforts to developing new solutions for managing our next-generation infrastructure, which is crucial in the telecommunications industry.

In terms of improvement, while the network map and dashboards are generally easy to use, the NetFlow app can be a bit compressed and difficult to customize for better readability.

I have been using Auvik for a couple of weeks now. We initially tried out their trial and found their network management features promising, so we decided to subscribe for a month. Since our network infrastructure has grown organically over time, we need a clearer picture before implementing any updates. Auvik is helping us understand our network better.

Auvik's support has been excellent right from the trial phase. Even though we were only at tier one, they were very prompt and helpful. They even helped us solve some tricky configuration issues by granting them access to our dashboard. Their support team is top-notch and very capable. I would rate the support as a ten out of ten.

Positive

Before using Auvik, we tried Zabbix and PRTG for network monitoring, but they didn't provide the topology insights we needed. They focused more on receiving SNMP traps. Auvik stood out for its ability to give us a clear view of our network topology, which was our key requirement.

Setting up Auvik initially was a breeze and it took less than an hour. Whether you are installing it on a physical or virtual machine, the process is straightforward. I used a Docker release on my old Mac desktop and it ran smoothly right out of the box with just a few clicks.

I find Auvik's pricing to be a good value for the features offered. With the professional plan costing around $15.30 per month per device, it is affordable, considering you only pay for active devices like routers and switches. For us, considering our network costs around $400 per month, which we see as a worthwhile investment for the benefits it provides.

I find the Auvik user interface easy to use overall. However, one drawback is that once the network topology map is generated, it is a static view and you can't remove or rearrange devices. This makes it a bit cumbersome to navigate, especially for networks with multiple devices. Exporting the map as a PDF also maintains this static view, which isn't ideal. To work around this, we export the data to Excel and use other tools like draw.io or Visio to redesign the topology for better understanding.

I use Auvik's dashboards, and they generally provide a real-time picture of our network, which is quite accurate. However, there can be some false positives, especially with older devices. The dashboards help understand overall network health. 

Auvik offers free monitoring for all devices except routers and firewalls. This includes devices like network-attached devices, PCs, and printers, making it cost-effective for monitoring a wide range of assets. Additionally, Auvik provides monitoring alerts for device issues, such as low printer paper, adding value beyond just network monitoring.

Overall, I would rate Auvik as a ten out of ten.

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

It's a SaaS application.

It has definitely helped us to put out fires before people even know there is a problem. It helped us to discover a lot of network problems with one of our buildings so that we could have it rewired.

We're a pretty small team, there are four of us in IT. I'm the primary network person and then I have a backup. Auvik does help him and other members of the team, and our developer. We all wear multiple hats, but we have our specialties. It helps everybody on the team when I'm not able to get to something, and somebody has a network issue. It helps everyone else to diagnose the issue if I'm tied up working on something else.

The solution has also decreased our mean time to resolution by at least half. We're able to very quickly see what's going on. We can see the connections within the image it shows, but we can also deep-dive quickly through the TrafficInsights and the logging. Even if you quickly go ahead and make a decision to reboot something to restore service, you can still capture logging and things that would normally be on the device, so that you can quickly figure out what happened. That helps with root cause analysis for after the fact so that you can come up with plans to avoid the issue going forward. That's the kind of thing we didn't have before. Before we'd have to make a quick decision regarding, "Do we troubleshoot this to figure it out or do we go ahead and just reboot it?" Nine times out of 10, that'll probably resolve your issue.

It's a network monitoring system, so being able to see things like the hardware lifecycle, if our equipment is up to date, if connections are broken, or whether there are physical line breaks, is helpful. We're able to determine connectivity issues. We can monitor pretty much anything that is network-related.

It's fairly easy to use out-of-the-box.

We also use the TrafficInsights feature and it has been a huge help to us. Using it, we can see interface utilization, both WAN-facing and LAN-facing. We can see what kind of bandwidth we're using and what is using that bandwidth: what type of application, what host is using it, and how long it's been using it. And the historical data of TrafficInsights is great as well.

With TrafficInsights, we can obviously tell when our backups are running, because we run nightly backups and hourly backups. We can see the performance utilization of our backup server. And we can also tell, end-user-wise, what applications end-users are using and how long they're using them for. And while we don't necessarily know what they're doing, at the same time we kind of do know what they're doing. We know what websites they're going to, so we understand how they're utilizing the internet connection.

When it comes to identifying where we are experiencing performance issues using the TrafficInsights feature, I'm actually working on that right now, for the comptroller of our company. It's mainly about trying to get her to call me when it actually happens so I can log in and see it. This is the first time I've used it to diagnose an actual connection problem.

Auvik's network discovery capabilities are pretty fast. The biggest thing is that you have to commit to SNMP. You have to turn that on so that you can get the layer below. From a ping perspective, it does a great job of discovering devices on the network, once you have pointed it at the right entry point. You have to commit to a few protocols to open up the network so that it will get to the levels below the surface, where you're actually pulling information, data, logging, et cetera. If you really want to manage the network, you do have to open up a few protocols.

It also automatically updates network topology. It has a great map view of everything so that you can see all the connection points and the health of a connection. You can say whether it's a ping or if you have the right protocols set up so that you can pull in information. It's very easy to quickly see, from a graph, where you need to possibly address setup issues. The other thing that is great about the highlighting is when you have unknown devices on the network. They will come up and you can quickly filter for them in a very easy-to-use table. That way, you can tackle if they really are unknown devices or if somebody is trying to do something they shouldn't.

It's rare, but sometimes the actual application itself can be a little slow. That's because of the amount of data that it is pulling from remote networks. That has been my only complaint with it and it's really not even a complaint. But if the speed of the application were to improve, it would help a lot.

We've been using Auvik since December, so it's been about six months.

They do really well with the availability of the application. When they need to take maintenance windows, unless it's emergency maintenance, which I've only seen one time, they always have a backup. That means it's pretty much available all the time. We've never had a problem with it going down, ever.

It's pretty scalable. It's always easy to add on another visible device. Depending on how you decide to set up your network, you're going to pull in anything that isn't a piece of that main entry point. From a pricing standpoint, that part's good. 

Their technical support has been crazy good. A challenge for us, if we wanted to consider leaving the product, is just how good they are. Not only were they engaged from the beginning—even as easy as it was—but they guided us through and showed us different tools. They gave us multiple workshops. And even after those workshops we've had quarterly follow-up.

They really want you to use the product. It's not even a partnership issue. Rather, you can just tell they love what they do. It's definitely one of the better relationships I've come across in the last 20-something years of IT. That made the decision to go with them really easy for us. We felt really good about it after as well.

They're also very open to feedback and to looking at what that can lead to in terms of development and enhancing of their product. They've done so much reaching out to us. We have nothing but great things to say about them.

They definitely work with us. They don't just say, "Here, we sold you a product." They want us to get the most out of it, and that's what changes it to a partnership-type relationship.

We didn't have anything before Auvik, and it's helped out immensely.

There are a couple of tricky things to set up. You've got to know the equipment that you're running, but once you know that and you work alongside Auvik and use their Knowledge Base, it's extremely easy to set up. We had ours up and running in a day and we had it fine-tuned in a couple of months.

As a cloud-based solution, other than troubleshooting, there's barely any maintenance on our side. A lot of it is just the initial setup, such as getting a site running, and even that doesn't take that much time. You can have a site up and running and loaded in 30 minutes or less, if you know what you're doing. It's very straightforward, very easy to use, a lot of it is point-and-click. Once you've set up a few sites, you tend to know it like I know the back of my hand. It's super-easy for me to set stuff up.

We worked with an Auvik technical engineer. They had a deployment roadmap that we followed, and typically, every other week we were going through the different features and functions. We would set up a meeting to go over, for example, setting up SNMP and SSH login and turning on TrafficInsights. They helped us tune it to the way that we needed to use it.

The time-to-value ratio, for us, was day one. We had nothing before Auvik, so as soon as we got the product up and going, we were already seeing the networks through the discovery services. After a session of a few hours, we started to understand the SNMP and how to set things up and pull in a lot more of the logging and alerting, detailed information regarding the traffic. Within two to four hours, on top of the discovery stuff, we were off to the races. We quickly discovered versions and where we were from an asset-management perspective. We could see older equipment that we had, and we were able to quickly target a hardware refresh. The time-to-value was almost instant.

It's great for small businesses, but when you start reviewing the pricing model, depending on how many devices, and what sub-devices you decide to pull in, it can get tricky as far as the pricing goes. 

For us, as a mid-sized organization, it works great. There are some functions and features that you might get from a Meraki or from SolarWinds that, if you have a more robust networking team or a security team, might be useful, and Auvik might get passed over for an enterprise-grade solution. That said, Auvik is phenomenal for us. It's great for what we use it for. It gives us a very powerful tool at a very cost-effective price point for our size of an organization.

We have 20 to 25 billable devices. In terms of endpoints, we at least have 250 machines and there are a bunch of printers that we've got alerting on, and other miscellaneous devices that are connected to networks.

The challenge might be for a more robust network, where you start putting in a lot of billable devices. There's going to be a point where this solution would potentially be more expensive than some of the enterprise solutions, just because of the billing structure. Auvik could potentially price itself out of large organizations because of how it does billable devices and lose out to solutions that not only have more robust services but that price things out differently.

We have looked at a couple of open-source, network monitoring solutions, but they weren't as robust as this. NinjaRMM was one of the solutions we looked at. We pretty much just chose Auvik and moved forward with it. 

The strength of Auvik, and many of the tools at its price point, are the out-of-the-box monitoring capabilities. Where Auvik pulls ahead is when you set up SNMP and you're able to scan the layer details and information from all the devices underneath. That's when you're really going to start getting more of the robustness it offers, whether it's TrafficInsights or it's the asset management that comes from having a network monitoring tool. That's definitely where it comes out ahead. Ninja RMM, for example, is just giving you a high-level inventory of what it sees on the network. It probably wouldn't give you much more than a Lansweeper or the like.

My recommendation is that even if you have network experience, their product is vendor-neutral, so pay attention to the way that they do things. Even though it is specific to them, it's very easy to get used to the way that they have everything laid out.

Take advantage of the training sessions and of all the meetings. Go through the certification course that they have and pay attention to the Knowledge Base. Everything that they have done shows that they actually care about what they're doing and what they like doing. They are there to help. They will bend over backward to help you.

It does configuration backups and it takes them automatically. I also do those on the side as well, manually. In the event that something does happen, it's always better to have a backup. We've got backups for everything. We haven't come across any issues where we've had to use the configuration backups yet.

It does its job well. I would rate it at nine out of 10. I'm a little bit more network-driven, so a lot of the things it can do are fun, for me. I probably enjoy it more than anybody else on the team. 

You can definitely tell that this solution is younger than some others. It definitely knows its niche. It gave us everything we needed, to the point where I could rate it an 11 out of 10. But if I start to look at SolarWinds and some of the other names out there, some integration capability to do all the clicks within the service would probably be the next improvement that I would want. But if you ask for those, it may price itself out of where it's at now, which is a really great spot.

I don't see us leaving it for quite some time for sure.

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

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

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

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

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

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

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

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

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

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

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

Their documentation and knowledge base can also be improved.

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

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

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

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

Positive

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

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

It was all deployed within one day.

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

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

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

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

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

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

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