Auvik Network Management (ANM) Reviews

It gives me an overall idea of our network. It shows me where things are at. It tells me about devices being down, e.g., printers. I also use it to see web usage, e.g., what sites people are going to. It has a lot of uses. I check to see the overall network topology, when things go down, or whenever I get alerts from Auvik.

I use the reporting part of it. Every day, I take a look at the reports every day.

We are using the latest version.

It makes it simpler and easier for me, as an IT person, to manage my network.

The automation of the network mapping enables junior network specialists to resolve issues directly, freeing up senior-level team members to perform higher-value tasks. This has made our operations easier, simpler, and faster.

As things change on a network, Auvik detects that and automatically changes based on those changes. It makes things a lot easier. You don't have to figure it out by mapping it out on a paper, etc. You can just go there and see how things are connected. So, it definitely helps.

When the systems go down, Auvik is a pretty useful tool. It lets me know ahead of time that I have an issue somewhere.

It is pretty easy to use. It kind of deploys itself. You put some passwords in there and it just kind of spiders out into your network, testing everything. 

Its network discovery capabilities are pretty good. It kind of spiders out and detects pretty much everything on the network, e.g., things that we are using and not using anymore. Its network discovery capabilities allow me to detect these things so I can track them down and shut them off.

The reporting needs a little bit of improvement. Sometimes, I get too many reports. Or, I don't get reports when I should be getting reports. I don't know if this is Auvik's fault or the devices that the reporting is coming from, but I have noticed there have been some discrepancies.

I have been using Auvik for five months.

I have had no issues with its stability.

I get emails letting me know that Auvik will be down for maintenance or updates. No maintenance is required.

Our environment is not very large. I am the only user of it.

I haven't needed to use the technical support.

We didn't previously have anything in place. We looked for a solution because we had nothing in place for network topology and reporting on systems being up and down as well as having the reporting on other things that Auvik does.

The initial setup was a little complex.

The deployment took four sessions, which were an hour long each.

Auvik suggested that we put it on a relay server, then we took it from there.

I did need some help from Auvik specialists. With some of the switches, I needed to get them in the device and reporting correctly. There were some problems, so a specialist had to get on and help me configure it.

Auvik has decreased our mean time to resolution by 50%.

I find Auvik kind of invaluable. It wasn't that expensive and did provide me with a lot of information. So, it is pretty beneficial.

We have licenses per year. It is on a network device, so we pay for switches and firewalls. Everything else is included, e.g., computers, access points, and printers.

Auvik offers a trial period. I recommend taking advantage of that and seeing if it works for your environment.

I looked at competitors. Other providers had multiple systems. I just wanted a single system to do everything. So, Auvik was an all-in-one package.

The TrafficInsights feature shows us network bandwidth usage without the need for expensive, in-line traffic decryption. I use it to see what sites people are going on and how to block certain things, like social media. Though, it is not that important to us, because we don't have an issue with our bandwidth. So, if we had an issue with our bandwidth, I would have to monitor it more, but we don't at the present time.

Auvik is very useful. I would rate it as eight out of 10.

The primary use case is network monitoring.

One of the things that I like the most is being able to see what is connected to each switch port. If there are 300 switch ports, I can find out which port any given computer is connected to on the network, assuming it is physical. We then can label certain ports as uplinks, servers, or storage. It is easy to find where a lot of traffic is coming from because we can get to that individual switch level, which is a lot easier to do in Auvik than it is to do native in the equipment.

Remote accessibility of the network devices is the most valuable feature. I often have to log into switches and routers to make changes, and I can do so from any computer as long as I have an Internet connection. I don't need to have my laptop or a VPN. Auvik is faster.

Auvik automatically updates our network topology. The topology map is drawn in real-time. Seeing the network versus visualizing is helpful. With real-time and historical monitoring, we know when devices are offline or if there is high utilization, specifically with the SNMP monitoring and SSH monitoring.

Its network discovery capabilities are really strong. With the right access, it can detect additional networks, then scan those networks. 

It is easy to use, yet not easy to administer. If I am a technician, then I just need to log in to a switch or see what the network is doing and what it is connected to, which is very easy to do. If I am an administrator, then I have to maintain, clean, and label that environment. Auvik's utility in that regard is cumbersome. It is hard to find where certain things are configured. Also, it is sometimes hard to figure out why Auvik is doing what it is doing.

There is a weakness with the network discovery capabilities, e.g., if it has access to virtual machines, then it is picking up on networks that don't matter. These are private virtual networks on individual computers, but Auvik doesn't know the difference. So, it is constantly coming up with new networks that it thinks it needs to scan. In my environment, I have 250 computers with probably 100 people who are running Hyper-V. Each one of those instances is creating virtual networks that it is getting discovered, then I have to tell it to ignore it. I have never seen the ability to say, "Ignore the networks or submits that look like this."

Sometimes, the UX is difficult to navigate for certain aspects. For example, I like to keep the generic devices out of the topology, so I often will purge those, but I only want to purge the ones that are offline. In the managed devices section, although you can filter by generic device, you can't filter by up or down status. You can only do that in the device section, not the managed device section. So, I have to take a picture of the generic devices that are offline, then navigate to another area where I can actually delete these objects, then select them using a picture. I can filter in one place, but I can't delete. Then, in the other place, I can delete, but I can't filter the same way.

At this company, I have used Auvik for a year and a half. Prior to that, I would say that I used it for about three or four years.

The stability has been fine. I get notifications for network maintenance and there hasn't really been an issue with that.

It requires no maintenance.

The major limitation is the multi-tenant aspect. For example, if I was to put this in a business that had six corporate offices, which is a pretty big business, I wouldn't want all of that under one tenant. I would want that under separate tenants for each location, but there would need to be an eagle eye view of the six locations from a high level, and you wouldn't get that in multi-tenant.

