Director of Managed Services at Custom Systems
Real User
Has user-friendly monitoring and management functions, and reduces troubleshooting time
Pros and Cons
  • "The most valuable feature is that it will back up the configuration and that it will keep multiple copies of it. If a change is made to the configuration by someone else in my company, for example, and something goes wrong, I can bring up the previous configuration and the current configuration, and it will show me exactly what's different. It greatly reduces the time it would take to troubleshoot because I can pinpoint exactly what was done. I can then either change whatever it may have been or roll back the change."
  • "The biggest area for improvement is the speed of the website because it's not something we host. Each of our clients hosts an agent that gathers the logs and pushes it up. The website can be slow to click around in or click through."

What is our primary use case?

We use Auvik mainly to monitor switches and firewalls but also use it to monitor VMware. We also utilize the extra monitoring that Auvik provides for desktops.

How has it helped my organization?

Auvik gives us better insight into devices and helps us troubleshoot better because we can compare configurations. Auvik also gives us better and faster alerts on devices. If a client has a switch that's down, we tend to be able to find out and react to it before the client has to reach out to us, which is always a great benefit.

When internet connections are down, we can find out quickly, especially after hours or over the weekend, and can make sure that everything is working before the staff come back in to work for the day. We can make sure that everything is back up and running. The number of alerts and the granularity of the alerts mean that we can pinpoint on a particular switch the specific port that is causing the issue.

The other great aspect that has come in handy a few times for us is traffic monitoring. We can see if someone's internet connection is running slowly and see exactly where the traffic is going. We can zero in on what the traffic is, which user is using the traffic, and what switch it's going through. The information that Auvik gives us helps us troubleshoot, which is a lot of what we do. Auvik has helped us make sure that the company continues to run efficiently.

What is most valuable?

The most valuable feature is that it will back up the configuration and it will keep multiple copies of it. If a change is made to the configuration by someone else in my company, for example, and something goes wrong, I can bring up the previous configuration and the current configuration, and it will show me exactly what's different. It greatly reduces the time it would take to troubleshoot because I can pinpoint exactly what was done. I can then either change whatever it may have been or roll back the change.

Auvik's monitoring and management functions are easy to use. For certain devices, switches, or routers, you have to make sure that SNMP monitoring is enabled on the device. Once it's enabled, Auvik is extremely simple to use. I've worked with other monitoring software in the past, and it has taken weeks to configure all of the alerts and get everything monitoring the way we want it to. With Auvik, once the device is capable of pushing the logs, it's simple. Auvik also has many out-of-the-box notifications that are pre-built and that automatically monitor. Setting up a switch or a router is simple and quick.

Auvik provides a single integrated platform and two different ways to install it. If you have VMware, you can put an appliance right into your VMware for monitoring. If you have a Windows server, you can install the agent, and it crawls the network and finds everything easily. Having a single integrated platform is important for our organization because we don't want to have 10 different programs or applications and have to go through each one to differentiate which one is using what and where. We want to be able to have one central location where we can find everything we need.

Before we switched to Auvik, we used three or four different applications to monitor different functions. Some were designed to monitor VMware, some were for desktops, and some were for switches and firewalls. Using multiple products was a pain, and none of them actually had as many features as Auvik does now. We have saved quite a bit of time by switching to Auvik. We have central alerts, and we have functions pre-built now that we truly understand what it takes to get a new client configured. We just added a client in the past few weeks, and all we had to do was throw the agent on a machine, let it figure everything out, and put in the passwords for the devices into Auvik. That was it, and Auvik took care of everything else. It definitely saves a lot of time, especially in terms of the configuration of the monitoring.

We can visualize the network mapping/topology of our organization with Auvik. It's really nice that it breaks it all out. When we have clients that have 40 or 50 switches across multiple buildings, the map will be very large. In these cases, it's very difficult to zero in on the map; however, we will still be able to pinpoint which devices are connected to which switch. If a particular switch is down or having issues, we'll know exactly which segment of the company is going to be affected by that. We'll know if there are network loops because certain things are interconnected.

The ability to not have to try to manually figure out where everything is and just be able to pull up a map and identify a switch that is connected to it is great. It makes creating a network map for new clients much simpler. If we go into a new client, we can run Auvik for 24 hours, and then it will bring up all the switches and all the devices connected to the switches. It will show where the firewall is as well. It has definitely taken away the time spent creating the network maps, which were never one of my favorite things to create in the first place.

Auvik helps keep device inventories up to date for us, especially with regard to switches, routers, and firewalls. Even if we're the ones who put one of these in, we don't necessarily have to go write down the serial number. We can get it configured, put it in, and then go back into Auvik to make sure that it's being picked up and monitored. We can also check whether we have all the information right there for us so that we can get everything right out of Auvik. If the switch gets replaced and it goes directly to the client, we don't necessarily need to see the switch because we know we can pull out everything we need right from Auvik to update our inventory of the devices for that particular client.

Having a stronger inventory and the flexibility to more easily find particular aspects allows us to delegate certain low-level tasks to junior staff. Because we can pinpoint exactly where particular devices are easily and quickly, we are able to delegate more high-value tasks such as important firmware updates so that patches are done as quickly as possible. It makes it much simpler because we know exactly which clients need the update. We can use Auvik from the portal to remote directly into that device to apply the firmware that we need.

Having Auvik keep our device inventories up-to-date takes away the need to have someone dedicated to recording that information or keeping the information up-to-date. We can just log into Auvik and get it. It's much faster, and we're not wasting time on doing something that, although is very important, takes away from us having the ability to do other much more important tasks.

The time-to-value is worth every penny. The speed at which Auvik alerts us when there are problems with switches or firewalls, or when switches or a segment of a network is down is worth it in and of itself. Then, you have the added benefits of VMware monitoring at no additional cost, configuration backup, and log storage. The cost of Auvik for the amount of time that can be saved and the ability to look good to a client because you're on top of everything is well worth it. The amount of time that Auvik has saved us is certainly worth its cost.

We have definitely seen a reduction in mean time to resolution. Auvik is very quick to alert us and give us the information we need based on the client and the switch. We can log into the Auvik website and get more information so that we can be more on top of things. There have been several times when we've had a switch go down on the client in the middle of the day, and we have been able to reach out to them to let them know that the switch is down and that we're working on it before they even realize that the switch is down. It allows us to get to a problem much faster and also helps us to look better to our clients. Prior to Auvik, if there was a problem we typically found out when the client reached out to us. The client typically would find out within 10 to 15 minutes that there was a problem and then reach out to us. So, it would probably be 15 to 20 minutes before we would know about the issue. Whereas now, we know about an issue within three to five minutes, so we're on top of it. Auvik has cut down our time by 10 to 15 minutes.

What needs improvement?

The biggest area for improvement is the speed of the website because it's not something we host. Each of our clients hosts an agent that gathers the logs and pushes it up. The website can be slow to click around in or click through.

One other area for improvement is a central location to figure out what devices are not having their configuration backed up or are not monitoring a certain item. Right now, you have to click into each switch, router, or firewall and then just make sure that all of the boxes are checked for backup and monitoring. This, technically, should already be happening as soon as a switch is installed. However, for auditing reasons and to verify that no one missed anything, having one place where you can click and see a list of all the switches, what's missing, and which switches are not doing what in the realm of backup or monitoring would be great.

Buyer's Guide
Auvik
January 2023
Learn what your peers think about Auvik. Get advice and tips from experienced pros sharing their opinions. Updated: January 2023.
670,080 professionals have used our research since 2012.

For how long have I used the solution?

I've been using it for three years.

What do I think about the stability of the solution?

The stability is good. Auvik is hosted on AWS, so if AWS is having issues, then Auvik will as well. However, the few times that I have remembered them having issues, they have been resolved quickly. We've seen no ill effects from any of the times they've had issues.

What do I think about the scalability of the solution?

It appears to scale very easily. We have small clients and large clients, and Auvik handles them all very well. It doesn't seem to have any issues with any changes we throw at it.

How are customer service and support?

Auvik's technical support is great. We don't have to reach out to them very often because we don't have that many issues. However, the handful of times that we have reached out for assistance with configuration they've always been easy to work with and helpful.

