Auvik Network Management (ANM) Reviews

We used it for network monitoring and network health. We had it deployed at all of our sites. We are an MSP, and we've got about 30 different managed clients. All of them had an Auvik collector at each site to monitor the network for changes or infrastructure health. We have an RMM solution for remote monitoring and management of our workstations and servers, but that tool doesn't monitor network infrastructure. 

Its monitoring and management functions are very easy to use. With some of the other solutions, their built-in database of OID markers isn't great, and you need to manage all of your own MIBs. With a lot of competitors, if a device isn't in its catalog, we need to go and add it to the catalog ourselves, which is a big challenge, whereas Auvik has a phenomenal database behind it, and it is generic, which is another benefit of Auvik. It's not vendor dependent. So, whether you're using Cisco switches, Ubiquiti switches, NetGear switches, TP-Link devices, Hyper-V or VMware, FortiGate firewalls, or Barracuda firewalls, Auvik typically supports them. It has very broad support.

Its integrations are exceptional. The multitenancy in it is also phenomenal. It's very easy to jump from one client to another while also keeping those clients separate. So, if you have someone who is only managing a couple of sites, that's all they can see. They can't see everything else, but someone with a little bit more access can see all of the sites. Being an MSP, we have a lot of different sites that we're accessing. When we have a co-managed environment, a tech for client A can go in and see all the information relating to client A, but they won't be able to see anything for client B.

The time that it has saved is almost impossible to measure. For example, we had a client, and their firewall had failed. We picked up a new firewall. We were going to go set it up, but the last backup that we had on the client's server was from a year and a half prior. It was well out of date, and it was missing a lot of the recent changes. With Auvik, we were able to go in and download the latest backup and restore it instantly. It has saved all those hours that we would have spent troubleshooting or finding missing rules, as well as the management time of having a tech periodically go in and do all of those backups. Because the whole system is automated, it's very hard to measure how much time we saved, but it is a lot of time.

It is the best in class for visualizing the network mapping/topology of the organizations we were monitoring. It is extremely intuitive. One of the big things is everything is all color-coded. So, whether a connection is layer one or layer three, it is very easily highlighted with a blue line versus a gray line. If it is wired versus wireless, there is a solid line versus a dotted line. All of the device types have their own category associated with them. So, if you're looking for a firewall, you just look for the red dot, and you can pick that up pretty easily. If you're looking for a switch, you look for the orange dot. Finding devices on it is very intuitive.

They also had a great feature of being able to collapse and group some of the devices. If you had ten security cameras connected to one switch, rather than having ten little black dots on it, it was able to group them into one item saying security cameras, and you can click on it and expand. It's something that I didn't think about that much when I was using the product because it seemed normal and intuitive. Moving away to a different product that doesn't have the same mapping level or the same features has made the switch a little bit more difficult. You can still get there at the end of the day where you can find the devices, but it is just not as easy.

It was absolutely helpful in reducing repetitive, low-priority tasks through automation. That goes back to things like backups. The fact that it would automatically go through and do the backups, and we didn't need to spend the time to go through and check that was phenomenal. The remote internet connection checks were very useful. ISPs can be very difficult to work with when you're trying to discuss service or packet loss or interruptions. Rather than telling the ISP " We're experiencing this issue," the reports coming out of Auvik gave us a great ability to go to the ISP and say, "Hey, here's some more data. We're dropping packets at such and such rate." Auvik gives you historical benchmarks and reports, and because we already have got the history of it, to troubleshoot, the ISP doesn't have to start gathering reports from that point.

If you have a client that has two locations and a data center, Auvik can group all of those collectors into one client, and you can have a larger view of all three locations and how they interact with each other in one overarching network map, whereas Domotz splits it into three separate locations. Domotz is great in the sense that you get one flat rate per site, but what it won't do is that it won't integrate those sites together. They would be three separate agents that need monitoring within Domotz.

The remote access feature was very useful. If a client's server was offline, we didn't need to VPN in or go to the site to turn on the servers. Auvik gave us the ability to turn on the server remotely without having to go anywhere. It saved us time on that side of things. Over the four years that we were working with it, on average, it has saved us about 150 hours.

Auvik has a phenomenal granular access model where you can even make your own custom role. If you have a co-op student and you want them to only have read access, that's easy to set up. If there is a more experienced person, but they're only allowed certain sites, it is very easy to restrict their access.

Auvik's SSO integration is one of the best I've ever seen. When we were first adopting SSO, Auvik was the first vendor we integrated it with because Auvik was able to get SSO set up where it's one per user or per tech. It's not a big bang migration, and you can have a trial with a couple of techs first, and if it works, roll it out to more.

We had integrated Auvik into ITGlue. When we're onboarding a new client, rather than having to manually add each device into ITGlue, after Auvik has scanned the network and picked up all the devices, we can import all the devices from there. From an accuracy standpoint, being able to import devices saved us from the manual entry and saved us from user errors, such as mistyping a map address or something else.

It definitely reduced the mean time to resolution. The spanning-tree notifications from it were helpful. We've had a couple of instances where a client found a cable that they thought was just loose, and they were being helpful by plugging it in somewhere, which created a loop on the switch. We got to know about it from Auvik. We knew which port it was plugged into and what the solution was to fix it instantly. It reduced our mean time to resolution to about a quarter of the time. We were able to fix things that would've taken an hour to resolve in 10-15 minutes.