Auvik for MSPs is great because you can segment/isolate the different clients. However, Auvik gets overwhelming when it is a big business with multiple locations, hundreds of networks, and thousands of ports. I think that would be difficult to manage. If you are talking 5,000 to 100,000 switch ports, then you are talking about a lot of networks with a lot of different viewings and protocols. There really is a limit. There is almost no support for any kind of routing protocol. Where there is the Layer 1 and Layer 3 bars that tell you if it is physically connected or Layer 3 routed, the Layer 3 router should really include things, such as, what is the routing protocol that it found or the ability to see a trace route of how it is routed.

Sometimes the technical support is really good, and sometimes it is just terrible. Some of the gentlemen and gals are extremely knowledgeable when it comes to networking. They know the product and are very helpful. Then, some of them don't really get engaged in the support. They will just send an article/link, like, "Read this and do it on your own." I don't reach out to support because I can't find an article or do it on my own. I reach out because there is something I don't understand or don't know how to do. Making sure that they understand what it is that I am trying to accomplish requires a conversation, and some are willing to get on a phone call and some of them are willing to. The ones who are willing to get on a phone call are the ones that I have the best experiences with.

The initial setup was pretty complex. The company that I work for moved out of an office where we had 60 to 70 switches. Now, we are down to about 12. Therefore, the setup was more complex back then, although we only had one location. Now, we have one location and one data center. The deployment took four to six hours.

Auvik's setup time and automated network mapping and documentation provides time-to-value. It is very valuable in that sense. For a small environment, it rolls out for you very quickly, e.g., five minutes. Roll out the collector and let it do its scan, label one or two networks that are there, throw in the credentials, make sure it is identifying everything, and you are done. Then, it just kind of works. The amount of value that you get then in perpetuity to the relative installation is very high, but as a single IT company or an employee in a single company, that quick rollout isn't as valuable because I am only doing it once.

I did the deployment myself. I have used Auvik before, so I just set the collector using VMware OVA. I put a collector in our office, labeled the networks and set exemptions from the scan, and then just let it go. Obviously, I tried to enter all the credentials that I could at the time, but then I found I had to make modifications to group policy so the computers and servers could be accessed. So I probably just threw it out there and then added the credentials later. If I had to do it again, I would have put the credentials in first then threw it out there.

We are not making a profit on Auvik. It is an expense.

Although networking is only a small piece of what I am doing, it can be a time-intensive aspect. So, the time required is significantly less using Auvik than it is to manage the devices individually.

As an individual IP company, Auvik is a little bit pricey. It is a little expensive, but as an MSP owner, I have a small side business. So, I'm an Auvik customer in that sense too. In that, I think it's reasonable to pay $10 to $15 a device or less depending on the endpoint. For the amount of capability that it has, it is very reasonably priced.

There are devices monitored at no charge, such as:

• UPS batteries
• VMware ESX hypervisors
• Wireless access points
• Printers
• Dell EMC iLO cards.

I would probably compare Auvik to PRTG Network Monitor. I think Auvik is a lot faster than PRTG Network Monitor. I am not a very big fan of other solutions. I have never really tried them. 

Auvik gives us inventory. I don't think PRTG Network Monitor does that. So, I can integrate Auvik with our IT Glue cloud status, then we have an inventory of network devices that we don't have to manually create. It saves some time there. PRTG Network Monitor doesn't do that.

PRTG Network Monitor is easier and simpler to set up because it is not trying to do everything that Auvik is trying to do. Once you point it at a device and give it the credentials, it just starts monitoring. At the same time, it doesn't show the relationships between other devices; it doesn't show those connections. It is not an apples to apples comparison. 

We haven't had any SolarWinds Orion products. Now, we wouldn't buy that at all. Auvik is far easier than Orion.

My team members aren't really using it. The other guy is kind of a junior IT guy, and I think it is still intimidating to him. My boss is a higher level engineer, but he is too busy managing to do anything technical. He just relies on me to tell him if there is anything he needs. He mostly wants the solution for the monitoring. He wants to know when a hypervisor module is failing or a hypervisor server goes down.

If you don't put in the credentials, Auvik can't log in and grab those device backups. Once you put those in, then it is automated. It logs in and grabs the configurations. Although, Auvik doesn't support all devices. So if you don't think you have certain types of hardware, it doesn't do anything for you.

Networking has a high learning curve and Auvik lowers that learning curve. It doesn't eradicate or eliminate it though. You still need a pretty strong level of understanding of networking in order to understand the GUI visualization that it is presenting. Just like any other tool, the time invested is largely going to determine the quality of your return.

Auvik has a little ways to go, but I still highly favor it, so I would rate it as an eight out of 10.

We are a multinational company in almost 55 countries. One of the reasons why we selected Auvik was we wanted to have insights into our networks. Ultimately, we can control them at a central level. Auvik was the best fit because it has:

1. A cloud-based solution using a SaaS model. 
2. Visibility into end users using tools. 
3. Terminal auto-connect, where we can connect devices from Auvik. 
4. Some sort of an audit. 
5. Backup consultations in the tool, which it maintains. 

It has really eased our life in terms of network operations.

It is improving our network operations in 55 countries, including the US, Latin America, Europe, the Middle East, Asia, and Oceania. 

Auvik automatically updates network topology. Since it automatically updates the topology, we proactively know what is happening in a country or our branch offices. It also alerts us if there is a topology change, e.g., if it discovers anything new in that country. So, it has reduced the number of failures in our operations. We went from being reactive to proactive. So, we are no longer reacting to what is happening and others are doing. This has saved us about two to three hours a day. We used to spend two to three hours every morning checking the firewall and router logs for malicious behavior.

The automation of network mapping enables our junior network specialists to resolve issues directly, freeing up senior-level team members to perform higher-value tasks. The type of views that we have Auvik automatically discovering has helped our operations, as issues get resolved at Level 1 or 2 with the help of the topology. They don't go to Level 3 until they are serious. 

Auvik has decreased our mean time to resolution. Around three years back, there always used to be a heavy load on Level 3. Nowadays, in a month, there are maximum two tickets that reach Level 3. They all get sorted out in Level 1 and 2.