Technical support staff even reach out to us periodically and ask if there's anything that they can help us with. Auvik's support has been top-notch, and I'd give them a ten out of ten.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

We used a ManageEngine monitoring solution for monitoring switches. It may have come a long way by now, but the downside at the time was the sheer time it took to get it to monitor what you wanted it to. It did not have a configuration backup or the ability to check configurations and what was different between two particular configurations.

We had a big client we had just taken over who had quite a few switches and devices on the network, and we figured that it would be the perfect time to give Auvik a test run. We really liked the fact that Auvik would monitor, back up configurations, and map everything out.

We wanted the ability to retain logs for more than 15 days, and Auvik implemented the ability to push logs out to Azure or AWS for retention. You can get your own bucket of storage, connect it, and keep logs for as long as you like.

One of the reasons why I like Auvik's cloud-based solution is that it's easier to get alerts. If an on-premises network monitoring solution goes down, it's much harder to get alerts, whereas the cloud solution can tell you that it's down because it can't see it. You may get a false alert that it's down, but it's better to have a false alert and look into it than it is to figure out that it's a true alert. Alerting with a cloud solution can be a little bit better than that with an on-premises solution.

The other aspect that's nice is if hardware crashes on-premises because of a ransomware attack, for example, and I have my logs stored in a cloud solution such as Auvik, I can still get to those logs to figure out what happened or how the attacker got in and do some forensics work. Whereas if the logs were being stored on-premises, I would probably have lost them all.

How was the initial setup?

The initial setup was very straightforward. You have to go into Auvik, create a customer, get the agent to install, pop the agent onto a machine, and give it credentials so that it can scan. You let it run for a little bit, then you add your SNMP credentials into Auvik so that it can log into the devices, and you're done.

You can do more configurations to make sure that the backup feature is turned on or enable traffic insights for each switch. These are just a couple of clicks on the mouse. The initial setup and onboarding of new clients have been simple and quick. We've never had any problems.

We implemented Auvik out of the box. The network mapping started to populate within 10 to 15 minutes after the collector was implemented. How long it may take to truly grab everything depends on the size of the network, but typically, within an hour you will have a pretty solid understanding of the network via the map. If you were on-site with a new client, you could install the agent with their approval and have a meeting about the different aspects of what you're going to do for them. By the time the meeting is finished, you would have a pretty strong understanding of the entire network and what devices are out there.

What about the implementation team?

We deployed it with the help of someone from Auvik.

What's my experience with pricing, setup cost, and licensing?

Given the types of alerts and the different aspects of Auvik, I think it's worth the cost that is associated with it. I don't think the cost is terribly high. The infrastructure is the core or the backbone of a business. If it goes down, then the business stops. You have to decide how much money you're going to lose if your network is down and you can't figure out why for hours or days versus what Auvik would cost you a month.

What other advice do I have?

If you want to evaluate Auvik, give it a couple of days at the minimum. If you have any questions, reach out to their technical support. Ask them how to do things and how things work, or watch some videos on it. Auvik has a lot of functionality, but don't get overwhelmed. Look at each one separately, spend some time on each one, and just give it some time to sink in and see what it can do.

Overall, I would rate Auvik at ten on a scale from one to ten.

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Flag as inappropriate
PeerSpot user
Remote Engineer at Golden Tech
MSP
Provides a quick understanding of a network, and helps in finding out the issue easily and quickly assessing what we need to do
Pros and Cons
  • "I really like the network map. It's probably the most useful feature because we have monitoring set up in other systems too, but seeing what's connected to what and where it is makes a lot of things a lot easier to troubleshoot."
  • "When it comes to monitoring, Auvik provides a single integrated platform, but I feel it could do more things. If it could facilitate device upgrades, that would be great."

What is our primary use case?

We use it mostly for monitoring. Also, we're pretty big on getting device configs from it, but I don't know if we have used any of those configurations to roll anything back. For a lot of our network equipment, whenever you update the firmware, part of the feature of updating it is that it backs that up automatically for us. 

There are around 20 or more clients in Auvik that we monitor. Mostly, it's just for alerts if things go down, but with firewalls, we specifically have alerts that monitor memory because we have a problem with a couple of firewalls that go into the conserve mode if their memory hits a certain percentage. It's a huge part of our monitoring. Half or more of the alerts that come in, come in through Auvik.

How has it helped my organization?

It has made monitoring a lot easier. It has made finding devices and charting network maps for onboarding companies easier. If you are a tech and looking at a company for the first time, you can just look at the network map and quickly get an understanding of how big it is, how complicated it is, how many network tunnels there are, and what's the main firewall or the center of the network stack. It's super easy to quickly acclimate to a new network and troubleshoot up or down a network stack. I find that fantastic.

Being able to visualize the network mapping/topology for the organization is its best feature. It's very reliable. It'll more likely add a device that's not important than it will miss an important device. It does it so quickly and automatically, and not a lot of time is spent managing the network map. Every once in a while, once or twice a year, there'll be an alert, and we investigate it and we find out that it's just an obsolete device that was never removed from the map. So, you just delete the device. Other than that, it takes care of itself. It's fantastic. I don't have a lot of criticisms of it other than just keeping it up.

It's very intuitive when it comes to network visualizations. It is very easy to pick up, and it's great that there's a little key there that always tells you exactly how it's connected. It was probably the easiest thing to learn. If you aren't accustomed to Auvik, you can just look at it for 5 or 10 minutes, and you can absorb it. You're then good to go. You can very quickly and easily understand what you're looking at.

It has helped reduce repetitive and low-priority tasks through automation. It takes a lot of tweaking to get the alerts just right, but a lot of the repetitive tasks that we do have been automated. They've been automated for a long time, and they exist in very niche parts of our business that aren't really related to Auvik. The reduction is hard to measure, but it's a good percentage. In terms of the after-hours calls, with the emergency issues coming in, after two or three guys who set up Auvik went through the alerts and optimized it, with the number of things that took care of themselves and alerts that took care of themselves, we started getting fewer calls. Percentage-wise, there is a 20% or 30% reduction. It wasn't a huge chunk at the beginning, but it was noticeable once they got everything ironed out with Auvik.

It has affected our IT team's visibility into remote and distributed networks globally. We're a service provider. We manage a lot of networks. They range from a single network stack to multiple locations with multiple distribution frames that are all tunneled into each other. Before Auvik, it was pretty difficult to get an idea of how something was set up because we were just looking at configurations and talking to other people. It took a lot of experience to get used to a single client. Now, when everything is set up, if we want to understand the network, we just go into Auvik, and we can see the whole network.

It's a big part of our networking and monitoring. I'm in Auvik a couple of times a week. I don't specialize in networking, but I still end up looking at Auvik a couple of times a week to solve something, or I have to work on an alert that came specifically from Auvik, and I have to investigate. Aside from the UPS battery alert issue, which is obnoxious, most alerts are pretty easy to understand, easy to follow up on, and easy to resolve.

It has had an effect on our IT team’s availability. It makes the work of the IT team easier. We spend less time troubleshooting, and we are more available to work on other things. It has saved a considerable amount of time. We only have one network engineer, but everyone else is capable of working on networks. Auvik has made it easy enough to point to the issue. So, the network engineer can just focus on the really important and really intensive things, and everyone else can work on the intermediate things by using Auvik. Previously, it would take twice as much time for somebody like me to figure out a network problem.

It's very easy to delegate low-level tasks to junior staff. The API is integrated with ConnectWise. So, the alert comes in, and the dispatcher lets everybody know, and then any of the techs here can work on the alerts. With the information that we have in Auvik, we're able to very quickly assess the first thing that we need to do. We almost always get it resolved in time unless it's an ISP issue.

What is most valuable?

I really like the network map. It's probably the most useful feature because we have monitoring set up in other systems too, but seeing what's connected to what and where it is makes a lot of things a lot easier to troubleshoot.

The uptime and downtime information is valuable. It is pretty reliable to know when something goes down.

