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?
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