The most valuable feature is the auditing part. Whenever we are doing any changes, it captures those changes. Date-wise, if we want to refer back to them, we just need to view the date when we did those changes and it will give us a comparison of what has been changed from the last concept. 

The Auvik terminal's service is a value-add to our operations.

It is very user-friendly. It is easy to use, understand, and deploy. My guys have not taken any training from Auvik, but we have learned the systems quite quickly. Because it is user-friendly, you don't need professional training for it.

Auvik's network discovery capabilities are awesome. It not only discovers the network, but it also gives you a map by designing how your network will look like in your environment.

Auvik has very good alerting modules. If a connection or device goes down, it alerts us right away. A good part of that alert is it has some sort of intelligence mechanism. For example, if the router or network device has some sort of malicious activity or critical issue, then it alerts us upfront. It will say, "Hey, you have some issues that you might need to check." It alerts us to critical elements before something bad happens. 

They need to improve the reporting system. They still don't have a proper reporting system in Auvik. They have built a dashboard in Power BI using APIs, but they should build some sort of report within Auvik itself. If Auvik fixes the reporting or comes up with a good reporting module, it will change the game.

I have already talked with the CEO of Auvik about this. He agreed that he will be working on getting some reporting systems in Auvik. As of now, they only have reporting via Power BI, and it is an additional cost to get the Power BI licenses. Another drawback, the Power BI reporting is not that accurate and you really have to struggle to get the reports.

I have been using Auvik for three years.

It is a SaaS-based tool. Auvik takes care of their hosting environment. So far, I found this solution to be more stable compared to other tools that we have used on-premises.

The scalability is good. An important thing about Auvik is that this tool is available from anywhere. For example, we are in a pandemic situation today and forced to work from home. Auvik gives us the capability to do our network operations from anywhere. This is one of the important features that I like about Auvik. For the on-premise solution, you have to make sure you are in the company network and have the VPN connected with the resources.

In my department, we have 46 people using it.

We are expanding Auvik into other countries. For now, we have expanded it into Europe and Asia as well as starting to expand it into the US. So, we will have a long journey using Auvik.

Their technical support is good. They need some improvement. They are not quick. Whenever we raised an issue with Auvik, which was two or three times, the technical support was a bit slow in responding to our issues.

We used to manage the firewall and routers manually, connecting to the countries' VPN. Today, we don't need to have them connected. We can just manage it from a single Auvik console. This has really changed our network operations. 

The initial setup is an easy, straightforward process. You just need to download the Auvik collector, and it is just three steps: next, next, and next. Then, it is complete. From the employee perspective, it saves you at least four to five hours. Other tools take people  a working day to deploy one site. Whereas, Auvik takes just a few minutes. The reason for that is they have their automated discovery capabilities, where you just put in your SNMP credentials.

I deployed myself in five minutes.

Three years ago, we used to work out of the office for hours doing maintenance, like patching and upgrading tools. My guys are no longer doing night duty for operations like that. We don't do any maintenance on Auvik because it is done by Auvik.

Compared to other products, Auvik's pricing is more feasible since you get all its features. You pay for licenses on a per network device basis. It monitors hypervisors, but does not bill for that. There are no additional costs, which is something that I like.

We did evaluate a couple of tools, both on-premises and cloud, then we decided to go with Auvik.

Auvik works smoothly compared to other tools. It also discovers the entire network in a respective area, then Auvik maps it automatically and gives you a good topology. This was a key factor in our decision.

Auvik is for any networking department. If you have a very complex network or a lot of devices that need to be monitored, Auvik would be the best fit. Auvik is not for a simple environment. If you have 10 devices or 10 branch/site offices, then Auvik is not a good fit because it will become expensive.

We are still in the testing phase of the TrafficInsights feature, which gives you full visibility into what is happening on your network. Also, the TrafficInsights feature will help you to say where protocols or services are consumed heavily. In the long run, it helps you to optimize your bandwidth based on your country consumption. It gives you a lot of details and integrated traffic insight, which we unfortunately need to hold back on because of data protection laws. 

It doesn't configure out-of-the-box automatically. That is a manual job.

For an enterprise environment, I would rate this solution as 10 out of 10.

I'm a systems engineer, so I use it for troubleshooting and for doing research, like baseline functions like figuring out network layouts and things of that nature.

What I really use the most is probably the devices section. The map is very helpful to me as well in my role.

I use the dashboard occasionally, and for the purposes that use it, it's pretty functional. It's pretty straightforward to use the network map and the dashboard.

I do get network visibility. For my purposes, it was partial. I do have to dive in to get some of the visibility I require.

The benefits witnessed were pretty much immediate after we deployed it. When we deploy to a new client, the benefits show themselves right away.

Auvik doesn't necessarily allow entry-level technicians to solve tickets on their own. You do need a little bit of experience with it. That said, once you do, it's very useful for technicians.

The product has helped to decrease our main time to resolution by 50%.

Auvik allows us to spend less time on setup, maintenance, and issue resolution. It saves me time in that I could dive in and get some answers that I would normally have to go through a couple of other portals to get to. I could find information that I needed from multiple spots just by going into Auvik.

The solution's interface isn't the most user friendly, however, once you get used to it and once you get into the groove and have a little bit of experience, it's pretty nice. For a novice coming into it, it's more difficult. I was overwhelmed, for sure. The layout just isn't the most intuitive. 

I've used the solution since 2019.

I've never run into any stability issues. 

The product is scalable. I've never had issues with our larger network.

I've never directly worked with technical support.

I haven't used any other similar solutions. 

I am occasioally involved in the deployment, however, not very often. It is easy to implement. It doesn't take long at all to get up and running. It takes less than an hour. 

We have a networking team, however, usually one person from the team handles the setup. 

There is some cleanup that needs to be done occasionally. Sometimes, when devices are decommissioned, they don't properly remove them, so we do need to manage that.

I'm not familiar with the pricing or licensing. 

I'd rate the solution eight out of ten.

I would advise new users to poke through the menus to familiarize themselves with it. When I first started using it and I found when people first started using it, it was a little bit overwhelming. That said, once you get familiar with it, it's a very helpful tool.