I find it pretty easy to use the monitoring and management function of Auvik. I passed the test on the first try, and it's all very intuitive. I like the menus, and it's pretty easy to get through things. There are some things that are a little bit more complicated, but there was nothing I wasn't able to figure out. Rarely, I would have to reach out and ask somebody to show me how to find something in Auvik or how it works. In terms of accessibility or how easy it is to get into it, it's pretty easy. Even setting up devices for configuration polling and SNMP is pretty easy.

What needs improvement?

When it comes to monitoring, Auvik provides a single integrated platform, but I feel it could do more things. If it could facilitate device upgrades, that would be great. 

It also has a feature where it passes alerts along. So, a device will have an alert, and then Auvik will pick it up, and then the API will create a ticket through Auvik, but the alert will be very vague. The one with which I had the biggest problem, more than anything else, is the alert specific to a UPS. There is a specific alert when a UPS's battery hits five years old, which means it needs to be replaced regardless of whether it's alerting or not, but the way the Auvik finds the UPS and gets the alert makes it almost impossible to tell which UPS it is. If the UPS has a web portal or a web GUI that I could go into and take a look at the battery, life is great, but we had one tenant where all the UPSs didn't have that. It took forever to figure out which one had a battery that we had to replace. Its monitoring is great, but the integrations could be better.

Overall, it hasn't provided a single integrated platform for us. We still have to use other tools to shore up where Auvik is lacking. For the most part, Auvik helps keep device inventories up to date, but it's not perfect. One of my least favorite things is that people bring in devices, their devices get retired, and then they just go off. A lot of times, we wouldn't know if it is something that we need to get back online as soon as possible, or if it's something that just went down. There were times when little switches that are under people's desks would be mislabeled with critical network infrastructure. Someone kicked a switch or something like that, and it went offline. We got the alert, and we wondered where it is and how could we get it back online. We called the company, and they were just like, "Oh! It's this little thing in here. Just plug it back in." It was just used for the printer. There would also be devices that were being retired, but the service desk or other teams wouldn't know about it. They would spend half an hour trying to figure out what was going on. So, even though it takes care of the inventory, there is a small amount of auditing that we still have to do. That's normally done because we're getting a lot of false positives, which probably is a good thing. It's better to get a false positive than for it to not alert when something important has gone down.

It's as good as anything else out there. It isn't better or worse than the systems that we already have in place. We don't use it for device inventory because we have other systems that keep track of devices and configurations. When I think of device inventory and Auvik, it is to know whether something that's currently online needs to be online. I would never look at Auvik to determine how many computers are currently at a location. I have two other systems that already do that for me, and they do a better job than Auvik. For the systems that we use, we have agents on computers. So, they give us an enormous amount of information about computers and things that are available at a location, or just an asset list for a client. Things that we can do remotely through them are pretty incredible. If Auvik wanted to be competitive, they would have to get into an area their competitors or the other companies do in terms of putting agents on things. That's a whole different thing than just SNMP polling.

For how long have I used the solution?

We started Auvik at the beginning of 2020 because I remember taking the Auvik test while working remotely during COVID.

How are customer service and support?

Their support is fantastic. If I have a problem with Auvik, I just open up a chat to interact with somebody, and they get to me in a minute or two. They almost always get it resolved just through chat. I don't remember ever having to call Auvik.

The central services people tell me that Auvik has quarterly reviews with our company. So, they follow up with us all the time. 

I would rate their customer service a 10 out of 10. They get to me immediately, and they always help me solve the problem, and they're always nice. I've probably talked to the same three guys every time.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

We were using Audit API, which was pretty useful, but they were mostly Windows machines that had our agent servers and workstations. So, a server workstation would go down, but all you would know is that the server is down, or the whole site is down. We would have to do a lot of digging on our own to piece together:

  • Which devices are there?
  • What does the stack look like?
  • What's the first thing that we need to troubleshoot?

We definitely tried to make the Audit API work, but the consensus was we needed something better to get these things done faster so that we weren't spending so much time during discovery especially, or we weren't spending so much time chasing alerts after hours.

Once we got Auvik, that became way easier. Instead of having to dig to figure out how it's set up, we could immediately look at Auvik and determine what the first step needs to be. It has cut off a huge amount of discovery. We have so many clients, and you have to be here for a long time before you know everybody, and even then, some clients don't really have problems. You're only looking at them a couple of times a year. So, if you have a great memory, good on you, but Auvik really made it a lot easier for service desk techs. We're not in the network all the time, but we troubleshoot networks frequently enough, and it's important that we are able to do this quickly and correctly.

How was the initial setup?

For us, it's better that it's a cloud-based solution. I don't know about other companies, but we're remote to almost all of our clients. So, it's all cloud.

I did a lot when it comes to getting configuration polling working for firewalls, but other than that, I haven't been a part of its initial setup. The central services and networking teams got it set up, and then once it was ready, the techs like myself took the Auvik test. Once we passed, there was some tedious work that needed to be done at first setting up SNMP on networking equipment and making sure configuration polling was working, but that was about it.

It did take a while to set up Auvik, but that's because we have a lot of companies that we monitor. Everything was running smoothly within about six months we started working with it.

What was our ROI?

We have absolutely seen time-to-value with Auvik. It has cut down after-hours support. We're spending less time in the middle of the night trying to figure out why a network is gone so that we'll be up in the morning by the time people arrive for work. That was just huge for us. There are fewer tickets on the board during the day, or we can resolve the tickets we get faster.

We have seen a reduction in our mean time to resolution. In my experience, it has just cut that in half. We can just look at Auvik, and we know what a network stack looks like. We can begin planning how we want to approach the problem.

What's my experience with pricing, setup cost, and licensing?

I don't know anything about its pricing, but I would say Auvik is worth it.

What other advice do I have?

I would rate it a 9 out of 10. It works superbly. It has made my job a lot easier. It made me understand networks so much better and more quickly too. I love Auvik, but they could do more with integrations. If we could just do everything through Auvik, such as push firmware through Auvik, and if Auvik was better at telling me which UPS has a battery that needs to be replaced, I would give it a 10 out of 10. 

Which deployment model are you using for this solution?

Public Cloud
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: Partner
Flag as inappropriate
PeerSpot user
Buyer's Guide
Auvik
January 2023
Learn what your peers think about Auvik. Get advice and tips from experienced pros sharing their opinions. Updated: January 2023.
670,080 professionals have used our research since 2012.
Network Engineer at a computer software company with 51-200 employees
MSP
Makes onboarding new clients very straightforward, easily mapping the network and saving manual work
Pros and Cons
  • "Among the most valuable features are the hardware life cycle and configuration backups, when applicable... When it does show you the hardware life cycle for, say, a Cisco device and the configuration backup, that's the most useful aspect for me as a network engineer."
  • "Something else I would like to see would be additional vendors for the hardware life cycle. Right now, they mainly focus on Cisco stuff, which is fine, but not every customer we have uses Cisco."

What is our primary use case?

We use it to monitor the network infrastructure and assets of our clients. We are a managed service provider and it fits neatly into our role. We also use it to keep configuration change records, which is something we didn't have before. It's nice to have that in one platform.

How has it helped my organization?

When we are onboarding a new client with network infrastructure for monitoring, Auvik makes it very straightforward and simplified. It can map out and easily visualize the customer's network so that we don't have to manually do it. It definitely has increased automation.

We used PRTG but it lacked the mapping function to visualize the network with an interactive map. It also lacked the configuration backup tool, the hardware life cycle, and good NetFlow insights. Moving to Auvik has saved a good 30 to 50 percent of our time.

Another thing that I love that Auvik does and that PRTG doesn't do is the integration with a lot of our MSP tools like ConnectWise and Teams. PRTG would open tickets via an alert, but it would never close them if the alert cleared. All those tickets from PRTG would go to me and I would have to manually close them. I would get inundated with tickets. Auvik will also open a ticket but, once the alert clears, it will automatically close the ticket, saving me from having to close a lot of tickets. That too has reduced repetitive work for me by 30 to 50 percent.

Our MTTR has almost been automated because of the tickets. About 90 percent of our tickets have been automated. I still have to manually look at the rest and maybe do a little work against them, but it's not crazy. It has unquestionably helped out with resolving issues.