Auvik is phenomenal for network monitoring as well as for other functionalities such as remote access or backups. A really cool feature that it has is that it takes a backup of all of the configurations automatically. Auvik periodically, most probably on a daily basis, logs into all the switches and firewalls that you have on-site to see if there is a change, and when there is a change, it does a new backup of the device. It logs changes for you. If you start experiencing some issues, you can go back to those logs to say, "Oh, there is a change made last week, Thursday," and with Auvik, you can just roll back to that snapshot nicely and quickly.

Its UI is really intuitive. It's really easy to get a hold of it. It's very easy for non-technical people to understand. One of our problems with some of the competitors is that they've got a fairly grayscale UI. It sounds very pedantic, but the color scheme of Auvik made identifying which devices were which and how they were connected to each other easy. It was a very useful feature that is underrated. 

Another feature that worked really well for us was the remote access tool. If we needed to log into one of the network devices, we didn't have to jump on a server, workstation, or local device, or connect through a VPN. Auvik was able to give us direct UI access to any device on the network.

It is amazing in keeping device inventories up-to-date. It mostly keeps them up to date as things change. There were a couple of hiccups where a device would get replaced and the mapping would break, and we'd have to go in and fix the mapping. It was with devices that Auvik couldn't fully discover or devices that would change frequently, such as cell phones or other devices on the network that are dynamic and change all the time. The integration would just show up with an IP address and a MAC address. There was no other information in them, which wasn't very helpful. They were the devices that Auvik wasn't able to discover fully. If they had full SNMP or SSH credentials and Auvik knew what the device was and it was matched correctly in Auvik, then Auvik could push it through.

It is not at all cheap. We migrated to Domotz because of its pricing.

We used it for about four years, and we just migrated away from it.

It was probably one of the best ever. I went to school with three other guys. When we graduated, three of them went to work for Auvik support. Full props to the support team. They are phenomenal. I would rate them an eight out of ten. There's always room for improvement. I do wish that they had more open-source pfSense support. There were a couple of things that I was hoping would come out as features but they didn't.

Positive

We didn't have a solution in place. Auvik was our initial solution, but now, we have migrated away from it to Domotz because of pricing. What really triggered it for us was that our firewall of choice is pfSense, which is open source. Auvik, by default, would categorize pfSense as a Linux server, which is essentially what it is. We would then manually categorize it as a firewall. Firewalls are on the list of billable devices for Auvik. However, we weren't being billed for them because Auvik was originally categorizing them as Linux servers. When we were onboarding the product, we mentioned this to our account manager, and we told him that none of our firewalls are being categorized as billable devices. The account manager at the time said that it was a bank error in our favor, and because they were not able to categorize it properly, they were not going to bill us for those devices.

We then costed out our offering with it and had that set with all of our clients. Recently, Auvik was able to fix that bank error, which essentially doubled all of our prices. This makes for a very hard conversation to go to clients and say that we need to double our prices to them because our vendor has doubled our prices. That was a challenge. 

I'm okay if you're going to double our prices, but the support for pfSense, for which they weren't billing us before, is fairly limited. With most of the firewalls, if you have site-to-site VPNs, they show up on the network map as a site-to-site VPN or remote access VPN. Auvik will monitor the usage on those to say, "You have 10 remote access connections, and everything is okay, or you're up to 50 people connecting remotely, and you're starting to get degraded service." All of these additional firewall monitoring features weren't available on pfSense, which was fine because they weren't billing us for it. Now that they wanted to start billing us for these devices, I had asked them if we were going to get support for all of these additional features. They said no because they are not looking to expand their pfSense development. That was frustrating. So, it basically came down to whether we double our costs and pass that onto all of our clients, or whether we look for an alternative, such as Domotz, that doesn't have as many features and is not as pretty in a sense, but it halves our cost. So, we ended up halving our costs instead of doubling them.

As part of onboarding, we got talking with some of the Domotz dev team, and all of the features that were missing have been added as feature requests. We're working with their engineering team to implement some of the features that are not quite there yet.

It was significantly easier than onboarding Domotz. Virtually, every alert or trigger that we could have wanted was built in by default. We didn't have to set up custom alerts, custom triggers, or their base alerting standards. In fact, if anything, it was too much. We had to turn off some of the alerts that were misfiring or not a hundred percent accurate, but there was nothing that we wanted that we couldn't get out of the box.

Its setup was easier. Everything was a lot easier. Even onboarding of new devices was easier. Auvik would identify them a lot easier. Our current solution is a lot more finicky and has more manual elements to it. It's definitely something that Auvik was better at.

Its time-to-value is instant. Before we even onboarded the product, we could see the value in it just from the demo.

Auvik is definitely one of the more expensive platforms. It is not cheap at all. If cost is an issue, Auvik isn't on the table at all, but they do have a fantastic solution for the cost. If budget isn't a concern, they are probably the market leader.

We migrated away from it to a competitor called Domotz because of pricing. Auvik bills per what they call a billable device, which is a firewall, a switch, and a controller. All of those count as billable devices. Domotz, as an alternative, bills per site. It's a flat fee for the whole site. So, whether you've got 3 switches or 10 switches, it's the same cost.

Auvik's premium product has a couple of other features with regard to NetFlow and some of the traffic analysis on that side. They've also got Syslog now in their premium product. However, we found their premium product to be fairly expensive. The whole product is very expensive, even for their standard offering. So, to bump up to premium, it's a lot more expensive. We trialed it for a bit. It was very useful but not worth the extra cost.