Our initial purpose was to look at network data from our endpoint protection units. We wanted more visibility into the traffic coming into and out of the organization.

One of Auvik's big benefits is that it's cloud-based. You have agents that you deploy locally, but other tools require us to deploy a virtual machine inside our network. We needed to secure the operating system on the VM and ensure it was always functional and patched. With Auvik, we don't need to worry about that. We periodically need to patch the VM that reports back, but it's not as frequent as managing your own virtual machine.

NetFlow data is available in Auvik. That's an advantage over other reporting tools. You can be certain about the data going in and out, so it's easier to troubleshoot bottlenecks and look at the network switch interfaces to see which ones are overwhelmed with traffic. 

Auvik has decreased our mean time to resolution by around 10 percent by improving reporting. We pick up errors that we could probably find with other systems, but the Auvik system is a little quicker about sending us the alerts. 

People typically use Auvik to look at NetFlow data, but we went for it because we wanted a convenient cloud-based platform to collect data that we don't have to host locally. We like that having space available is not our problem. You can deploy an agent on your network through a virtual machine running on a secure Linux operating system. It's a secure product, and the data we need is available in the cloud.

The interface is easy to use. You need to refer to the manuals, but there's enough documentation for you to get started without the need to contact support. We primarily use it for NetFlow data instead of network troubleshooting, but we launched a little project to look at internal traffic, and it was quite intuitive based on my experience. 

Price sensitivity is an issue in the country where we use Auvik because of our exchange rate. It would be helpful if they could offer a slightly more affordable price in this region. I'd also like to see Auvik introduce more AI-driven features. 

We've been using Auvik for probably a year already.

Auvik is 100 percent stable.

It seems like Auvik can scale quite quickly. We don't have a large network, but I believe it can scale well. 

I rate Auvik support eight out of 10. I haven't contacted them much, but I was satisfied with our limited interactions. 

Positive

We have used other solutions, but we haven't used something that would be considered Auvik's competitor. Previously, we used a combination of tools. We used some of the native reporting tools that came with products of some of the switches. Auvik's reporting delivers more granular details.

Auvik is a cloud-based solution, but you need to install an on-prem agent that communicates with the cloud service. The deployment was straightforward, and you can get the solution running in a few hours. It takes a little longer to start ingesting the data. We have two people monitoring the solution. It requires limited maintenance aside from periodically updating the agent. 

I can only say that I think Auvik is worth the price, but I haven't calculated an ROI. We spent less time implementing and maintaining it, and it has improved our resolution time. 

From our perspective, Auvik is slightly expensive because of the exchange rate between our country's currency and the US dollar. It makes a significant difference. Some devices are covered at no charge. We don't use it extensively, so it isn't that essential. Maybe we'll use it more in the future, so it's nice to know that they have free offerings we can use as part of the solution. 

I rate Auvik eight out of 10. 

We are a managed service provider, so we use the solution to monitor our customers' network environments.

Auvik provides a single integrated platform for network monitoring, but we integrate with other platforms for ticket generation and another dashboard we use, BrightGauge. 

The alert generation is excellent; we need to be able to look at a customer's network and see if there are any issues we should be aware of, like emergencies and offline devices. Auvik provides this and alerts us to issues before the customer calls about the problem. We had a case where a device failed, the solution notified us right away, and we were able to use the automatic backup configuration, which we restored to a replacement device.

The monitoring and alerting are the most valuable features. 

The automated configuration backups are another excellent capability. 

Auvik provides excellent visibility into our remote and distributed networks, which is especially helpful when onboarding a new customer. The solution offers great insight into the network we're taking over from a single pane of glass. This gives us situational awareness, allowing us to address issues, find credentials, configure, and correctly monitor network elements.

The solution's monitoring and management functions are more challenging than needed; the interface is sometimes unintuitive and confusing. That may be because I've never had formal training with the tool, so it can be difficult to navigate sometimes. This can be frustrating, as I sometimes need to go back to square one and follow multiple steps to get back to where I've just come from. For example, to access a list of devices I was just looking at because there isn't a direct path back.

I've had some issues where the solution repeatedly discovers a device I don't want to manage and alerts me about it. This is probably me not using the tool correctly, or it could be Auvik recognizing the device in different ways.

The solution sometimes finds networks and devices it sees, but I don't know where to begin looking to try and find out where it could have seen these from. Therefore, I want to know the path or details about the discovery, where the tool discovers a new network, and what way it takes to get to it and find that it's available to scan.

I also want Auvik to identify itself differently on networks because we have some firewalls that identify it as a potential risk, not only because of what it's doing but also because Auvik can present like a foreign intrusion into the network, which scares some of our customers.

We've been using the solution for almost two years. 

The stability is excellent; we've never had a stability issue.

The tool scales well, though we have yet to push its limits. We can manage multiple customers, and it's a tenant-based solution, so Auvik is as scalable as we need it to be.

I never had to contact tech support. 

We used MS Power Automate to monitor some of the devices we now use Auvik for, and Auvik does a better, more thorough job. We've also used the Kaseya VSA platform for monitoring. Still, Auvik is geared more towards the network, discovery, and monitoring aspects, which works better for us than other platforms.

I wasn't involved in the initial deployment, though I've been involved in the deployments to some customers' networks. In terms of maintenance, there are specific tasks we carry out as part of our obligations as an MSP around monitoring Auvik, but we don't need to do any maintenance with Auvik itself.

I'm an engineer, so I'm unfamiliar with the cost of Auvik and the other options on the market. My advice to those concerned about pricing is to do their homework and compare all the offerings. They could also demo Auvik to see if it meets their needs and justifies the cost.

I rate Auvik seven out of ten. 

A monitoring solution like Auvik is essential for any MSP, but other contenders exist in the marketplace.

Regarding reducing repetitive, low-priority tasks through automation, we're not currently using the solution for that. We could benefit from this area, but we have yet to leverage the capability.

As far as helping to keep device inventories up-to-date, I imagine the solution would help, but we don't use it for inventory.