It has also helped tremendously with quarterly business reviews because, with just a click of a button, we can get the hardware life cycle and export all the data to an Excel spreadsheet. That helps our management.

And because most of our clients are remote from us, that visibility that Auvik gives into their environments is in a better overall layout than our previous platform. The UI of PRTG was very '90s-esque, like a poorly designed website. It had the functionality but the UI was lacking tremendously when it comes to ease of use and organization.

The visibility Auvik provides almost makes it so that we don't have to be actively monitoring things. We don't need a NOC or a SOC to get alerts. We're more confident now in the network management solution that we have. Before, we were getting alert upon alert and my phone would be blowing up and then I would get all the tickets. Auvik has put that kind of stress on the back burner.

Overall, it has freed up about 25 to 30 percent of the time I used to have to put into things.

Another advantage is that I didn't want to show a junior tech our previous platform because they wouldn't know what to do with it. Auvik, on the other hand, is more geared toward all levels, rather than just the high-level engineers. It will tell you what might be the cause of a problem rather than just alerting on something that it sees. While we don't have it geared toward our lower-level team yet, it's very easy to use and they should be able to pick it up.

What is most valuable?

Among the most valuable features are the hardware life cycle and configuration backups, when applicable, since that's not applicable for all vendors, platforms, and networking types. When it does show you the hardware life cycle for, say, a Cisco device and the configuration backup, that's the most useful aspect for me as a network engineer.

Once it's set up properly with the SNMP strings or credentials, it's very straightforward to use. It has a small learning curve, which is nice for a network monitoring tool. Ease of use is very high on our list of requirements, not just for me as a network engineer, but when I want the help desk or the level-ones to be able to look at something. It needs to be easy to use.

It's also very much a single pane of glass, which is especially helpful for our business model as an MSP.

In addition, I greatly appreciate Auvik's ability to visualize network mapping. It's very good for visualizing how the network is formed and the interconnections. Since it's interactive, it's more helpful than a static map or static video diagram. It's a very helpful feature.

What needs improvement?

I like how you can request features, and one feature that I think they're working on is the ability to export the topology map as a video.

Something else I would like to see would be additional vendors for the hardware life cycle. Right now, they mainly focus on Cisco stuff, which is fine, but not every customer we have uses Cisco. I'm not looking for them to add every networking vendor, and these just might be legacy devices, but Fortinet is a big one that we've used and I don't think Auvik has the hardware life cycle for that. I don't know how it does on Aruba, but we have some legacy HPE as well. I do like the Meraki integration, although it would be nice to see a Juniper Mist and Aruba Central integration.

Another improvement that would be nice, one that should be at the top of their list, is the ability to properly identify vulnerabilities, based on a vendor's security alerts. If it could recognize, "You're on this version of firmware and you're hitting these types of vulnerabilities," that would definitely check off a big security feature for this tool.

For how long have I used the solution?

We demoed Auvik early in the year and we fully signed up sometime in the summer, so we have been using it for several months.

What do I think about the stability of the solution?

Overall, it is very stable. 

Every platform or NMS has its own quirks or kinks that have to be worked out, but it's nice that Auvik will update on the backend. I don't have to worry about updating a server platform.

What do I think about the scalability of the solution?

Its scalability is very high. It gets a 10 out of 10.

We have Auvik across multiple organizations. We monitor, administer, and maintain, network monitoring for dozens of clients. It's deployed across all their different environments and in organizations with multiple branch offices. Our clients include the smallest, one-branch organizations up to medium-to-large enterprises. It definitely fits all those use cases.

How are customer service and support?

The technical support that Auvik provides is very good. They're very quick to respond. They have a live chat feature, which is very nice. They're pretty knowledgeable since it's their product. There's no comparison between the support from Auvik and the support we received from our previous vendor.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

We used PRTG before and we're still using it now. We're trying to slowly migrate from it. We put all our eggs in that basket, even though it was a very flimsy basket. We used it for networking servers, mainly.

We didn't use it for endpoint and computer assets. That was handled by ConnectWise Automate. We wouldn't want Auvik to do that.

How was the initial setup?

The deployment was very straightforward because of the user interface. This is where it's more straightforward than Domotz. Sometimes, when you have too many choices, it can be a burden. With Auvik you decide: Do you want the OVA? Do you want to install a .exe? It's very simple. I could probably have someone on our level-one team actually set it up.

It took less than 10 to 15 minutes after the collector was implemented before the network mapping started to populate with basic devices. Then it was a matter of fine-tuning. It was up to me to categorize devices as I saw fit and tune the SNMP so that it got the data that I wanted.

Overall, our implementation of Auvik took a few weeks because of the number of sites and devices and the fine-tuning. Also, an NMS is always being worked on. You're rarely perfectly happy with how it looks. It's constantly being fine-tuned so that alerts generate correctly without over-alerting.

That's one thing I have liked compared to PRTG. Auvik's out-of-the-box alerting is very straightforward and handles the alerts you are likely to see. But that's also where it could do a little bit better, in the customization of alerts. With PRTG, we could alert on almost anything, whereas with Auvik, you're somewhat zoned in.

We have definitely saved a good amount of time on the setup of Auvik, compared to PRTG. PRTG was significantly cheaper, but there was no onboarding help. It was a matter of, "Here you go, do it yourself." Auvik had a customer success team to walk us through and help iron out any kinks, which was greatly appreciated. That was part of what we're paying for. The pricing helps with support. PRTG's support, while it was okay, wasn't as straightforward and easy to get a hold of someone compared to Auvik.

The maintenance involved with Auvik is around fine-tuning for data collection, but it does not involve updating the agent or the backend. It's nice that I don't have to worry about updating the platform itself. I just have to worry about the data getting collected and making sure SNMP strings are updated.

I was the only one involved in the initial deployment, from our side.

What was our ROI?

I didn't set up PRTG but compared to my brief time with PRTG, Auvik has been night and day and the value has been very quick. For some of our customers, we never had a solution in place to back up configurations. Auvik now provides that. There's definitely peace of mind knowing a config backed up. It is definitely proving its value.

What's my experience with pricing, setup cost, and licensing?

I don't think Auvik's pricing should be based on device, which it is right now. I don't know what their market share is or how they compete with Domotz, but if they want to stay competitive, Auvik should have simpler pricing. Domotz is $21 per month per site, whereas Auvik is per device, so it definitely adds up very quickly.

Which other solutions did I evaluate?

In addition to the other issues I mentioned, Auvik and our previous platform are night and day in the following way as well. We would almost be scared to put in a subnet for PRTG to scan because we wouldn't know what we got. Now, it's easy to see what we're getting in terms of the devices and prune it from there. 

It's also helpful that it's not onsite because we're trying to move servers and services off-prem. Auvik is definitely a step in the right direction. It's one less piece of infrastructure to worry about. You don't have to open up your environment to collect monitoring information. It just needs outbound traffic, which makes things easier. That's where it shines compared to an on-prem solution. Also, you don't have to maintain or update software or the agent. It does that automatically. I don't have to worry about updating firmware.

With an on-prem solution, everything is hub and spoke and everything has to go back to our data center. Auvik, as a cloud solution, eases up on that usage of our circuits and internet.

While Auvik is geared toward network infrastructure for an MSP, it could probably do a little bit better on the server side. PRTG definitely had that as an advantage over Auvik. It could monitor servers and that type of infrastructure better than Auvik can. 

Auvik also doesn't have some customizable automations for a specific use case that might need an if-then-that statement to run a script or commands. That might be very niche, but one of our clients is using PRTG like that. 

It is nice to see that Auvik has an expanding roadmap. I don't know what PRTG has on its roadmap for new features, but it's nice to see that Auvik is not getting stale.

I did evaluate Domotz and the pricing worked out in favor of Domotz, but we ended up going with Auvik. We're only in Auvik for a year and we'll see how it goes, but unless the pricing becomes too high, I don't see us moving away from it. Domotz was the only other one that was within reach and more geared toward MSPs.