In terms of comparing Auvik’s cloud-based solution versus on-prem network monitoring solutions, it is a tricky balance because while the Auvik database and the backend are all cloud-based, you still have an on-premise collector doing some of the management for you. The management of it is cloud-based, but there is an on-premise component to it. There are some alternatives, such as PRTG or Zabbix. They're all on-premise alternatives, but they are very much a pain to manage, particularly when you have multiple sites and multiple clients. Having the backend cloud-based is very useful. However, that's a feature that they share with Domotz. Domotz is cloud-based in the same way.

Overall, I'd give Auvik a seven out of ten. Tech-wise, it's a ten, but its pricing is a very big barrier to adoption.

I originally purchased Auvik to assist in troubleshooting network issues on the local area network and wide area network. We were having some slowness issues, but they were only in certain segments of the network. I had no tools on-site to help me find where the problem was.

I was able to realize the benefits of Auvik Network Management immediately. I knew I was having network problems. I got it up and running in a day, and I was immediately able to seewhere my issues were.

It does not cover everything I need, but a part of that is because I have not implemented Auvik 100%. I got Auvik up and running far enough to do my troubleshooting, and I then left it while I worked on other major projects. So I still have a lot to learn. I am taking all their classes, and I learn more in every class. My frequent comment is that it is like drinking from a fire hose, but

Auvik is putting the classes online so I can then go back and run it again, open up my Auvik and go through the items covered in class. Going through those training sessions has helped me configure Auvik.

I am 90% positive and 10% negative about its user interface. Most of the time, it is very intuitive, and I can find what I am looking for, but sometimes, it is a struggle. What is awesome is that during the training sessions, the instructors always end with Q&A, and you can ask any question. You do not have to ask a question just about what the training was on. They answer your question, and they always lead me to where I need to be on the interface.

The network map is currently giving me partial visibility. I do not have visibility to my portal to the Internet, but that is partly because I do not have it configured and partly because I am not sure if I want to allow that password access to my firewall.

The network map along with the dashboard gives a real-time picture of your network, but my network map is still messy. I am not sure if it is because it does not have all the permissions yet to do everything it wants to. About half of my devices are stranded in the middle of nowhere, and the other half are connected through multiple connections. A part of that is that Auvik does not have the Ubiquiti stuff down yet, so they do not really know which devices are talking to each other, but it is enough. Especially with the connectors, I can see what device is talking and figure out where my bottlenecks are. It is nowhere near perfect. When they give their training sessions, their network map is beautiful. Mine is pretty chaotic.

Auvik Network Management decreased the mean time to resolution for the initial problem I had.

So far, I have used it only for one initial problem. It helped with that problem.

I like the way that Auvik auto-configures itself to do the mapping. I wish it was a little more accurate, but as soon as you start getting your authentication correct for the different protocols that Auvik uses for discovery, it starts putting together your map for you.

It is not backing up my configurations on much of my network equipment. For some reason, it struggles with Ubiquiti equipment, and it is a known issue. They have a ticket open for it. Some of the issue could be the way Ubiquiti handles authentication. Ubiquiti handles authentication differently. Auvik expects to be able to log in to a device and then go into Config mode, whereas you are already in Config mode when you log into a Ubiquiti device. There is no additional authentication required, so they are having difficulties getting their scripts working on Ubiquiti.

The piece that I would like to see the most is getting those configs backed up. That is my chief complaint. If Auvik can get that work, they would be perfect.

I have been using Auvik Network Management for about seven months.

I contacted Auvik about how often they were down, and their response was they had not been down. They have just been doing maintenance that temporarily takes the system away, so it is not 100% stable yet. It does seem to go down a couple of times a month, but it is never down for long. Usually, they are fixed quite quickly.

We have just a single site with a couple hundred devices. I know that they have very large customers' data centers, so I am assuming that Auvik scales well. 

I am the sole IT person for this facility. It is a school for the intellectually disabled. We are a live-in facility 24/7 and 365 days. I have 300 students and about a hundred staff. I provide support for over an 850-acre campus.

We have just a single site with a couple hundred devices. I know that they have very large customers' data centers, so I am assuming that Auvik scales well. 

I am the sole IT person for this facility. It is a school for the intellectually disabled. We are a live-in facility 24/7 and 365 days. I have 300 students and about a hundred staff. I provide support for over an 850-acre campus.

Positive

I used PRTG. PRTG proved to be too complicated for one person to set up and use. It took too much care in feeding. Auvik is definitely better.

It is a hybrid setup. I have a collector on-site, but all the actual work is done in the cloud.

Its deployment was pretty easy. 

The only additional maintenance is if any equipment comes online and it does not recognize the equipment, you have to go into Discovery and give it the appropriate username and password.

That is the only maintenance required.

I deployed it myself.

The school I work for was founded in 1893 by a private family. It is still run by that same family, and that family dislikes the subscription model. They much prefer to buy equipment and own it, so trying to convince management to use a subscription model for a piece of software was pretty difficult. However, I was able to get Auvik to present it more as a multi-year contract instead of a subscription model. It is something their sales can do for other customers, but I do not think it is something they advertise.

For the size of our school, it is expensive, but I understand the reason behind the pricing. All my servers in the network are monitored by Auvik at no charge. We are only paying for network devices, so I pay for switches, access points, and firewalls, but I do not pay for all my user PCs and MACs, and my servers, which are my critical devices.

You need to understand the permissions required by your different pieces of hardware, especiallyfor different hardware types such as Windows, VMware, your networking hardware, and your Internet interface. You need to have all the permissions ready so that you can set up your Discovery. The hardest thing to get running on Auvik is getting the Discovery set up properly.

Overall, I would rate Auvik Network Management an eight out of ten.