As to whether the solution reduced our mean time to resolution (MTTR), I don't have access to those reports, but it's unlikely it impacts our resolution time. We don't continually monitor Auvik or have a staff member dedicated to working with it full-time. If we took advantage of the automation, I can see how the tool would reduce our MTTR, but we're not currently leveraging it as effectively as we could be.

My advice to others evaluating Auvik is they will need the hardware to run the collector at customer sites.

We are using it for monitoring and troubleshooting. It is cloud-based, but the collectors always have to be on-premise. We must be using its latest version.

It automatically updates your network topology, which has made any kind of troubleshooting or planning way more efficient. To make sure that everything is up for you, every 15 seconds, it checks for a device to be online and any network element to be up or down, and every minute, it checks for your other devices, such as your PCs or IP phones. It does a subnet scan every 600 seconds to see if thresholds are being pegged or have fallen off in certain levels. If you don't want to have so much ping traffic on your network, you can change that to whatever value you want. All that is customizable. It kind of becomes something you depend on when you're looking for a device. If I want to find out where a device is plugged in specifically, Auvik is the first place where I would go to check if I can see it there. Earlier, if I'm looking to see where a device is, I used to check my windows DHCP server and look for an odd or new IP address that had appeared. In Auvik, I can filter the map based on a device, subnet, or VLAN, or I can see all devices that are plugged into a specific switch, which is really convenient.

It has significantly decreased our mean time to resolution. In the past, sometimes, it took us a long time to come to the conclusion that this is the problem. When trying to go through the troubleshooting steps to know what the problem is, when Auvik has that information for me, troubleshooting is significantly quicker. I don't have to go through an entire department and look at their connections to see how they're impacted and then decide that everything they have in common is this switch. Auvik is able to tell me that this switch isn't online anymore. I can then say that we have a problem with a switch, and we're working on it to kind of calm folks down.

TrafficInsights dashboard is one of the first things that I log into every day in Auvik. Before going with Auvik, I tried a different solution for it, and that solution was just terrible in comparison. It only permitted five interfaces for traffic insights, and if you wanted more than five interfaces, it costed more money. It was just completely unreasonable. Auvik doesn't limit you on the number of interfaces for traffic insights. I get a better idea of the type of traffic on the network through Auvik than anywhere else. I can look at the type of traffic through my firewall monitoring, but I'd have to go a lot deeper into the protocols and ports that are being used just to see what's going on in the network.

With Auvik, if I look at traffic insights, I can get a good graph of how much traffic is happening at specific times a day. I can lay out the type of traffic and break it down based on the applications. I can then filter from there. If I'm seeing that we have a lot more web traffic or media streaming traffic, I can look a little bit deeper and see the exact applications, such as Netflix, YouTube, and TikTok. I can then see who is watching Netflix. It makes it a whole lot quicker than watching my firewall because I'd have to filter by a domain or IP address to come to the conclusion that someone is watching Netflix on the network. In Auvik, based on the filter, I can get all devices involved with that conversation to Netflix, which is a really nice feature. The other menus within TrafficInsights allow you to keep it all relative, so you're not resetting or recreating those filters. I can just filter based on Netflix and see who are the top users. I can see who is using Netflix and on which laptop they are using it.

The TrafficInsights feature helps in improving our overall network performance. It allows for me to look at a month's worth of time, and then I get an idea of what's the normal baseline. It helps me in getting a good baseline for expected backups because I can see when the backups are happening and how much traffic is related to backups. So, I can see when things are normal or abnormal. For example, when media streams are a little high, that's abnormal, so I will look into it a little bit deeper. It helps with this kind of stuff, and if there is any kind of impact on overall throughput for other users, I get to nip it in the bud right away, which is valuable. 

The out-of-the-box device configuration backups save time and money too. With Auvik, I can see the configurations even if I have them saved on the file server or something like that. If I got a protected share that has configuration backups, being able to deploy that configuration or even save that configuration as a text file from Auvik is a time-saver. I am not paying for the other product any longer just because Auvik handles that. Previously, I would have been paying for both. If Auvik couldn't do that, I'd have to pay for two products, so it saves money, but more importantly, it saves time. I don't have to spend so much time going switch by switch.

The best feature is the support access. Access to Auvik support is right there within Auvik. It has a little support button at the bottom, you push it, and you get connected with a support agent. They can see your internet. They help you out, work with you, and answer your questions right there. I don't have to go and open up a ticket somewhere else and try to explain anything, which is a great feature. I can get someone in less than a minute, which is really helpful.

It is very simple. It is very easy to learn how to navigate, and their knowledge base is a good resource. 

It is an SNMP-based platform. It can communicate with almost any device that you're trying to monitor, such as a switch or a router, through SNMP. If you're trying to monitor Windows machines, it uses WMI. It gives you a good layout of the sensors for a lot of devices. It can generate alerts based on if the fans are working, CPU is hot or highly utilized, or RAM is highly utilized.

The Syslog feature is also really valuable. I don't have to go into each individual box, so I have it all centralized. Everything is in one pane of glass. When I first started using Auvik, they didn't have the Syslog fully deployed. It was a beta. Now, it is fully deployed, and it is a great feature. Auvik really relies on SNMP in order to give you good information about a device, but our IP phones, for instance, don't support SNMP. With a phone pointed towards Auvik for the Syslog info, I can see the stats within Auvik, whereas before, I would have to go into the phone server and the phone to get an idea of what's happening with that phone. So, if someone is telling me that his phone keeps restarting or has bad call quality, I can go to that phone's Syslog within Auvik because even the phone itself doesn't store that information. Our phones only show the last six reasons for a reboot, and if someone is saying that reboot is the issue, then that's not good enough. You want to look for a pattern. You want to look for what might be happening internally on the phone. For that, you would have to go into the phone server and then get down to those logs. If the log info is already sent to Auvik, I don't have to go into the phone server and then write up a command to filter it down to just this little tiny query here. I could just look at that device, access the log info, and get what I need, which is very valuable.