An MSP business can almost flip a coin between Domotz and Auvik. Auvik is priced per device, whereas Domotz is priced per location or site. It works out in Domotz's favor, although I can't speak for its feature sets. Domotz does have a leg up in terms of deployability. It has a hardware appliance, almost like a Raspberry Pi, so it's easy to deploy on anyone's network, whereas you have to run Auvik as a virtual appliance. It can't run on ARM, which is not a deal-breaker, but it is nice to have options when deploying. You're somewhat locked in with Auvik for deployment because you need to run it on a server or in someone's vCenter. It's not that customizable, whereas Domotz can run on ARM as well, I believe.

Auvik has two versions, Essentials and Performance, which is similar to Domotz's model. With Performance you get NetFlow visibility and another feature and that increases the price per device. But the device types they charge for are only those that are part of network infrastructure. Overall, it's probably cheaper via Domotz, but if you have a lot of sites with just one device, it might be cheaper to go with Auvik. Auvik doesn't charge for access points, but they do charge for switches, routers, and firewalls.

What other advice do I have?

Auvik definitely helps keep device inventories up to date. If I have the scan running, it does a really good job of finding devices on the network when the subnets are put in. However, the network infrastructure shouldn't change that much, so I don't typically have it running scans all the time. We're mainly using it for network infrastructure and not as much for endpoint devices. It primarily shines when it comes to network infrastructure, but it did do a pretty good job of doing the initial inventory of the networks.

My advice would be to do a proof of concept if you are in an MSP role or organization, because the costs can quickly add up.

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: MSP
Flag as inappropriate
PeerSpot user
System Engineer at a energy/utilities company with 51-200 employees
Real User
Top 20
It's helpful if you're trying to troubleshoot and the documentation isn't a hundred percent up to date
Pros and Cons
  • "With TrafficInsights, we can view the information and do something with it. In the past, we couldn't easily find that information."
  • "Auvik could have better compatibility with more devices. The devices that we're using are essential within our network infrastructure. It would be great to access the full range of features that some of the other ones do, such as the device configuration backups and the configuration change alert."

What is our primary use case?

We initially got Auvik to monitor our network devices and equipment mainly for outages and that sort of issue. We have integrated its alert system and email-to-text solution from a local New Zealand telecommunications provider so that our IT staff can get text alerts to their phones. It's quite handy because you're not constantly monitoring your email. So for our different alerts, we get texts now as well as part of that. It might be on the weekend or something like that, and you're not sitting there monitoring your emails, so texts are a bit easier for our on-call IT person to get a text, and then they can check out what's going on.

One of Auvik's services we use is TrafficInsights. It's reasonably new and wasn't around when we first got it. We can feed all the logs into there to see what connections are going and where things are connecting to the environment. It's pretty useful from a security perspective. For example, you can search and see when a specific IP address might have come into your environment if you need it to do an audit or a review. We generally use it for audits or checking where certain things are connecting from around the world. It's a good security feature we can use when we're worried about a device talking to a particular IP address. We can see how long it may have been talking to that. We haven't actually used it for network bandwidth as such.

Auvik also acts as a config register, connecting and pulling the configurations of switches. It's good to have that stored there. If we need to restore or roll back to a particular config, those are saved somewhere else in addition to saving it manually before we make changes.

How has it helped my organization?

Auvik has definitely saved us time. You don't have to go to a room somewhere and figure out what's under what. It's scanned, so it shows you everything, including what interfaces are hooked into what devices. If you didn't have that, you'd need to go into a room to look at a fizzled connection and find where it plugs into. Auvik has decreased our average time-to-resolution. For example, if we have an internet outage in our office. In that case, it shows that an internet connection has gone offline and tells us when we've got a failover internet circuit with different providers. 

In the past, we wouldn't have even been notified if we swapped over to one of the other internet connections. When troubleshooting, we know right away when something isn't working or hasn't come up online. We can see which connection is active or current and which is offline. I can't say precisely how much time we've saved using Auvik, but from a year's perspective, I've probably saved a couple of weeks' worth of time. It's reduced the amount of time I spend manually performing tasks like documentation, mapping things out, and troubleshooting. Auvik's features help us address issues before they become a problem for our users. For example, we have a resource usage alert that pops up when there's a sudden increase so we can jump on it. We can stop a non-essential service from taking up a lot of resources and could potentially freeze the server or device. It saves a lot of time addressing the issue after the fact while preventing potential impacts and outages.

It includes automated out-of-the-box device configuration backups for most things, including most generic Cisco functionalities. These have also saved us time. Before I joined the company, they had a separate service for that. They were paying for something else on top of other solutions. Having that all in the one system saves time as well. You don't have to worry about doing it manually. When we make changes to devices, it automatically rolls over to the next one. You can have a log of the dates and times when it changed, and you can set up notifications for when the configuration changes. You can investigate if it changes when it shouldn't have. Without that, you wouldn't even know it has changed without looking at it, but then I don't think you would anyway.

Our team is pretty small. We only have a small IT shop within our business, but we still have our services with Auvik. It makes it easier for them to fix problems quickly without trolling around and finding other documentation. They can jump in there and see the alerts on that map, giving a bit more information. It saves the rest of the team from constantly having to look at the networking.

What is most valuable?

Auvik is easy to use and provides us with an abundance of information. It can show what devices are connected to the network and the specific interface that it's connected to, saving us a lot of time. It's helpful if you're trying to troubleshoot and the documentation isn't a hundred percent up to date, like if you take over from someone else, and there's no documentation about how a specific device connects. If it's in Auvik and the network is set up, you can jump in there and find what it's connected to. It even maps it out for you in a pretty little diagram at the top. 

It's comprehensive. You load up a network, and it picks up pretty much everything. That makes it easier to use without having to do too much pumping. In terms of discovery, we only use it for certain things, such as our network gear and our servers. It picks up everything. You do have to do a bit of filtering and some tie-up to make sure you're not seeing stuff you don't want for your specific use case, but that comes down to what different people use it.

Auvik is constantly scanning automatically in the background, and if there's a new device in the network, it'll pick it up. You have to make sure that you have credentials or the right port sector so it can pull the correct information. It may be able to see the device, but it may not necessarily get the information from it.

TrafficInsights has helped us identify and troubleshoot performance issues. When we're doing maintenance, you can monitor it live and ensure that the performance isn't being affected too much. If it is, we can pause and decide to reschedule when there's not so much going on. With TrafficInsights, we can view the information and do something with it. In the past, we couldn't easily find that information. We'd have to dig through individual policies or logs, like on a firewall, for example, whereas it's now all in one place. That made it easier to be able to view that rather than clicking and moving between multiple places.

What needs improvement?

Auvik could have better compatibility with more devices. The devices that we're using are essential within our network infrastructure. It would be great to access the full range of features that some of the other ones do, such as the device configuration backups and the configuration change alert. But there are always new devices coming out, so they have to work through getting the compatibility in the first place.

It makes too many attempts to connect to devices when it's online. You want real-time alerting and that sort of thing, so it has a lot of active connections going on behind the scenes. It creates quite a bit of talk on the network when it's connecting to a device. When it's trying to connect to one for the first time, it tries all the credentials you have saved within your credential library, and that isn't always ideal. If you're on the device, you can see that there have been a lot of failed login attempts because it's just trying another credential that it shouldn't use.

For how long have I used the solution?

We've been using Auvik for about a year and a half.

What do I think about the stability of the solution?

When we need Auvik, it's there. There is quite a lot of maintenance that goes on behind the scenes. We get alerts when Auvik is unavailable due to maintenance, but that's also a good thing in cybersecurity threat environments these days. Being in IT ourselves, we know how important that is. 

What do I think about the scalability of the solution?

It's simple to scale up because you can add a whole network or office environment into it quickly. If you don't need it anymore, you can delete it. It's very scalable.

How are customer service and support?

I would rate Auvik support eight out of 10. I've opened a couple of support tickets when we've needed certain things. They respond pretty quickly. We've also had chats with them throughout the setup process. The account managers have helped us get questions answered or pointed us in the right direction.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

Before I joined the company, they had a PRTG system, which is similar in terms of the overall goal. But I had Auvik, which is a lot easier. It's all there. As long as you've got the network and a user to connect to something, then you're basically on your way, and you don't need to do much with the collectors either, which is the thing that talks and you install it and make sure it can talk to the right places on the network. You pretty much let it do its own thing. 