We primarily use Auvik for managing and monitoring devices, including network devices, access points, and printers. We utilize Auvik's alerts to notify us of offline devices or any unusual behavior it detects, such as high interface utilization or low disk space. Additionally, we employ Auvik to automate the backup of our network switches.

We implemented Auvik because we lacked visibility into potential network issues, such as switch or access point utilization. While I have a wireless controller that provides some insights, Auvik unifies this information into a single, comprehensive view. This centralized visibility enables us to proactively identify and address network problems.

Auvik is deployed in a hybrid model because we have an on-prem collector that sends the information to the cloud.

Auvik is intuitive.

The ease of use provides me with peace of mind. It eliminates the need for me to independently explore certain aspects.

It has significantly reduced our mean time to resolution. For one particular issue, it saved me an estimated 10 to 20 hours at a minimum. Additionally, it has enabled me to respond to a handful of other issues one to two hours quicker.

We have been enabled to dedicate less time to the setup and maintenance of the solution and reduce the time required for issue resolution.

I have utilized configuration backups to replace equipment. I have employed alerting mechanisms to correlate user concerns with known alerts, enabling me to grasp the situation promptly. I can inform users of the need to replace toner cartridges or alert them to power outages caused by switch failures. Overall, this process aids in identifying the expected network status.

One of the primary advantages we observed with Auvik was the immediate availability of switch backups. This enabled me to seamlessly track configuration changes between backups. This was particularly valuable during the initial months when I was implementing numerous network switch installations. Auvik's ability to quickly adapt and incorporate new information is impressive. The only aspect that might require a time investment is understanding the normalcy of specific bandwidth or statistical data. However, this is not a learning process but rather a data-collection exercise.

The monitoring and backup are the most valuable features.

The Auvik network map and dashboard are not reliable enough to provide a real-time view of our network.

Metrics should be reported for individual devices rather than IP addresses.

I believe it would be highly beneficial to display the paths over which each VLAN is accessible on the network map.

I have been using Auvik for almost six months.

The stability of Auvik is excellent. The only time it goes down is when they announce it beforehand for maintenance.

Auvik should be extremely scalable. I have not seen any issues in that regard.

The technical support response time is slow. With 20 years in the service industry and nearly 30 in IT, I find that while the technical support representatives are polite, I sometimes feel more knowledgeable than they are. It's frustrating explaining my concerns to level one support only to have them escalate the issue to an engineer, leaving me in a communication limbo for potentially weeks.

Neutral

The initial deployment was uncomplicated. While Auvik itself was very easy to use, it requires SNMP to be configured correctly on all devices. This is the time-consuming aspect of the process. If SNMP is already configured on all devices and we have the necessary information, the setup can be quite straightforward and likely take less than an hour.

I was the only one from our organization involved in the deployment.

We used Auvik for the implementation.

Initially, I was an enthusiastic advocate for this product. I told many people about it and was very excited about its potential. However, once I started using it regularly, my enthusiasm waned somewhat. While the product does excel in certain areas, the recurring cost can be a deterrent. Overall, I believe the product is fairly priced, but I would consider it a better value if it were improved in certain areas.

If an alternative monitoring solution is not available, Auvik will take care of it. While we pay our MSP to monitor the servers, Auvik provides me with the essential information I need to stay informed about their status at no charge.

I would rate Auvik seven out of ten.

Auvik may require minor maintenance after adding or correcting connections, as some of these changes may not be displayed correctly.

Ensure the SNMP configuration is accurate, as Auvik relies heavily on it for network monitoring and management. Additionally, use managed switches instead of unmanaged switches to avoid potential network disruptions and complications.

I'm a technical team lead managing other engineers and specialists for several clients. I utilize Auvik for strategic discussions, escalations, and support tickets. I'm on the backend trying to coordinate responses to outages, feature requests, etc. 

We use multiple applications to manage our network. Auvik is our network mapping and discovery tool that creates alerts in our ticketing system. We use ConnectWise Automate and that suite of products for ticketing. It's not like Auvik is a ticketing help desk system with remote control, but it can do just about everything from a monitoring standpoint. We still use AppNeta for board mirroring or finding latency in network traffic.

Auvik is a total package for network discovery that completely meets our needs as a company. I don't see us leaving Auvik for some other network discovery tool. It's a one-stop shop where we can dive into each of our client's networks, and we have quite a few. I don't know precisely how many we have. It's fewer than a hundred, but it's too many to do LAN diagrams in Visio. 

The solution has reduced repetitive low-priority tasks because it collects the SNMP information for us and alerts us when servers go offline. We can see connectivity in the network from a bird's eye view without the need to dive into the firewalls and switches. Auvik saves us from having to create manual diagrams, and I can export all the data about a client's network, so I don't have to gather all of that myself.

Given our number of clients, we would probably need another full-time engineer if someone had to keep track of all of this on their own. It's roughly equivalent to a human working full-time for an entire year. That's one less person we need for all that, and Auvik reduces human error. 

The visibility Auvik provides is critical because it's part of our onboarding process, giving us a high-level overview so long as the client doesn't change the SNMP default values. We can immediately see what a new client is working with as soon as we get off again into their network.

Auvik has improved the team's availability by about 75 percent. Before Auvik, we used a different tool to scan, but it provided only a one-time snapshot of the network, whereas Auvik provides mapping in real-time. 

It's probably one of the first tools we introduce to new hires in our network operations center. Auvik is intuitive and offers hints. You can type a vendor name or an IP, and it's immediately accessible at a high level. Of course, there's depth to the product that takes time to develop. Junior engineers can quickly get a look at it, start learning how SNMP works, or configure it on devices and watch them appear in Auvik.