It also gives you a live or close-to-live topology map. So, you can get down to things. For example, if all of a sudden a machine is really slow during the day for someone, or they lose connectivity, you can check out the machine baseline by name or by IP. When it is on a switch, you can check the port it is on and get the logs on that switch to see if there are any errors being generated on that port. So, it is just a lot quicker than going into the switch's interface. You can get information on the device via Auvik without going into each device separately. You can get a log, but you can't do any configuration changes. You can just get information on the devices, and then if you see that you need to make a configuration change. If you want, you can also tunnel in through that or do it externally. The ability to launch a console session to your switch, router, or any device that you're monitoring (if that device supports it), or launch a browser session through Auvik to that device is a nice little feature they have. You can interface right there through that single pane of glass.

It backs up my configurations for me. For the routers, I have a cloud-based subscription, and it backs up my configurations every 30 days. So, I can see the changes that were made, and then I can do an A/B comparison of the configurations and identify exactly what was changed. I can even redeploy the configurations from within Auvik, which is pretty handy.

I liked the Teams integration that exists in Auvik. We have Office 365, and I can create a channel within Teams where my alerts from Auvik pop up in Teams so that I can see a feed of different alerts. I have a feed of different levels of alerts such as emergency, critical, warning, and informational that are generated in Auvik, and if I'm not viewing the tab in my browser that has Auvik, and they pop up as alerts in Teams on my desktop. I might have a ton of tabs open, and if I am not viewing the tab that has Auvik, these alerts will pop up in Teams, and that'll get my attention. It also has the ability to send a text alert. It is indirect, and even though it comes to you in SMS or MMS format, Auvik sends it to an email address, and you can get around by using your MMS email address based on your service provider. So, staying informed about the environment when I'm not directly looking is definitely a valuable resource for me.

One of the great things about Auvik is the shared collector mode, which is useful in an environment that has more than one physical location. We have 15 different locations, and I can have all of those locations pointing to one collector. So, all these locations are sharing this one collector, and I can get a map, which is way out on top of the map that you would see in Google maps, to see all my locations. I can see alerts on that map for any of those 15 locations. I can zoom in right there to the location, and from there, click on it. It is really handy.

They don't let you customize the dashboard, which is like the homepage of Auvik. There is one feature that I don't use that's on the dashboard, and it is for SSL VPN services. The way it is designed is that if you have a separate, dedicated SSL VPN appliance, they can see that. I'd rather not have that take up any space on my screen because it never is going to populate with any kind of information. I'd like to move some things around on the dashboard, but I can't do anything like that. I know that they don't plan on doing it, but if they could open the dashboard just a little bit and allow us to customize it a little bit, it would be incredibly helpful, but it is not something that I feel I'm truly missing.

I wish they did have a few more integrations, and I'm sure that they're going to have more coming down the line. It was last month when I had a meeting with them, and their goal is to just kind of make it as universal as possible. So, they take some customization features or limit some customization features just because they feel that if they make it something you can customize, it might make it less universal. You can use their integrations with other applications. It integrates with the popular RMM solutions, and that's great, but when you are viewing Auvik through that integration, there is no way for me to limit or control how Auvik sees a location. So, I can't just have it default to a certain view. If you're looking at a specific department, I can't have everything automatically filtered down to that specific department. I'd have to go through and add those filters for Auvik to do so.

Most of the issues that I have had are related to the dashboard and wanting a bit more customization available through the dashboard because that's where you'll spend most of your time. Auvik is on the dashboard, and you can create and save these filters, which is great, but if I were to filter the map by all switches, the information below doesn't reflect the filter. I have to select the device within the filter, and then it starts to show the results. I can then see the dashboard of that device. If I were to filter by switches, I would like my top device utilization to only show me switches from my alerts and anything related to my map filter. That was something I asked about in one of the meetings with Auvik last month, and I don't think they have any plan to expand the dashboard anytime soon or at all. So, that was a little bit of a letdown. So, I am adjusting my workflow to fit the product and its abilities, but it really makes sense to me to expand it over time within the TrafficInsights dashboard. If I filter by my access points, then it should only show me the information related to my filter.

Another limitation, which is probably still under customization, is related to the reporting features. It doesn't really give you the ability to customize reports, create reports, or schedule reports. Adding those kinds of elements to it would really take it over the edge. It has some built-in reporting, and you can generate a report based on just a few things. You can do 10 reports that are built-in, but you can't create a report, and you can't customize a report. You can export the reports. It is designed that way. I would like to be able to create and schedule some custom reports. There should be the ability to do a temporary report. For example, if I am monitoring one or multiple devices for a week and I had the map filter to these devices, I'd like to be able to just quickly generate a report to be able to see how this device communicates, or how these devices are communicating over the course of a week. Such a feature would be really good. Reporting is the main thing that you're looking for in a monitoring system, and Auvik falls short there.

I probably have to look through the knowledge base to see if it does exist, but I do not believe there is a way for me to set a threshold for certain types of traffic. For example, when media streaming gets to a certain percentage of network traffic, I get an alert. That's why I'm kind of in it all the time. It is one of the tabs that I have open, and then I just take a look and see what is a little high and then zoom in.

Auvik doesn't deploy firmware upgrades and things of that nature. I don't know what would be required to allow them to be able to handle firmware upgrades for all these different devices, but it is probably not necessary for them to go that far because they'd have to open it up for so many different vendors.

I have probably been using this solution for a little bit over a year.

It has been incredibly stable for me. They do maintenance just about every weekend for adding new features or just cleaning some bugs up.

The whole ability to add more locations is really impressive. I know that people can have multiple collectors, but for me, I just have one collector and 15 sites sending information to that one collector. I can expand if I need to add more devices at a location or add a new location entirely. I can even reduce, which is great.

When I first set up Auvik, during that trial, I was seeing everything from one site. After a discussion with the guys in support, they recommended that I basically change the mode of Auvik to be a shared collector and make the other locations sites. This way I can just look at one site at a time, or I can come to the main dashboard and see all the sites from a bird's eye view. I can just continue to expand or compress based on my needs and preferences.

