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