We use Auvik when we're doing strategic planning for clients. It helps us find servers, hosts switches, correct serial numbers, etc., so we can do warranty lookups and that sort of thing. It's important. We primarily use it for information gathering to see a visual network diagram mapping and get tickets.

It's hard to say that one feature is my favorite, but I like Auvik's ability to map networks using SNMP. It maps the network, so I can look at all the devices and set them to provide alerts or automatically create tickets when outages occur. If clients need it, I can export all of the data into an Excel spreadsheet.

The monitoring and management functions are easy to use. The network visualization is also intuitive. Ease of use is crucial because many of our help desk specialists and entry-level people need to navigate the solution, so it's vital to have simplicity in standard high-level searching. A single integrated platform is essential to stay in line with our best practices.

The search could be slightly more intelligent. If I type in "Dell" and put an extra "L," Auvik doesn't give a suggestion, "Did you mean 'Dell?'" I have to fix that. That's a minor thing.

Also, if I select a specific device and apply it as a search filter, it shows me the device, and I have to click on it to see it at the bottom of the page. Otherwise, it just stays on the discovery. When I close the device, it remains on the switch displaying the diagram. I have to click the home dashboard to get back to the way it was.

When I remove the filter, it should take me back to the home dashboard. After I add a filter, select a device, and apply it as a search filter, I think it should pop up if there's only one. When there's only one device in the filter, I find it somewhat annoying to need to click it to dive into that device. If I remove the filter, I would prefer it return to the home dashboard. It's a minor irritation at times.

I've used Auvik for more than five years, close to eight. 

Auvik is solid. I have never experienced an outage. Auvik has downtime, but they provide notice well in advance. The maintenance window tends to be at times that won't impact me. The most recent maintenance window was on Dec. 3 at 7:00 AM Eastern, which is 4:00 AM Pacific, so it didn't affect me at all.

I don't see a limitation to the scalability.

Before the company adopted Auvik, I used Visio to create my online diagrams by hand.

I wasn't involved in the initial setup, but deploying the collectors is easy. Another person handles the onboarding process, but the network maps are populated within a day or so. I've never heard anyone say, "Hey, it's taking a long time for Auvik to get going." They say Auvik is up, and I see the map is there. 

I rate Auvik 10 out of 10.

We mainly needed a tool for managing or monitoring our firewalls and switches. We do have other tools for general server environment monitoring and applications monitoring, but they are not as good for managing and monitoring firewalls and switches. We specifically needed monitoring and management of firewalls and switches for our data center environment.

It provided the ability to track down the changes in the firewall and the ability to have centralized visibility into our networking stack. We are able to compare and correlate functions from one environment with another environment, which is helpful when we upgrade the code or the framework in one location. We can compare how the stats were previously, and we get to know whether the new code is doing anything funky or if we are seeing any issues. It allows us to compare sizes that are running on the older code and sizes that are running on a newer code. We can see if there is any difference in the CPU usage, RAM usage, or the utilization of the firewalls themselves.

It's a single pane of view. There is a single dashboard, and you can add multiple sites and multiple users to it. You install collectors in different areas, but the management is from a single location. Everything is cloud-based. So, you can access and do monitoring from pretty much anywhere. The beauty of it is that if you have multiple physical locations across the continent, you can see the networking stack on one single page. This single integrated platform is very important for us. The most important factor for us was that this platform is cloud-based. If we were hosting it in a single physical location, it would have been hard to be accessible by other locations. Having it in the cloud and being able to see everything in a centralized location was super important for us because in the case of the old or other tools that we had in the past, or we still have, we need to log into a different tool or different console to see the information, and it's hard to correlate all of them in a single location. Auvik gives that ability. We can compare the states and the information from a firewall located in the east of the US and a firewall located in the west of the US, which is super helpful.

It is nice to be able to visualize the network mapping/topology for the organization. You don't have to do anything. You add the subnets and the VLANs you want to be scanned. As long as the collector can access those subnets, it is done fairly quickly. It depends on how complex your network is, but it can take less than 30 minutes to map everything and give you a visualization, which is pretty nice. Otherwise, it could take you hours to stay up-to-date with the charts of your networking topology because the topology changes from time to time. With Auvik, you can see every node, every switch, and every firewall. You can see how they are connected. You can visually see how your network is and what you have. The best part is that it adjusts on the fly. If I add a new switch, the topology would adjust, and the new switch will be there. If I take out a switch or create a new branch, it will automatically show that. It's really nice and easy for the day-to-day understanding of where you are, but it's also very important when you have a new network admin, and you need to get them up to the speed of your network. In the past, we had to pull out various diagrams and explain what we have and then figure out whether all the diagrams were up-to-date, whereas now, we can just show the dashboard, and they would understand that. I would rate it a 10 out of 10 in terms of the overall intuitiveness of the network visualization. It's really intuitive. From what I was able to see, everything was correct. It's not that you get raw data and some visualization and then you need to work with it or adjust it. It connects everything. From what I was able to see, everything was pretty correct in the diagrams.

It has helped reduce repetitive, low-priority tasks through automation. Previously, we were doing daily backups of the firewalls, but now, we don't have to do that part. That has been a help. The automation of the backups was helpful. 

It has significantly improved the visibility into the networking topology. It can see the access points, and it can see pretty much everything on the network. It can detect servers and physical hardware as well. It has significantly improved our visibility. This visibility is not the most important aspect, but it's definitely important and significant to have this visibility and know what you have in the topology.

It keeps device inventories up-to-date. We can quickly search and find out the devices we have or check what we have. That part has been really helpful. Instead of tracking in an Excel spreadsheet, we can search the inventory in Auvik.