Access to Auvik support is right there within Auvik. It has a little support button at the bottom that you can click to connect with a support agent. You don't have to go and open up a ticket somewhere else and explain anything. You can get someone in less than a minute.

They've been great. All of my questions have been answered, and any issue I've had related to a feature within Auvik has been resolved for the most part.

The other product that I was using was a product created by the manufacturers of the devices. It was something that I thought would be perfect for the devices, but it wasn't. Auvik is superior across the board in comparison to that device. The only thing that Auvik doesn't do, but the other device can do, is deploying firmware upgrades and things of that nature. It is probably not necessary for them to go that far because they'd have to open it up for so many different vendors. I was using a vendor product for certain devices, and it wasn't reliable and viable.

I was involved in the initial setup of Auvik at my location. It was straightforward, and I was surprised by how much information Auvik can give you. The way they deploy is the smartest way to deploy anything. You go through that trial period with them where you'll give it all the time to gather the information about your gear. When you're actually talking to the guys, they give you a demonstration of Auvik in your environment related to your gear and the information Auvik will use, which is very important. 

Before we got down to the purchase, I wanted to see information related to the gear that I actually have, and that's important for anybody. I didn't want to see the hypotheticals of if we had a specific gear. Instead of deploying it in my environment with the belief that it is going to be great, and then realizing it is not compatible with this, I wanted to know that first, see it, and then decide whether or not that's going to be a deal-breaker. For example, I might get to know that Auvik is not going to show me information about the access points that I have because the manufacturer's access points don't have a feature that allows Auvik to see that information.

In terms of the duration, we gave it a weekend. There are different methods for using Auvik, and you can spin up a Linux box and install Auvik that way, or you can use their appliance. Based on your environment, they have their recommendations, and then you just let it sit for some time while you configure all your devices to communicate with Auvik. The setup configuration took me half a day. I had to make sure that I had the traffic all permitted through the firewall, the switches and routers were all set up to send information to Auvik, and SNMP communication was all good. After all that was set up, I just had to wait for Auvik to gather the information. I come in on Monday, and I saw all the information Auvik gathered about the network topology and other things over the weekend.

Comparing Auvik's setup time with other solutions, I haven't seen better. Auvik does the work for you. I spent half a day setting up the SNMP information and entering whatever credentials I needed to enter into Auvik for the WMI communication. After that point, you'd have to kind of trim it down. You have to say that I don't want to see the subnet because it'll scan everything. When you give it the information to look at your route, it'll be able to grab any route that your router can see. If you're not concerned with the public WiFi that you might provide and that your router might handle, you can just eliminate that from the map. You just say don't scan the network, and this way, you're only looking at the data that you want to see, which is really handy. So, in terms of the setup time, it is about how fast you can get into your devices and how quickly can you enter the credentials into the devices that you manage.

Its pricing is very reasonable. We had looked at other solutions where you pay based on the amount of traffic that was filtered through and analyzed. With Auvik, we pay by a billable device. For one of the locations I have, one network element would likely be a billable device. So, every billable device has a network element, but not every network element is a billable device. If I have a location that has 50 network elements, then maybe 30 of them are billable devices. PCs, VoIP phones, and access points are monitored at no charge. 

You pay based on billable devices, and that is very reasonable. You can control that to a certain extent and make a device unmanaged, but you don't get the benefits of Auvik being able to collect all of the information to make it useful. It'll tell you that this is an unmanaged device. You might know it is a switch, but it is not giving you any switch information. 

When you make a device managed, then it is a billable device. It is important to the whole cost of trying to replace your devices or expand your locations. You have to consider the cost of that switch. You have to think that if you are going to buy a switch, it is not just the price of this switch; it also becomes something that's billable in Auvik. Would you buy another switch, or would you replace the switch and buy a bigger switch? Auvik just continues to collect the data and continues to give you traffic insights, Syslog, and all other features that you want. It is worth it.

There was one other solution that was evaluated in terms of install, deploy, and configure. Other ones for which I had seen demonstrations weren't what I was looking for. They could do things similar to Auvik, but they weren't what I was looking for at the time.

When you're doing the trial, the trial is using your info. I would just say at least do the trial and see what it shows you and really explore all of the sub-menus. If you're looking for insight and alerting based on thresholds and health checks, it is definitely something worth looking at. It might take you some time to configure devices to communicate with Auvik, and then just let it do its thing and watch.

It is a little difficult to say whether Auvik helps us in putting out fires before people or end-users even get to know that there is a problem. If you are at your computer and your switch goes down to which it is connected, you're going to know at the same time I get to know, but I will know what happened. That is the kind of fire that it helps me put out. When I'm not looking at Auvik or any kind of monitoring system, if your switch goes down, you would come up and tell me that you don't have internet. I won't know why you don't have internet until I go in and see that all people don't have internet, and that switch is offline, but Auvik will let me know if there is an outage right away.

I would rate Auvik a nine out of 10. The only thing that keeps it from being a 10 is just the lack of some customization in certain areas. That has really been the main limitation for me. It is not that big a deal, but that would just get it right to a perfect score. I find it very valuable in terms of how quickly you can set something like this up and how much information you can see within your network from a single pane of glass. I still open up my other monitoring tools that are built into the devices, but I don't really view them as much as I view my firewall monitoring in Auvik. 

We're a cloud service provider, so we wanted a solution that would proactively be able to notify us of potential issues. We have four core cloud platforms that we provide. We wanted something that could look at both the network connectivity as well as the infrastructure and storage layers.

As a cloud provider, it's of paramount importance that we're connected to the internet and the cloud in general. If the data collectors ever go offline, there's an alert that's actually sent out to us. Because of the alert tiering, we can have it so that that's treated as an emergency alert and it goes to a different set of critical recipients. We've had it where it's assisted us when we were having issues with one of our IP transit providers, and we were able to use the logs that it provided to demonstrate that we had a definitive issue with the provider and their connectivity. That actually enabled us to push back on the IP transit provider and get quite a substantial claim approved because we were able to demonstrate how unstable the link was.

