What is our primary use case?
Auvik is our primary network management tool. We utilize it to ensure all systems and remote sites are seamlessly connected to our central office. While its core function is network management, we leverage its capabilities for deep-dive technical analysis when needed.
In our setup, Auvik itself is deployed in the cloud. I'm not sure if they have a hybrid or on-premises option available. However, we do require a collector, which is a virtual server we own. This server stores data that Auvik accesses for network management and discovery. If the collector goes down, Auvik won't be able to report any information to the cloud. Although I manage everything through the cloud interface, I never need to log into the collector itself.
How has it helped my organization?
The UI can be easily navigated by new users.
Auvik offers a network map for improved visibility. However, I'm unsure if our current setup allows us to take full advantage of this feature. While I can access the map, it sometimes displays inaccurate connections, with devices either incorrectly shown as connected or missing entirely. While my initial suspicion is a fault on our end, I believe the overall concept of the map is good and has potential.
Using the network map is easy. Auvik has a helpful key that explains what each line represents and what different devices look like on the map.
The network map provides full visibility without the need for other tools.
Auvik helps decrease our Mean Time to Resolution and allows us to spend less time on setup and issue resolution.
What is most valuable?
I like how Auvik gives us a quick overview of the overall situation. With a glance at the main page, we can see the most utilized sites, the overall bandwidth usage, and even identify the top bandwidth consumers. The color-coded map with green for online and red for offline sites is an intuitive way to get a high-level picture at a glance.
What needs improvement?
I requested that Auvik implement an alarm system to notify me immediately of any disruptions or anomalies. While email alerts are currently in place, I believe audible notifications would be more effective in attracting my attention.
I appreciate the notification that they're addressing the recent service outage. While I understand being kept informed, multiple emails for every impacted device seem excessive. It would be ideal if notifications were consolidated into a single update once the issue is resolved. Hopefully, they'll have it fixed soon.
For how long have I used the solution?
I have been using Auvik for one and a half years.
What do I think about the stability of the solution?
Overall, I'd rate Auvik's stability a solid nine out of ten. While occasional downtime is inevitable, they're smart about scheduling it for minimal impact - typically early Saturday mornings when most users are offline. Of course, like any technology, unforeseen issues can arise, but these are rare and Auvik keeps users well-informed throughout any downtime occurrences. Infrequent hiccups aside, Auvik has proven remarkably reliable.
What do I think about the scalability of the solution?
Auvik is very flexible and can scale to anything we have.
How are customer service and support?
The technical support has been able to resolve all our issues promptly.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
Previously, I used SolarWinds, which worked reasonably well. However, after experiencing a security breach, I decided to move on due to concerns about continued vulnerabilities. Although SolarWinds may have taken corrective measures since then, I opted for Auvik. My primary driver for this change was the map functionality. While SolarWinds displayed individual sites and color-coded lines depicting connectivity, highlighting downed circuits with red, Auvik's map features are tied to external providers like Leaflet or OpenStreetMap. This limits customization, preventing me from using my background image and manually connecting elements. While longitude and latitude coordinates are available, I find this approach less intuitive for my needs and potentially confusing for the general user base. Additionally, SolarWinds' technical support proved unhelpful after the breach, refusing to assist with resolving issues related to device recognition. This lack of support contrasted starkly with Auvik's customer service, which readily helped me ensure all my devices communicated seamlessly with the platform. The responsive customer service led me to switch to Auvik.
How was the initial setup?
The initial deployment with Auvik's support was straightforward. They provided clear guidance and assistance to get our systems up and running. While we assumed ownership gradually after mastering the basics, Auvik stayed readily available for ongoing support. Whenever we encountered hurdles during implementation, their tech team promptly cleared the roadblocks. To finalize the process, Auvik conducted a comprehensive review, ensuring everything functions flawlessly. The smooth deployment took a month with moderate effort, and it could have been significantly faster if needed. Me and my system admin completed the deployment.
What about the implementation team?
The implementation was completed in-house with the help of an Auvik technician.
What's my experience with pricing, setup cost, and licensing?
The initial offer was high, but I was able to negotiate it down. The final price is quite competitive compared to other options. Auvik offers a robust feature set that can be further expanded with add-ons. I'm particularly interested in their inventory asset program, which appeals to me because it conveniently bundles all the software we need. While I'm leaning towards adding it eventually, additional funding would be necessary. Furthermore, Auvik offers an optional "Traffic Insights" add-on that provides comprehensive data on all connected devices. It's important to note that these add-ons come at an additional cost on top of the basic Auvik license.
What other advice do I have?
I would rate Auvik a nine out of ten.
Network management can be a bit of a plunge. We dive in, test the waters, and then see if it works for us. We didn't fully grasp the benefits of Auvik until we had it up and running for about six months to truly understand its impact. One thing I've noticed in the past year or two since we adopted Auvik, is that they were initially rough around the edges on some things. But they've stepped up their game since then. Their upcoming release sounds particularly promising, especially for remote desktop functionality. We currently use other software for that, but Auvik's new feature will allow us to do it directly within their platform, which I'm excited about.
We were able to get Auvik up and running and see the value quicker than we did for SolarWinds.
Maintenance is occasionally necessary. If we add or remove devices, adjustments are required to ensure proper system recognition. However, when no changes are made, the system functions autonomously daily.
To avoid initial frustration, it's crucial to ensure proper device accountability and the ability to identify elements like SNMP. Verify everything is running as expected. Auvik's lack of visibility might stem from our recent router replacements and mass equipment installation within the past six months. It's important to remember that if our configuration isn't accurate, Auvik is not at fault. Therefore, having everything properly set up beforehand would be the best approach.
Which deployment model are you using for this solution?
Private 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.