It has definitely saved time to do other tasks. Some of the daily tasks that we had to do are now done by Auvik. With Auvik, our team spends less time checking things, getting dashboards, and pulling up reports.

We have multiple applications and tools to manage and monitor various aspects of the networks. Auvik has saved us a few hours a week. When you have three or four different tools, you need to take information from each of those tools and then get some insights out. With Auvik, we log into a single location, and we get all the information. It has been time-saving for sure.

Few of the features are valuable. One feature that is the most valuable for me is that after we added all of our firewalls, every time we make any configuration change in the firewall, it creates a backup and retains the change history for months. We can see and find out when a change was done and what was the change. The best part is that if we want to compare the current config with the config from two weeks ago, the tool pulls up both config files and tells us what the difference is. If something is not working today, instead of asking around who made the change, what was changed, and how things were two weeks ago when everything was working, we can just pull both configs, check them out, and know what exactly the problem is and investigate.

Auvik is a cloud-based solution, and it definitely has advantages over on-prem network monitoring solutions. We don't have to manage anything on-prem, and we don't have to patch the backend. We don't have to allocate resources for the management console to work, and it's accessible from anywhere. We don't have to back up the virtual machine or the appliance because everything is managed by Auvik. We really like that part. You definitely need internet connectivity to send all the logs and data to Auvik. If your internet goes down, then technically, you don't have visibility at that time, but then, you likely have a bigger problem than being able to get the data.

It takes significantly less time and effort to set up and maintain Auvik versus our previous solutions. With the previous solutions, we needed to get somebody trained. Somebody had to go and watch tons of videos to understand how to deploy the solution and how to properly install and configure it. With Auvik, we just provide the executables to somebody, and they just install it. We then go to the console and the data starts to come there. It's way easier and faster to set it up.

They can improve its monitoring capabilities for the physical servers or operating systems. At the moment, they do have some visibility. Even though you don't buy Auvik for monitoring your servers, and it is more for network monitoring, it would be nice if they can do end-to-end monitoring so that you don't have to use a different tool for operating system monitoring. You can get all the information from Auvik.

I have been using Auvik for about three months.

It has been very stable so far. I don't see any issues. I'm not concerned about its stability.

It can scale. I don't see that as an issue.

We have various firewalls and switches in HA. We have various models and vendors. We have a three-layer topology. We have a core layer, a distribution layer, and an access layer. All that is visible and monitored from Auvik.

Their technical support has been good. They come up with solutions, and they are there to help. I'm happy with the experience so far. I would rate them an eight out of 10.

Positive

We used PRTG, and we used Nagios. We used these two recently. They were more for monitoring. They didn't have the capabilities of management. They weren't keeping backups, and they weren't alerting us where there was a new firmware update. They also did not have the topology visualization.

Both of them were on-prem solutions. So, we had to have a system or VM to install them. We installed PRTG on Windows. We needed a dedicated box to run it. They weren't cloud-based, and they weren't highly available.

I deployed it, and I worked with my network engineers to set it up properly. I started the initial deployment or initial installation of the collectors, and then my team took over. I worked with them to deploy it in multiple locations. It was straightforward and pretty easy to deploy. You need to do some configurations to add everything, but the initial configuration is straightforward.

We just downloaded the out-of-the-box solution and just clicked on next, next, and next. We haven't done any customization. It took about 30 minutes initially because I added a few subnets. It took 20 to 30 minutes to get the diagram. Initially, you get some data depending on your network. We have a fairly large network, so it took about 30 minutes. It is awesome to get that information in 30 minutes.

It was pretty straightforward and easy to use for firewalls. You set up a connection to the firewall, and then everything pretty much works on its own. Some tools require you to learn for weeks before you figure out how to deploy. Auvik, in that regard, is pretty easy. We had a little bit of a challenge adding the switches just because we have specific switches, and they communicate with the firewall on a specific protocol. There was an API or a way to add them up, but we just didn't know how to add them up out of the box. Auvik's support was able to help us out fairly quickly, and overall, it was an easy and smooth deployment.

We did it ourselves. I don't see a need for an integrator to do it because it's straightforward.

It doesn't require any day-to-day maintenance from our side. Everything is managed by Auvik. They run the updates and the patches. The only thing that you need to do is that when you add a new device, you need to provide a new password, or if you change the password, you need to update that in Auvik. Other than that, there is no maintenance.

I would like it to be more cost-effective or affordable. It's not the most expensive one, but it's also not the cheapest solution out there. You pay month to month. It is what it is. It is not for everyone, but it depends on what you're looking for in your budget.

To someone comparing network monitoring solutions but concerned about pricing, I would say that Auvik is not the cheapest solution out there. You pay per device you monitor, but there is value in it. If you monitor the key systems and components, then you can make it cost-effective. If you want to monitor every single switch in your environment, it certainly won't be a cheap solution. You need to evaluate what you need to monitor. Do you need to have every switch? You can have maybe the top-tier switches and get all the information from those. You don't necessarily need to have every switch monitored because it doesn't really distinguish. You pay the same price whether you are monitoring your core switch or your access switch. To make it more cost-effective, you need to pick and choose what you want to monitor.

We've evaluated FortiMonitor from Fortinet, but it wasn't a good fit for us. We also evaluated LiveAction. That was also not a good fit for us.

I would advise giving it a try in the trial period, adding all the devices you have on the network, and seeing what value you are getting. I would also advise assessing what you need to monitor and what you don't need to monitor because you pay per monitored device.

I would rate it a nine out of ten.