The other element that it's helped us with is in predicting the future. And another thing that it allows us to do very easily is to track our bandwidth usage that's going in and out of each of the data centers. We've been able to use that information to trend and predict when we need to get upgrades in place. Funny enough, we have an order now where we're increasing our connectivity at one of our data centers tenfold and that's being driven because Auvik's enabled us to understand that we're rapidly approaching our threshold.

The mapping tool does make it easy and convenient to access and get console-level access quickly and easily because of the way it works within Auvik, it embeds the credentials. It's a couple of clicks of the mouse button and you're on a console session. You don't have to go through that rigmarole of what's the IP address, how do I connect, what do I use PuTTy, do I use Telnet? What are the credentials? With Auvik it's very streamlined, click, point, click and you're on.

We've saved on intangible costs. The overhead of managing three different open-source platforms has now completely gone. We just have a SaaS platform, we pay our fee, and it does exactly what it says it will do.

It carries a high value ratio on time-to-value. The interesting thing with the price model is that that value ratio could change. It depends really on if you have a hundred switches, it's going to be a lot more expensive than a client that's only got two large switches. But for us, we find it's very high value for money and good value for money.

The auto-discovery and the mapping are quite nice. We can see how our data centers are connected. That was one of the immediate appeals. 

The change control that's built into it for picking up network device changes and recording is something else that we found to be extremely useful.

It's extremely easy to use, although sometimes some features can be a little bit hidden. You have to know where to look, but generally nine times out of ten, it's very straightforward and quite intuitive.

Network discovery is very good. Like anything that does auto-discovery, it can at times get confused, but it's very easy to select to do an override. If it mis-detects a firewall as a generic network device, it's very easy to correct that on a manual basis. But that happens quite infrequently.

It automatically updates our network topology. We're quite lucky we don't have too many issues. It has given the guys on the desk confidence that they can see very quickly and access any system that we've got monitored. In the early days, we had a hesitancy to know if we could rely on Auvik, but over the last couple of years, it's proven itself time and time again. If it tells us there's an issue, we trust that.

In certain circumstances, it has decreased our mean time to resolution. The bulk of our issues unfortunately tend to be more of an application layer, which Auvik doesn't have visibility into.

Auvik enabled us to consolidate or replace other tools. In the early days, we used to use a SaaS platform called LogicMonitor, which we then reverted from and pulled to an in-house solution. That ultimately became three open-source in-house solutions. It was at the point that we wanted to look at something that could consolidate and give us more intelligence and that's where Auvik came into play.

We use network mapping slightly differently from a lot of MSPs who are more focused on using Auvik to maintain end-user environments. We're looking at it maintaining quite a complex data center environment. The mapping is good, but that can mean that it can get a little bit unwieldily. So having the ability to be able to have more manual control on how the map is organized, would be really useful for us. 

It uses SNMP in its discovery process and how it pulls in data. But today it doesn't have an SNMP trap facility so you can't have your infrastructure devices push alerts into Auvik. And that for us would be a big feature that we would like to see.

The single sign-on piece that they have is really good. That works really well for us. Everything else we're really happy with. They have the chain of control stuff and configuration management piece, which was really nice to discover. We never knew about that. That was one of those things that we fell across and then make use of that quite extensively.

We've been an Auvik customer for approximately two to two and a half years.

We haven't had any issues with availability. They do regular maintenance, but we always get proactively notified of it and it's never caused us an issue.

We use it to monitor two data center sites that have somewhere in the region of about 300 to 500 infrastructure devices in each and we never had a problem with it. My understanding is that if we went out to 20 data centers, it would scale without any issues.

It requires zero maintenance. We would have to do regular patch management with our on-prem solution. It wouldn't take up a huge amount of time, but it was something that had to be scheduled on a monthly or bi-monthly basis.

Technical support is extremely good. Any ticket that we've raised, whether it's a query or we feel that we've hit a bug, has been responded to promptly. They have an extensive knowledge base set of articles, which are invaluable for pointing you in the right direction.

We saw Auvik through one of our partners. We sell to IT resellers, and it was seeing the ease that they could actually access some of the information for a shared client that put us onto doing the evaluation. The one-week evaluation turned into a purchase.

The initial setup was very easy. We downloaded an OVF file, deployed, and connected. We had someone from their tech teams, once we had done the deployments, work with our service desk team and work through doing the initial config.

We had the collectors deployed in under a couple of hours and the configuration for each data center to set things up took us a week for each data center. That was a process that was hindered by us because we had to tweak and tune things to meet our requirements.

Compared to LogicMonitor, my experience was pretty much on par. The SaaS providers tend to have quite a streamlined model. You deploy a data collector, which they have as a single download, and then it starts to consume data into the SaaS platform. For SaaS to SaaS, it was pretty much the same. When you're doing your own on-prem deployment it's vastly more efficient. 

We think the pricing is actually really cool. Only certain network devices make the pricing really cost-effective for us. We can monitor 50 servers and essentially one server or 50 servers has no impact on costs. The one thing I think that's crucial is just to make sure that you understand how many billable network devices you have in your estate before you move forward.

Typically, in our environment, VM hosts, storage arrays, virtual machines, or physical like Windows or Linux machines, all have no impact on cost. The only things that really impact costs are our network switches and our firewalls.

My advice would be to verify that it can cover all the devices that you want it to monitor. For us, it does virtually everything that we need and the odd exception hasn't caused us any major problems. We're still able to do basic monitoring. We just can't sometimes get the level of detail that we want. Go back to the environment and make sure that you understand your network and your network devices so that you can make sure that it's going to give you the value that you want.

The biggest lesson we've learned from Auvik is that we had an assumption that because it talks to the devices and discovers them using SNMP as one of its main mechanisms, we assumed that it would do this SNMP trap feature. We were surprised that it didn't. It hasn't caused us any major issues, but we do welcome the day that that's actually added as a feature.

I would rate it an eight out of ten. Not a ten because of the lack of the SNMP trapping and the fact that it's got a lot of flexibility on the devices it monitors, but there are a couple of holes. It's not a big issue for us.