Ease of use and functionality were probably the main things that made us switch. PRTG is a product that requires you to set up a lot of things manually. There wasn't specific device compatibility. It was just standards, whether it was the way a device connected or the protocols through which it is connected to the device to pull the information. Auvik sets things up and has specific compatibilities with devices and a much nicer view to see the information that the old product didn't have.

How was the initial setup?

Setting up Auvik is straightforward. It has decent documentation and specific instructions on how to configure it to work with compatible devices. You're not trying to follow some document for a completely different device and apply it to your device. There's lots of information to use to help you with that configuration process as well.

I can't say precisely how long it took to set up, but you can get a whole network mapped out pretty quickly. I've set up a few offices around the country. It took me a couple of hours to get everything fully monitored and plug the information in. To set it up, all you do is check a network, scan, and get some credentials. That takes less than an hour. Then you're just waiting for the information to start going in. With other products, you sometimes don't even know where to start, to be honest. If I were trying to do the same thing on another solution, I might end up spending an extra day on it for the same sort of setup, whether that's a whole office environment or setting it up from scratch.

We did the implementation ourselves. In the first year, there was a local reseller who sold it to us, but they didn't help us implement it. We have a four-person team for everything, so we take turns doing different things. In terms of maintenance, there isn't a lot we need to do on our side. Once we've got it set up and doing what we need, then there isn't a considerable amount. The only time we need to perform any maintenance is when we're setting up new equipment. On the other side, Auvik does its maintenance. So we'll get emails about them completing maintenance and the service availability and that sort of thing.

What was our ROI?

It's hard for me to estimate the return because I don't know what that service costs, but Auvik has replaced the separate service we formerly used for device configuration as well as our old network monitoring solution. I don't know the difference in cost between Auvik and our old solution, but Auvik saves a lot of time, and time is money. 

What's my experience with pricing, setup cost, and licensing?

I'd say Auvik's price is reasonable. I don't know how much we paid for the old one, so I can't compare the two. But I think it's a good value, considering all the time saved and the information you can get from it. The license is billed according to the number of network devices. It bills you based on a few specific types of devices, like switches, routers, and other network devices. We're not even using all of our device allotment at the moment. I think Windows servers and machines and that sort of thing aren't counted as part of that licensing. We aren't charged for servers, I believe. We have a virtual environment, so all of our servers and virtual machines within that aren't part of that licensing scheme.

Which other solutions did I evaluate?

I think they were looking at about three solutions at the same time. They did a few trials a couple of years back. I can't remember which ones. I think there was a Solomon solution. They decided to go with Auvik because of all the information it displays and the ease of use. 

What other advice do I have?

I'd probably give Auvik an eight out of 10 at the moment. We're still waiting for them to become compatible with all of our devices. If they had that compatibility, I'd probably rate it nine or 10. For those thinking about adopting Auvik, I would say go for it. 

My advice is to put time into setting up the alerts because that's one of the best parts about it. If you have those alerts set up, it's going to save you a lot of time. You don't even need to go into Auvik to investigate. With that notification, the process comes a behind-the-scenes method for resolving those alerts. You should have a plan so your IT team knows what to do when one of those alerts is triggered.

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Brian Rardin - PeerSpot reviewer
IT Specialist at SES, Inc.
Real User
TrafficInsights allows us to see interface utilization, both WAN-facing and LAN-facing, and provides historical data as well
Pros and Cons
  • "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 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."

What is our primary use case?

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.

How has it helped my organization?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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. 

How are customer service and technical support?

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.

Which solution did I use previously and why did I switch?

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

How was the initial setup?

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.

What about the implementation team?

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.

What was our ROI?

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.

What's my experience with pricing, setup cost, and licensing?

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.

Which other solutions did I evaluate?

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.

What other advice do I have?

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.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Sr. Network Security Engineer at a tech services company with 51-200 employees
Real User
Top 10
Builds and updates network topology in real time, making that information immediately available
Pros and Cons
  • "One of the best things about Auvik, and it's why it's one of my go-to products, are the remote access capabilities. Without a VPN and without any other way in, I'm able to get in and work on and troubleshoot my devices through the remote access console. It has multiple options for that and has been very useful and a huge time-saver. That's one of the killer features. It's one of my must-haves and that's why I like it so much."
  • "The automated, out-of-the-box device configuration backup capability is one of the key features for me in Auvik. To manage a network, one of my key requirements is to be able to rebuild that network if something catastrophic happens. Having up-to-date backups is a must, and this is a tool that I count on to get that right, and it has always performed as I expect."
  • "The logging features could be a little bit better polished, although that aspect is relatively new. It comes in as raw data, with different formats for different vendors. It's not immediately clear to people what's going on with some of that and you have to read through the codes. Some of the higher-end logging solutions, like Splunk, which is very expensive, can parse through it and correlate items better. Improvement to the logging features would be a value-add, but I'm still very happy that it exists."

What is our primary use case?

I do internal IT for a company and I use Auvik for most of my daily tasks as they relate to firewalls, switches, and routing.

How has it helped my organization?

The automation of network mapping enables junior network specialists to resolve issues directly and helps to free up senior-level team members to perform more involved tasks. It can be a key tool in environments where somebody who doesn't have a strong network skillset can go in and see, "Is it good, is it not?" and be able to make a decision on whether it needs to be escalated to me or not.

It also automatically updates network topology. One of the things that I really enjoy doing, when I first get into a new environment with it, is to watch it rebuild the map as it learns in real time. I can see its process and for me, as a very technical guy, that is one of the most entertaining things to watch, as it learns and updates the changes in a network in real time. It saves time maintaining network topology since the tool actually does it automatically. I have a high level of confidence that the information is correct, and it is immediately available. Just last week, I got a call from one of our internal auditors who needed to provide some information. He said, "Yeah, this usually takes a few weeks. Can you provide firmware information and serial numbers?" During our phone call, I was able to get into Auvik, pull the list, get it sent over to him and say, "Here you go. We're done."

Auvik has also decreased our mean time to resolution. Being able to go in and look at what's not broken, very quickly, and get that confirmed, means that I can look at what I actually need to fix. It eliminates a whole bunch of other problems and a whole bunch of checking. It has reduced our MTTR by up to 80 percent in some cases.

And because we've got it triggering PagerDuty alerts, if something problematic really fires off, I will know about it and be in the tool looking at what's going. I can say, "Hey, this is a problem we need to alert," or, "This isn't a problem and we just need to be aware," very quickly.

Another benefit is the TrafficInsights feature which shows network bandwidth usage without the need for expensive, in-line traffic decryption, and it does it very well. That is a very nice-to-have in my current role because we don't have issues with our network bandwidth. But in other environments that I've been in, where there were issues with bandwidth, it is a very well-put-together tool allowing me to find the answer and say, "This is what our problem is." It enables me to tell the business that we either need to spend more money on bandwidth, or we need to deprioritize a certain type of traffic. It gives that information in a format in which I can give it to somebody who is less technical than me. I can show them the graph and say, "This is what's going on and why."

TrafficInsights helps to show you where your system is experiencing performance issues around capacity and what is the busiest traffic. It can help improve network performance by letting me know exactly what's going on. It lets me see whether it is an application misbehaving, a lack of bandwidth, an upgrade that we need to make, or a configuration. It gives me these choices so that I know for real what's going on. In some cases, people "feel" that something is going on, but this gives me the facts to know what's going on. I would estimate TrafficInsights has improved our network performance by 50 percent.

In multiple environments I've been in, we've been able to eliminate other tools and use Auvik as our single network management solution. In those environments, I've had up to five tools that I have been able to decommission by using Auvik. In that environment where there were so many tools in place, replacing them probably saved $100,000 a year.

What is most valuable?

Some of the key features that I get out of it are that it is a well-rounded monitoring solution, so I know when something fails—whether it's a device or a service on the device. But it also performs backup, in inventory, of some of the key things to control and manage the network.