We use Auvik to map out networks and to view device health, meaning not just if it's up or down but also if there are any system-generated errors that can be listed via Simple Network Management Protocol (SNMP).

It saves me from having to log into each device through whatever login they may have available to them. It's a single interface for the devices.

It has greatly increased our speed. We don't have to check individual device-specific interfaces for monitoring. It also handles real-time monitoring, as opposed to a daily or hourly check. In some cases, it also allows us to find a device that's in trouble and directly connect to it from the interface. It's a huge time saver, and it does save us a fair amount of leg work.

It has helped to reduce repetitive, low-priority tasks through automation, such as checking on a device and opening and closing tickets for the devices that are in.

We now have a lot more visibility into the networks than we did before. This visibility is very important for our IT teams. The IT team would have a fairly difficult job checking all these different devices manually. In some cases, the work just wouldn't get done if it wasn't being done automatically.

A simple site view with the associated devices populating as things to add to or remove from the network is valuable. It's also nice to have it integrated with our ticketing system to create tickets in certain cases for devices that go down or have some high-level alerts, such as high CPU or overtemperature.

It's pretty easy to use its monitoring and management functions. There's a wizard that's involved when you first start it up and then you can pick. The initial network sets itself up and then you can add networks if they are available to the devices being monitored. Its ease of use is fairly important. There are some other monitoring tools that we have available to us, but they're agent-based. We can't load an agent on a switch or a router or something like that. We need some sort of SNMP interface to detect those errors. Otherwise, they would go unnoticed.

It's pretty intuitive. As soon as you pull up the site, the map comes right up. You can expand or contract different device types. In many cases, it will attempt to interrogate the device and find out what device type it is, but sometimes, you may have to set it yourself.

For the most part, it's great for visualizing the network mapping/topology for our organization. However, when complex VLAN networks are involved, sometimes, the picture can get a little cloudy. It would definitely be nice if there was some way of choosing a VLAN to view or something like that. They should definitely improve the handling of multiple networks and VLANs. I do know that the information has been gathered, and I know it's possible to give different looks. There could be a layered approach to the VLANs where you can take the default VLAN or you can toggle a switch and show, for example, a security camera VLAN or a voice-over IP VLAN. It would be nice to be able to have it pull up the information relevant to a particular network. 

The GUI map view could potentially be adjusted so that we can manipulate it without necessarily having it resize every time we adjust the screen. There should be a single focused view. Currently, it resizes every time I move this bar that has the information underneath it. Sometimes, that's after me zooming in on a particular piece, which makes it difficult to find my place again.

I have been using Auvik for at least a year. I'm a senior engineer for an MSP, and I use the Auvik system on a daily basis. 

Auvik's stability is great. They do run regular maintenance, and they always have an announcement about the maintenance ahead of time.

Its scalability is great. You're not limited to a number of devices, etc. Your only limitation is whether or not it can see the networks that you're trying to track. Because this is a cloud-based solution, it wouldn't be good for somebody who has an isolated network or something that's not on the internet. Other than that, whether you've got 5 workstations on the small network with 1 switch and 1 router, or if you've got 6 switches, 30 telephones, 7 printers, and 18 access points, it shows them all irrespective of whether it's a big one or a small one. The pricing on it is based on the devices. A small network is going to have a smaller cost than a larger organization.

It's deployed across multiple clients that we have. Each one of our nine different sites is a different client. Of those clients, none of them has two sites. So, it's not necessary that we have multiple site issues. We have nine sites and nine clients.

Normally, we have been just speaking to the sales team. So, contacting the sales rep is something that we've done, but there is a knowledge base that is fairly fantastic. They have it set up for a bunch of different device types from different manufacturers. You can see how to configure them so that they're sending the right information to Auvik. Each one of them gives step-by-step guides on how to integrate that device with Auvik.

There is obviously technical support, but I have not had to use it, which is great. The support is available right from the interface. You just go to the website, and they give you the phone number, and there you go. It would be fairly easy. You can do it through a message or through their phone number.

Their sales support is fairly techy. They are not just managers. They know their devices and their software. I would rate the support provided by their sales engineers at least an eight out of ten. They were easily able to answer any of my questions. However, not a whole lot of questions came up because the product pretty much runs itself. There are how-to guides on adding the capabilities of new devices. If there's a router, a firewall, or something else, there are instructions on how to configure it to connect to Auvik.

Positive

I have, but they belonged to certain ticketing systems, such as HP OpenView, etc. HP OpenView comes into play if you only have one network to manage. Currently, I've got nine different networks under Auvik, and for me, it's a switch between them. It's as simple as just dropping down a box and looking at the next one. However, because it's integrated with my ticketing API, I don't necessarily have to drill down into it. I'll receive tickets for certain devices that are having issues.

It was very straightforward. There was some hand-holding that they needed to do for us in order to integrate it with our ticketing system, but so far, setting up Auvik, starting a new site, and having that site inventoried and discovered has been mostly wizard-based. So, it's not difficult. You probably don't even need to be familiar with the technology to set it up.

We implemented it out of the box, but there are checkpoints where you authorize networks to be scanned. There is a stop there, but it's not too big a deal.

It probably took about two hours to set everything up for the first client, and then after that, each additional client would be about half an hour.

Auvik had a sales team that assisted us in the initial setup. In terms of the staff involved, I and the owner of my franchise company were there. He didn't need to be there. He just wanted to be there.

It doesn't require any maintenance from our side.

It saves me time on a daily basis. So, there's a great time-to-value. A fair amount of my time has been spared using this tool.

Its licensing is very fair. The devices that stand to gain the most benefit from this product are the ones that are billed. In the case of routers, switches, and firewalls, I won't necessarily have the ability to put a management agent on them to gather errors and activity logs. This type of solution is a requirement for me to properly monitor and manage these devices. The devices that aren't being billed are workstation servers, etc. For those devices, I can put agents on them to monitor their health. It has a fair billing structure. Additionally, the billing seems to only happen for devices that I have linked to my ticketing API, in such a way that I could stand a benefit from it.

To someone comparing network monitoring solutions but concerned about pricing, I would say that when comparing with other applications, they need to check if the other solutions are able to integrate with their ticketing system APIs. They also need to check how many device types they expect to log into during any one of their days, in order to get a true look at the device health of the networks that they have under them.

I did know of one other option available, but we did not evaluate or entertain any others before we went with Auvik. It was presented to us as a trial, and we were simply impressed.

The best advice is to make sure that all the devices that you want to come up in the map view have been properly configured to send their SNMP data to the collector.

Auvik helps to keep device inventory up to date, but typically, we do device inventory in a different way. It's nice to be able to validate the inventory, but in most cases, inventories are handled by different tasks. Auvik is invaluable for taking the initial inventory for a new client, but normally, we would go with a different inventory process, and we would use this to validate that going forward. It helps with the building of the inventory, and it helps to validate the inventory as it progresses.

I would rate Auvik at least an eight out of ten.

We use it for our clients that have managed network services. We monitor their networks to see if there are any anomalies or unknown devices, and we use it for troubleshooting as needed.

One of the benefits is the insights into the network. We had one client that was having tons of issues. We put Auvik on there and we were able to isolate the problem to one device, remove it, and everything is now working well.

It has helped with visibility into remote and distributed networks, globally. For those clients that pay for the service, it allows us to see their networks, see what's going on, and sometimes even see an issue before the client knows and calls us, and that is what we want.

We have also seen a reduction in mean time to resolution, of about 10 to 20 percent, depending on what the issue is.

I like the traffic insights. That really helps to see what's using your bandwidth.

The monitoring and management functions, while there is a little bit of a learning curve, are pretty easy. Once you get it, it's straightforward and easy to go forward with. That's very important because we don't have time to sit around and try to figure out how to use it, looking at tutorials. It's pretty intuitive and their support is really great too if we have any issues.

And the fact that it provides a single, integrated platform for our organization is important as well. Having 50 different accounts to log into would make things difficult at times.

The overall intuitiveness of the network visualization is great. It makes it easy to see everything and easy to follow and pinpoint what's going on.

The visualization of network mapping is good. The only complaint would be that VLANs don't necessarily show up as a regular LAN does. They do show up, but there is some manual tuning you have to do to make that look perfect. That's kind of the nature of how VLANs work, so I don't think there's anything they can really do to help make that better. Still, it does at least pick up devices that are on there, and tries to connect it all, but it doesn't always do a good job.

Also, it doesn't help keep device inventories up to date. It doesn't have any updating features.

It has been three years since I started using Auvik.

It's reliable. We haven't had any issues with it. We haven't had any downtime because the server wasn't available, or anything like that. It's definitely worth it.

It seems to scale really well. When we first started, we just had three clients in there. Now we have it on all 35 of our clients, and some of them have multiple sites. They're not all fully configured, but at least we have the agent on them and we're getting data already. I just need to go into each one and set up the SSH and SNMP settings, but that's no big deal.

It's deployed into our managed network clients who have anywhere from three workstations all the way up to over 300 devices on the multiple VLANs.

Their technical support is a 10 out of 10. They have direct support within the platform via a chat and they'll walk you through anything and give you the guidance you need. And their email support is great as well, if you have to escalate something. They'll even do a Zoom call with you if they're not able to resolve it by email or chat. They don't leave you hanging.

Positive

We didn't use any solution previously. We just used an ad hoc network scan to try to find issues, but that doesn't really give you a great view of everything.

I'm the one who does the deployments. The setup is straightforward. It's complex in the sense that you have to connect each device and configure its SNMP or SSH settings, but it's pretty straightforward overall.

Depending on the network, within 30 seconds to two minutes, max, the network mapping starts to populate after implementing the collector. It's pretty quick.

It doesn't require much maintenance. Once you get everything set up, unless you introduce new devices, you don't really have to mess with anything.

We did our initial implementation with the Auvik trainer. He helped us onboard clients and gave us training. Our experience with him was good. He was really knowledgeable and helped us out as we needed it.

Initially, it was me and our CEO involved in the implementation, but he passed it off to me after the first couple. And of course, we have had Auvik's help with it as well.

Time-to-value from Auvik has been the troubleshooting of that one client I mentioned, just by itself. We spent countless hours onsite trying to figure out what was going on, doing our own tests with freeware, but we weren't able to isolate the issue until we installed Auvik. If we had done that from day one, it would have taken three hours for the setup, instead of that ticket taking 22 hours of work. It's a big benefit.

Auvik's pretty good in terms of pricing. It can get pricey if you have multiple managed devices, but if it's just a simple network with only one or two firewall walls and smart switches, it's reasonable.

The one client that we had issues with has 15 managed devices. That client is pretty expensive, but it's worth it.

Our eyes were set on Auvik, based on reviews from peers.

It's not really replacing any tasks. Rather, it's a good tool to see if the network is down. We have others that do the same thing, but Auvik is more for investigating issues.

My advice is to take your time. Make sure that the credentials are correct when you input them. Go through their guide on setting up WMI for Windows workstations to get better results. Just don't rush it and get good data.

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.