And one of the best things about Auvik, and it's why it's one of my go-to products, are the remote access capabilities. Without a VPN and without any other way in, I'm able to get in and work on and troubleshoot my devices through the remote access console. It has multiple options for that and has been very useful and a huge time-saver. That's one of the killer features. It's one of my must-haves and that's why I like it so much.

In addition, for products in this category, Auvik's ease of use is one of the best. It's really built for people like me. I'm heavy into the parts of IT that are not server-related, including routing, switching, firewalls, et cetera, and it is organized for somebody like me. It is the network engineer's toolset. It gives me what I need upfront in a way that I understand well. Auvik speaks my language.

When it comes to its network discovery capabilities, It is the best that can happen. I've used it in multiple environments, and as long as I've got the right starter information, it can go find information in an hour that would otherwise take a person weeks. It's very good and very quick. I've been able to benchmark it against competitive tools and it is way more useful, giving me information that I actually need and can use.

The automated, out-of-the-box device configuration backup capability is one of the key features for me in Auvik. To manage a network, one of my key requirements is to be able to rebuild that network if something catastrophic happens. Having up-to-date backups is a must, and this is a tool that I count on to get that right, and it has always performed as I expect. I am able to very quickly and easily audit that the backups happen and I know that they're there. I can also restore to a previous point with very little hassle, if anything goes wrong. Compared to other backup solutions, it saves me 80 percent in terms of my time.

What needs improvement?

The logging features could be a little bit better polished, although that aspect is relatively new. It comes in as raw data, with different formats for different vendors. It's not immediately clear to people what's going on with some of that and you have to read through the codes. Some of the higher-end logging solutions, like Splunk, which is very expensive, can parse through it and correlate items better. Improvement to the logging features would be a value-add, but I'm still very happy that it exists.

There are a few edge cases where I have found support for devices to be a little bit lacking. I'm migrating away from Check Point right now and Auvik and Check Point do not get along at all, so it was very troublesome to get those put in place.

Another issue that I know is already in progress, but that will be very nice, is full integration with PagerDuty. I'm using email connectors right now that have a little bit of a lag, so once the APIs are in place between Auvik and PagerDuty, it will give me better alerting when something breaks. I know that's on the roadmap because I've talked to them about it.

For how long have I used the solution?

Between two different companies, I've been using Auvik for about three years.

What do I think about the stability of the solution?

The availability is 99 percent. They do have maintenance windows where it's not available. I've been happy with their communication on the maintenance windows and they pick the times very well when it's not going to be available. I realize that everyone needs maintenance, but it works out very well.

What do I think about the scalability of the solution?

I've used this for everything from companies that are in a single building up to a company that had offices in 20 time zones with almost 100 offices, some of them with 1,000 users, and it was able to scale up to that. I've never had worries about how big this can go.

How are customer service and technical support?

Their technical support is fair to good. There have been a few times where I've had to escalate to somebody higher, when I thought the lower-level person should have understood it, but I've always ended up with a good answer.

How was the initial setup?

The initial setup is straightforward and, as far as the product category is concerned, it's the most straightforward. I've used this in an MSP environment and I've done deployments into close to 30 companies with Auvik and it is, by far, the fastest way to do it for a fresh deployment.

We can get the initial install going in a few hours and we can be confident in the data in a week or two. Comparing that to other tools, it would be an initial deployment of a week or two and two months until we're confident with our data. It has probably reduced the time spent on setup by 90 percent. And when dealing with an MSP, it cuts down a client onboarding by at least a month, which lets revenue start coming in earlier.

The implementation strategy depends on the size of the environment that we're going into, but we usually put in collectors at key locations and first let them do their discovery and see what's out there. Then we'll tune them down so that the collectors are monitoring from the right locations. But we like to get as much data in as possible, initially, and then tune downward.

As a cloud-based solution, it requires just about no maintenance and that's one of the other benefits of Auvik. With other solutions, we have spent more time updating and babysitting the servers and fixing our tools, instead of fixing our environment. That's a major plus.

What was our ROI?

When I was first evaluating it and we were going through pricing models, I was able to make the case that, for a team of five, this would be better than adding a person to the team when it comes to getting work done.

When I was new in this environment, I was trying to get a lot of stuff together. I brought Auvik as a solution to my supervisor and said, "This is what we used at my last company," and he was familiar with my last company. He viewed them as very good at what they do. I suggested we take a look at Auvik. As soon as he got the pricing during the first sales call around Auvik, he said, "Sold. Well worth that money." They didn't even have to finish the presentation. He saw what was being offered and he also based his decision on the fact that I'd used it before. The cost easily made it worth it in his mind for what it would provide to us.

What's my experience with pricing, setup cost, and licensing?

The pricing is fair for the value and time saved that you get out of it. The larger you go, the more sense it makes per device, because as you hit different pricing tiers, it becomes much more affordable per device.

Auvik is billed by network device. They've got a very clear-cut definition of what is a device and what isn't a device, and that's very convenient. Anything like a server, or a phone, or an access point, is not billed but they are still captured for data, which is very useful. Auvik is very upfront that the solution is not a good server monitoring platform, but it's a fair server monitoring platform and that comes along for free with everything else. My server guys have another system they use for monitoring servers, but they find being able to look at Auvik as well has been a huge value-add.

Which other solutions did I evaluate?

I have used LogicMonitor, PRTG, the N-central suite, the ManageEngine suite, and the SolarWinds products.

In terms of the differences between those solutions and Auvik, I would summarize them this way: Auvik is a tool built for the network guys, primarily, whereas a lot of other tools are built for the server guys first and then add in network. It's a tool really built for what I care about and it values my time. I'm able to get it put in fast, I'm able to use it fast, and my information is fast. It lets me do more with less.

What other advice do I have?

Definitely go through the proof of concept testing. The results speak for themselves. It's a fully rounded product and everyone I know who has used it has been happy with it.

When you're first deploying it, understand how you need to set up your locations. Otherwise, you're going to end up redoing work. If you're in a larger environment, you need a little bit of knowledge about where things are to be able to put stuff in the right places. If you're small, you can just drop it in and be super-happy with what it gives to you.

Overall, compared to everything else out there, it's a solid 10 out of 10. I haven't found anything that gives me what I need better.

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Director of IT at a computer software company with 201-500 employees
Real User
Top 10
Cloud-based, provides centralized visibility, and creates a backup of all configuration changes
Pros and Cons
  • "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."
  • "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."

What is our primary use case?

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.

How has it helped my organization?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

I have been using Auvik for about three months.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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.

How are customer service and support?

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.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

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.

What about the implementation team?

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.

What's my experience with pricing, setup cost, and licensing?

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.

Which other solutions did I evaluate?

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.

What other advice do I have?

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.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Flag as inappropriate
PeerSpot user
Charles Latham - PeerSpot reviewer
Centralized Services Lead at Affinity Tech Partners
Reseller
Configuration management and alerts are aspects of automation that result in less manual, repetitive effort
Pros and Cons
  • "The configuration management is the most valuable feature. I worked at an MSP before where they didn't have something collecting network device configurations. It was basically up to the technician who did it last, and you never knew if they saved a copy or not. Auvik makes that a lot more automated so we don't have to worry, if a device dies, that we don't know how it was configured."
  • "We have some clients that are rather large and the topology display can be a little bit of a mess. For smaller organizations, Auvik is perfect... But for some of our larger clients, the topology view is almost unusable."

What is our primary use case?

As an MSP, we monitor all of our clients with Auvik, specifically to monitor their network devices and connectivity, and to generate tickets. We also use it to back up configs for network devices, and it's where we get warranty information since we deal with life cycle management.

We can even push changes to devices through the terminal. Anytime there's a disaster, it's the first thing that we'll go to, to see what may be down or what may be inoperable. It's a really quick way of seeing what may be broken in a network. That's really handy. It's our network monitoring management go-to.

How has it helped my organization?

The configuration management has been a godsend. Every time something goes down, we don't have to worry about how it was configured. We're also getting alerts a lot faster. We have an RMM platform that's monitoring things, but it's a little slower to give us alerts and to give us data. Auvik is a lot faster and that's been really valuable. Both the configuration management and alerts are aspects of automation that result in less manual, repetitive effort.

If we're not wasting time checking configs and pushing documentation or mapping devices in a topology, that's time that we get back to do other things. The whole time I've worked here, we've had Auvik, so I don't really know this world without Auvik. But at my last MSP, those things took up a considerable amount of time, five to seven hours a week for me, at least, and probably the same for others. So it would be a considerable amount of time savings.

It also builds topologies automatically, so we don't have to go through Visio and hand-sketch something for every client. That would take a tremendous amount of time. Auvik does that for us and keeps it up to date every day.

And for what it does, Auvik gives us a single, integrated platform. Auvik is our source of truth for all network devices. We don't have anything else that overlaps with it. The amount of time it saves us is incalculable. If we were having to do this on different tools, or if we were having to manage things manually, it would take up a significant amount of our time. Not that managing things with Auvik doesn't take up a lot of time already, but it would take a lot more.

It is unified, automated and it's pretty concise. You don't have to dig around a lot to get to what you need, and that's really important. I was listening to one of the TruMethods guys and he was just talking about how many clicks it takes to get from your question to your answer. Auvik has a pretty concise depth to it.

Also, because we can drill into any one of our clients or any one site and get a very quick overview of what's going on, our team has good visibility into our networks. When a disaster happens, that visibility is crucial because it gives us a fast response time and faster mediation, which our clients love. Day-to-day, it can be important or not, but certainly, when everything's on fire, Auvik can be a real lifesaver.

We have virtual CIOs on our team who work with our clients and the fact that Auvik keeps device inventories up to date is invaluable for them. They can pull up warranty information and start plotting life cycle changes and let the client know, "Hey, we've got to replace all these devices over the next number of years." Having that data in a nice easy report saves a tremendous amount of time. And all of that information gets put into IT Glue, so we can easily search it or run reports from there on it.

As a result, we can communicate better with our clients. You don't want to just go to your client and say, "Hey, we need $50,000 so we can upgrade your equipment." What you want to do is say, "Hey, look at this report. Look at how old your stuff is. This is our plan for the next four quarters and how we're going to spend $50,000." That is gold. And delegating tasks to junior technicians is usually around procurement and projects to replace that equipment. That also wouldn't happen without that reporting.

In addition, having the device inventories up to date definitely saves us time. We don't have to wonder if something is still onsite or in the environment. It has a green check beside it so we know Auvik is checking in and we know it's online.

Another benefit is that it has helped us in reducing our resolution time by something like 15 percent.

What is most valuable?

The configuration management is the most valuable feature. I worked at an MSP before where they didn't have something collecting network device configurations. It was basically up to the technician who did it last, and you never knew if they saved a copy or not. Auvik makes that a lot more automated so we don't have to worry, if a device dies, that we don't know how it was configured. That's my favorite feature.

Ease of use is paramount for our organization. We have 15 technicians and everybody has to be able to get in there and work consistently. If it's not easy and we have to come up with all these rules on how to use it, there is a lot of room for people to make mistakes.

Auvik's network visualization is pretty intuitive. There's a legend right there and you can hover over any of those lines and it will give you the breakdown of the information. You can even click on any part of it and it takes you right to the device.

What needs improvement?

We have some clients that are rather large and the topology display can be a little bit of a mess. For smaller organizations, Auvik is perfect. You have your firewall, it connects to your switch, it connects to your LAN, it connects to your clients, and you're done. But for some of our larger clients, the topology view is almost unusable. I don't really know how to solve that. I don't know if you can.

I would like to see a better IT Glue integration in Auvik. With most platforms, when they dump something into IT Glue, it just shows up as a configuration. That is somewhat helpful, but it's not as robust as it would be if it filled in a flex asset for network details, or if it took that topology view and somehow pushed that into IT Glue as an image, for example. We try to treat IT Glue as our source of truth for documentation, and the better integration we can get from Auvik into IT Glue, the more we don't have to go logging in to everything to check everything.

For how long have I used the solution?

I have been using Auvik for about three years.

What do I think about the stability of the solution?

I get emails frequently about service interruptions, et cetera, but I don't experience them very often. I think a few weeks ago we had some collectors that started flaking out, but I'd seen the email, so I knew it wasn't a big deal. I do get those emails regularly, so it seems that they have problems frequently, but I don't experience them very often. Are they shooting themselves in the foot by letting me know? Probably. But at least they're being transparent.

What do I think about the scalability of the solution?

The amount of effort it takes to set up one client, when you have one client, is the exact amount of work it's going to take to set up one client when you have 100 clients. In that sense, it doesn't scale with the number of clients, but it's certainly much more scalable than doing it all manually.

We deploy it to every one of our 50 clients and about 2,200 endpoints, and that includes computers. We have configured every switch and firewall and WAP that we possibly can in Auvik for management. 

All of our technicians have access to it. Support uses it to troubleshoot network problems and our technical alignment team uses it to review standardizations. Our centralized services team uses it to make sure that we're backing up configs and that the devices are working correctly. BCIO will use it for life cycle management and phasing devices in and out. We deploy it to all of our clients because the value makes it worth it.

How are customer service and support?

I haven't had to use tech support very much. It's a pretty intuitive application. But the times I have had to contact them, I have usually done so with the chat so I can do other stuff. They always send me a knowledge base article and stick with me to make sure everything's working correctly. I have no complaints. It's been smooth.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

The only "solution" I used previously was "sweat equity." You can rely on Auvik a lot more. It takes some of the human error out of the equation. I can be forgetful, so I assume most people are. You can't be 100 percent all of the time, but Auvik can get a lot closer. It's a lot more reliable.

What was our ROI?

If you have a lot of clients already, there can be a lot of work to get everything into Auvik and fully turning. That being said, you can drop a collector and start discovering network devices really fast. When we onboard a client, I'll drop a collector and let it start scanning and then I'll go do something else. I'll come back 10 minutes later and it has a fully populated network scan. So you can get up and running pretty quickly with just the bare bones.

But to really get a lot of the benefit out of it could take some work to get all your clients in there and get everything integrated. You do have to touch every device and configure it to point to the collector or put in the right community string. There can be a little ramp-up time, but it's worth it.

What's my experience with pricing, setup cost, and licensing?

We have a lot of problems with licensing in many other solutions, but I've never run into a problem with Auvik licensing. That's a pretty good vote of confidence.

Which other solutions did I evaluate?

When comparing network monitoring solutions, if the concern is pricing, you need to factor in how much time the different solutions could potentially provide. If you can save 10 percent with this one and 40 percent with that one, but the last one costs a lot more, your time is valuable. You have to assess just how much easier it will be knowing you don't have to worry about something and how much more you can focus on other things. It becomes a cost-benefit analysis. 

Some of our clients are co-managed. They have technicians onsite who work for them and they work with us. One thing we do is give them access to Auvik and they just go crazy. They say, "Man, look at all these cool tools. You mean we get to have access to this?" Just being able to tunnel straight into a device within the Auvik portal saves a lot of time. I don't know if every network monitoring tool in that class can do that. There are a lot of features within Auvik that may not be present in others.

What other advice do I have?

It is about as easy as any other SNMP monitor when it comes to monitoring and management functions. Sometimes, it can get a little tricky to get stuff logged in and connected to the collector, but that's not on Auvik. That's just authentication and networks.

We've used Auvik to generate tickets to alert technicians to go and set up SNMP or to look at a particular alert. That's not really what we use it for, but we've gotten some benefit from that in the past. It's not crucial, but we've saved some time with it.

Every solution requires maintenance, even if it's just checking in and making sure things are working. But I don't think there are a lot of things that break that we have to fix, unless it's something that we've broken, like changing a password or changing a community string. The agents that we deploy are usually pretty solid. I don't recall having to reinstall an agent recently. So it doesn't require a lot of maintenance. It's mostly just the setup time to get everything integrated and get everything working.

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: MSP
Flag as inappropriate
PeerSpot user
Buyer's Guide
Download our free Auvik Report and get advice and tips from experienced pros sharing their opinions.
Updated: January 2023
Buyer's Guide
Download our free Auvik Report and get advice and tips from experienced pros sharing their opinions.