Auvik Network Management (ANM) Reviews

We primarily use Auvik for network monitoring and occasionally to remotely access some devices. It helps us monitor clients with a multi-site setup. We can monitor the network and overall network connectivity. The configurations of the devices we monitor are synchronized into IT Glue for documentation.

Auvik was part of the company's toolset when I joined as an engineer, and we have been perfecting it. We had a couple of big clients when I started. Everybody was under one site even though there were multiple sites. There was a site-to-site VPN and more. For some projects I worked on, we got directions from Auvik's account managers on how to implement multi-site within Auvik properly. That helped us manage these individual sites efficiently without creating too much burden.

Auvik's alerts notify us about an outage before our clients call us, so we can tell them that we're already on it when they call to say their internet is down. It gives them a sense of comfort and trust. Auvik is also crucial for any troubleshooting. If a device is down and we can't get to it from one way, it's always helpful to have another look through Auvik to start troubleshooting from the outside.

The cloud-based platform gives us ready access to necessary information without the need to go through additional steps to remote into a client site. Otherwise, we would need to set up a secure tunnel through a site-to-site VPN. Auvik makes it more convenient. 

It's arguably a more significant security risk in some ways. However, from the perspective of a managed service provider, it's more accessible to have a single pane of view for all our clients from the cloud-based portal. The initial setup and configuration are more straightforward. You don't need to pick a server or use many resources aside from setting something up in the portal and installing the Auvik collector. It certainly simplifies things.

It increased our visibility into remote networks since we can't be everywhere simultaneously. We don't need to deploy separate tools internally, which reduces the workload. It helped us improve network visibility in conjunction with our other toolsets.

As a managed service provider, we have multiple clients, so it's crucial to have visibility into their networks and our own. We have Auvik set up to cover our critical infrastructure. When the tool is set up correctly, it hums along pretty well. We can relax and let Auvik do the monitoring and documentation. It can gather the information or at least confirm it. If something changes, Auvik can pick it up. It does a lot for us.

Auvik helps keep device inventories updated. We have a couple of toolsets. For example, we have remote monitoring and management agents on servers. Auvik and some other tools can update the documentation automatically if one of the engineers forgets to do it after we change something on a server, such as an IP address. It provides another check for us and a general reminder, "Hey, this was updated. You should update the documentation for it because it looks different."

I like the ability to remotely access devices securely. The multi-site setup has also been useful. Once we learned how to set that up, we could customize each site and push out common information like SNMP credentials from the parent site to other multi-sites. The automatic network layout is excellent, and the overall monitoring is also beneficial. 

Auvik's monitoring and management features are relatively easy to use, but it depends on what you work with daily. When I started, there were features I didn't know about until somebody told me, "Set it up this way, and you could just monitor the internet connection as a whole." I didn't know that existed until somebody showed me. The basics are easy enough, but the advanced features require some training. 

They added two-factor authentication to access some of these devices remotely. It was a significant step forward because someone with access to Auvik has a lot of power. 

The network visualization is nice. We have some large clients with many devices, so the initial visualization might be overwhelming, but we manage that pretty well. There are some devices that we don't need Auvik to monitor. We lower the noise from workstations and printers because we have a separate toolset for that. However, it does get a little cluttered when you have a lot of servers. It was just a matter of getting used to it. I don't know if any platform has figured out how to do that properly, but it's pretty intuitive.

The solution integrates with our ticketing and documentation system. We use Auvik as our primary network monitoring system and alert system if something goes down. It provides a lot of benefits by putting everything in one place. Having a single integrated platform simplifies the process of looking. We don't need to go to multiple vendors and look at everything or have several windows and applications open. We also use PRTG to provide network monitoring for some of our clients, and that's more on the internal side. Auvik is good at monitoring anything outward-facing.

There have been times when our SNMP community strings were incorrect or weren't updated for whatever reason, and Auvik kept trying to scan them. Changing it was a pain, and there wasn't a way to extract that from Auvik. I understand there are valid security reasons why we wouldn't want to do that sometimes. In those situations, we had to recreate those community strings and reapply them to various devices.

Maybe they could implement a way to do that securely. It could be restricted by the role a person has within the organization. For example, perhaps a junior engineer wouldn't have access, but it would be available to a supervisor, manager, administrator, or higher-up. 

I have been using Auvik for a little over a year.

I haven't heard any complaints about Auvik's stability or performance degradation. Auvik has scheduled maintenance windows, but they're transparent about when they will be. It hasn't impacted us. Reliability is crucial because Auvik is part of our service to our customers. We've had issues with a few vendors where they've gone down or had quality issues that affect our services and reflect poorly on us.

Scalability hasn't been an issue so far. There is one thing to keep in mind, and it's probably less of a scalability issue with Auvik itself. However, we've learned from working with large clients that having multiple Auvik collectors is best. It would be best if you strategized about how to distribute the collectors throughout your servers and put redundancies in place. 

I rate Auvik support a ten out of ten. The knowledge base articles are pretty thorough. Once, I had to look up how to confirm SNMP credentials or set up SNMPv3. Auvik's team is excellent. Our support and account managers have been responsive and helpful. 

I rate Auvik a ten out of ten. I recommend planning and going through the steps to evaluate this. It's a powerful tool with an extensive suite of features, and the support is there if needed. Auvik has good people working there. 

Going back to the SNMP portion, you need to plan how to design and implement the solution, especially if you have a multi-site situation or are monitoring many devices. You need to plan for scalability and collector distribution.

We use Auvik to manage our network devices and get alerts about what's happening on our systems. We've deployed it across our showroom office network. We have 140 devices.

We're discovering devices we weren't getting previously. For example, we can monitor printer status and be more aware of what's happening with our printers. It's given us visibility that we didn't have.

It's essential because we don't have a dedicated IT team to manage our network. In addition to our IT infrastructure, we need to monitor smart office devices like the cameras and ensure all our devices are online. The ability to monitor this is massively valuable for our potential clients and us. 

We plan to use Auvik to keep our device inventories updated, but I haven't set that up yet. However, it has already populated a list of devices we will keep up to date. We didn't have that list previously. 

The best feature is the ease of setup. Auvik immediately scans and finds everything. It automatically connects to multiple devices with a single set of credentials.

Managing the platform seems relatively easy. I've only used it for a few days, but it's far easier than the previous product we were using. It gives us a single integrated platform, which is crucial for our business model because we provide solutions for others. The network visualization makes rough sense. There are elements that I find tricky to get my head around, but I think might be because it's all new to me. 

I say it's fairly clear, but obviously, it needs me to spend a little bit more time maybe grouping things together and things like that to make sure we've got the correct devices that things are mapped incorrectly.

I'm still undergoing the trial period. My only complaint is that I still don't understand what the license cost will be. More transparent pricing would be massive. In terms of functionality, it's head and shoulders above our previous solution.

I have only been using Auvik for about a week.

Auvik seems more stable than our previous solution. 

The scalability seems good. I placed a collector on a relatively low-power machine, and it doesn't seem to be struggling on the network. Everything seems fine.

We previously used Domotz, but we switched because it required us to run a device on the network that took another device off the network for some reason. I began looking at other solutions to see if they all had this issue. I stumbled across Auvik and decided to try it out.

One of the issues we face is that some of our customers won't allow anything to leave the site, so it has to be on-prem. That's one reason we chose Domotz. However, that caused problems with our network. We prefer a cloud-based system on our network because I work remotely more often than not. On-prem and cloud solutions have advantages and drawbacks. Some customers need an on-prem solution, but I prefer a cloud-based one.

Deploying Auvik is straightforward, and I did it myself. You install the agent, add credentials, and click okay. After you deploy the collector, the network map populates in under a day. I deployed it in the evening, and everything was there the next day. 

When comparing prices, you should consider how long it will take to set up and configure. A cheaper option might not be completely deployed for months. We don't have tons of time to do these things. The most important aspect is how fast we can get it running. How good the software is, and how quickly we can start using it effectively.

There was no visibility prior to setting it up on pricing. Having set it up, their pricing seems fair. It's definitely more expensive than what we're paying at the moment.

I rate Auvik seven out of 10. It seems fairly simple so far, and we haven't had any issues. However, I haven't used it extensively enough. It's expensive, and it would need to be mind-blowing to justify the cost. 

My advice to future users is to ensure you get your credentials together before starting the setup.

I use it to monitor all the activities in our office, including printers and the internet. It gives notifications for each device.

As a single, integrated platform, it's easy to track all the devices in the office. That decreases the time it takes for people to work together to find a problem. In some ways, it improves efficiency. 

It keeps our internet safe and helps us to protect our data.

The monitoring is really good. It tells us when a printer is out of ink or paper, so we don't need to check it and can deal with the device as soon as possible. It also monitors the internet so that we know whether there is a virus or it is safe. It also backs up our files, which is good.

The topology map is good. It shows each device and whether it has a safe connection, how long it has been connected, and its activities. That's really helpful. Knowing the map helps our efficiency.

It also breaks down priorities, giving us much more time and space for priority jobs. Each day, Auvik saves us at least one to two hours.

Their system is a little difficult because it shows a lot of LANs and it's a little difficult to find each device. In our system, we have over 20 devices showing and it really takes a long time when I want to find a particular device. If it's easier to use, it will improve work efficiency.

I would like to see a much simpler platform so that we could learn it faster.

I have been using it for one month, on a trial basis. We have 12 users of the solution.

I tried another solution, but it was not very good. The functionality was too simple. Auvik provides more detail and more functionality.

The price of Auvik is okay. It is appropriate for the market.

I prefer a one-time cost and buying something once. I do not like to subscribe.

Auvik doesn't require any maintenance.

We use it for alerts, to a degree, but we mostly use it for networking, monitoring, and triage.

Originally, what really was good about this particular solution was its ability to give us an alert, should something be down, based on simple networking such as pinging. There are a lot of other solutions out there now, but Auvik was, originally, the main source of our networking alerts and it automatically gave us tickets so that we could triage issues.

In a specific service situation where we have a failure, Auvik can save us a lot of time because it can remotely give us a picture of where the communications have stopped in an environment. It gives us the opportunity to put the eyes of a more senior team member on it, someone who is more experienced in networking, to assist somebody who is onsite to determine where the problem is likely to be occurring so that they can solve it much quicker. Many hours are saved for a higher-tier technician because they don't have to be physically onsite. They can use this utility to assist somebody who is there and helps reduce our MTTR.

Another benefit is the reduction in time spent doing repetitive or low-priority tasks, thanks to the automation. By also alerting us when an issue has self-resolved, it saves us the time of triaging an issue when it's not necessary to investigate it. It's helped us be more proactive, and at the same time, has given us an overview of things that have self-resolved.

The visibility we get is vital to my team. Any type of clarity, communication—even background monitoring—are all important. There are a lot of other tools, including SIEM and monitoring tools for networking, that are more advanced and have a better outlook on what's going on. But all the communication, information, and metrics are important for us to get a better picture, even when we're looking back to try to figure out client stability and hardware needs.

And Auvik has probably had an effect on our IT team's availability by helping us know about a client's problem and enabling a proactive approach to resolving it. If, for example, something is going up and down, up and down, we will get an indication of that via the alert system and the way it notifies our ticketing system, giving us trends. That gives us the opportunity to be proactive because we can resolve a problem before it becomes a complete outage.

When you have the alerting set up properly and you have the integration set up properly with a ticketing system, the end result is that, if you have a service desk triage team to determine who gets assigned a ticket based on the criticality of the situation, everything works together. The alerts notify us by creating a ticket. A ticket is then triaged by my service desk team, and they send it to a responding team. Human interaction is necessary in our design, but it does help that Auvik has a lot of automation in it.

Port mapping is probably the most vital purpose that I use it for. My team has a lot of different needs and they will use it for monitoring server performance issues and the like. But the most important functionality for me, over the years, has been port mapping when I'm trying to figure out where a network has stopped responding.

And as an MSP, we have an overall client management portal through Auvik, so we can get to everything from one spot. That's important when we are looking at solutions for clients, giving us some sort of unified reporting and access to clientele.

It's also pretty good when it comes to visualizing network topology if you take the time to manually make sure the access to individual hardware is configured. On an automated level, it helps to some degree, even for sites that are not fully configured or maintained. It's pretty helpful. And from an experienced-networking-engineer standpoint, the intuitiveness of the visibility is pretty good. From what I've seen from my entry-level technicians, their first response is that it's a bit confusing. But I don't think this is really an entry-level program.

It requires a lot of hands-on maintenance when it comes to cleanup. That's probably the biggest problem I've had because I don't have a dedicated resource to manually clean up stale records. I have a customer where it shows 4,000 devices because of the duplication of devices that I have to clean up.

I have recently found that the way that they bill, based on what they detect and what you're managing, is not self-cleaning. It requires that somebody intervene to resolve that. I'm a little challenged with the cleanup of devices for a client and the need to manually maintain it. A lot of manual cleanup is necessary.

We have been using Auvik for over five years.

I don't think I've had any outages with Auvik. I have to give it a 10 out of 10 for stability.

It has the ability to scale, but with the number of billable and managed products in mind, and the fact that it takes so much manual cleanup to get it properly situated for a larger client, I would knock the scalability down to about a seven out of 10. We have to manually figure out the billable devices and manually clean up configurations all the time, making it less scalable.

We deploy it to any client that has advanced networking. If they have multiple sites, that's where the design is most effective: larger clients that have multiple sites, even a dozen sites. We utilize it for networking that has switched stacks or multiple locations.

The communication with their technical support has been pretty solid. They usually respond quickly.

Positive

When it comes down to it, sometimes we require direct access to networks. We used other utilities like N-able products. Other types of programs like that would be useful. Otherwise, you're doing port scanning, either from the switches themselves or from third-party utilities on individual sites, from whatever server or access you have to the site. It's much better in that respect.

Prior to N-able, we used basic utilities, launched individually at customer locations, such as Nmap and Wireshark, where we were looking for network activity and details. All of them were manual applications that were installed and run at the time of need, instead of automated reporting.

I don't know why we moved to Auvik specifically, but we review products regularly. We probably had a presentation by the vendor and then there was agreement that it was the best way to move forward. But we utilize it at the same time that we use many other products for network monitoring.

If Auvik is properly manually managed by my team, there is value from it. If it's just left to run and not manually configured, monitored, or adjusted, then we don't see value from it.

From a client perspective, pricing is always an issue. Nobody wants to pay more than necessary. You need to be aware of the number of billable managed products, because they will greatly increase the cost of Auvik, based on your clientele and what you're managing.

I don't think pricing and licensing are communicated well by the Auvik team, as far as billable products go, until you get the bill. Once you get the bill and you realize you're being monitored for a bunch of things you didn't necessarily want to manage or control, you then have to take the time to manually reduce those managed products so that they're not part of your cost. It's clunky and not quite what I had hoped for.

Overall, I think it's been much better than other utilities I've used previously as far as giving me an overview of switch stacks, switch connectivity, and access to networking.

Maintenance is very manual. It's not the agents that require installation updates, it's the general interface. The configurations, or the inventory, have to be cleaned up manually and that's a lot of work.

My advice would be to keep an eye on billable products, most importantly, and be prepared to assign a resource who is dedicated to cleanup and configuration.

We use Auvik to create a graphical representation of our network. It's easier to trace issues when we know what's connected at a glance. Auvik gives us alerts when a device goes offline, and we use Auvik to identify the place in the network path where the issue lies. Was it a core switch? A downstream switch? Was it not a switch at all?

Auvik makes troubleshooting more manageable and the workflow smoother. When troubleshooting an outage or a node that went down, we can immediately identify the problem. It reduces the time we spend troubleshooting, allowing us to spend more time on other tasks, which is a roundabout way of saying it makes us more efficient. I'd estimate that it reduces the time we spend on these tasks by about 30 percent. 

Troubleshooting is just like anything else. You always focus on the tools you use the most or the ones that are the most effective. Auvik is one of the top two we use for specific issues, namely network outages or known downs.

Auvik improves our visibility into your remote and distributed networks. It provides quick visualization, so we don't need to log into any individual switches. We can do everything through Auvik, especially port tracing. We need to see what device is connected to which port. This can be easily done within Auvik.

It also helps us delegate tasks within our IT team. As soon as we locate where an outage lies, we can instantly determine whether it needs to go to a low-level technician or a higher one based on what we see on the network map or alert that Auvik triggers.

It doesn't automatically keep our network inventories up to date because we still need to enable SNMP on the device. But once it's in the inventory, it's easy to manage with the existing devices we already have.

A cloud-based solution reduces our hardware costs because we don't need to deploy a VM for monitoring. Also, we're a managed service provider, so we would have to have an on-prem solution for each client, which would be cost-prohibitive.

I like Auvik's alerts. We can configure the alerts for a specific timeframe, i.e., we can set it to alert us when devices have been offline for a specific amount of minutes. If a device or port is flapping, we can ignore it or allow only the first alert to come in and mute the subsequent alerts.

The monitoring and management are quite straightforward. I rate it nine out of 10 for intuitiveness. During onboarding, we went through how to set everything up. It's a set-it-and-forget-it solution, and we can use templates to move forward with other devices that we add based on our documentation.

Auvik is one of our go-to solutions, depending on the issue. If we see a device go down, we usually get an alert from Auvik or our RMM solution. Auvik lets us trace graphically to know where the issue could lie, reducing the amount of troubleshooting we have to do.

It's a single platform but isn't integrated with anything besides our PSA. I don't think it needs to integrate with anything else other than our ticketing solution. 

Auvik could be more customizable. Also, the network map isn't as clear as it could be. I don't know if it's even possible, but it would be nice if Auvik could pick up on dumb switches. I don't know if that's possible based on SNMP, but if they can figure out a way to do that, it would make our life much easier.

Our organization has been using Auvik for about a year.

We've never had any downtime outside of their regular maintenance windows. They always notify us in advance when there will be maintenance. Even when they're down for maintenance, it's after hours, so we don't notice. 

Scaling Auvik is pretty simple. We just activate SNMP, put the credentials in devices, and we're set once the Auvik collectors are in place.

I'd rate Auvik support seven out of 10. We haven't needed to reach out to them much. I can only recall around three or four times in the past year that we contacted them. They've been pretty good. We have only used web-based support, not phone support. 

Neutral

We were using Nagios, but it was getting too pricey. Nagios also provided more information than we needed. Auvik provides SNMP, which is fine for our purposes. With Nagios, we had to install agents on each node to recognize it. If we could activate SNMP, we'd get more reporting from Nagios when we install the agent, but it wasn't intuitive how to do that. 

Once it was slotted in place, there wasn't much of a learning curve at all, so we saw an ROI right away.

We looked at Zabbix. Zabbix had a free tier, but it had absolutely no support. We went with Auvik because of their support.

I rate Auvik nine out of 10. If you want simplicity, Auvik is probably the way to go.

Zabbix has a free tool, but their paid solution is actually quite expensive.

Auvik is our monitoring solution; we're an MSP, so we use it to monitor multiple medium-sized enterprise clients. It's primarily used by the network team, though other teams log on occasionally. We have five users in our company. 

Auvik helps us manage our clients better, and it's all from one web page, so we can switch between clients easily without having to log into different systems. We can also remotely access their networks, which is handy. 

We previously used multiple solutions for managing our networks and switching to Auvik resulted in time savings of approximately 20%.  

Auvik increased our IT team's availability, especially as we can look into issues remotely and from our phones if we're away from a PC. All our teammates can log into a webpage instead of installing applications on their computers, which is nice from an availability point of view. We have seen time savings in the area of 10%. 

The solution helps us delegate low-level tasks to junior staff; we send alerts to our NOC team, and they help triage some of the lower-level ones. If they can't resolve it, they escalate it to us. The delegation capability is essential, as it saves us a lot of time.   

Auvik helps keep device inventories up-to-date; we can set it to scan the network, and the information updates automatically. It saves about 30% of our time.

The solution keeping device inventories up-to-date helps our teams focus on high-value tasks and delegate low-level tasks to junior staff.   

The best features are the alerting and monitoring. 

Using Auvik, we can remotely access our clients' devices or networks, which is an excellent feature.

The solution also allows us to do backups, check usage, and do SNMP polling for device statistics all in one pane of glass, which is nice.

Auvik's monitoring and managing functions are easy to use, especially as I did some webinars. We need the service, so ease of use is critical.  

Auvik provides a single integrated platform. 

Auvik provides a basic network map, and as long as everything is working correctly, it draws a little topology table, which is a nice feature. 

Auvik helps to reduce repetitive, low-priority tasks through automation, primarily our backups, as that's a repetitive task. From a backup point of view, the solution handles everything, and we only need to verify once in a while, so we have time savings of 90% in this area.   

I want to see improvement around backups; we had a case where we created a ticket for online support, and they were able to set up backups for one of our devices, but they were unwilling to do the same backup script with a different device. The script uses the same code, just a different model number, and the engineers weren't willing to add it to the other model.

We've been using Auvik for about a year. 

Auvik is a stable platform. 

Auvik is scalable, though we have one client with many devices, and it can sometimes be slow to load some of the data.

The technical support is excellent; I've logged several tickets with them, and they always resolved my issues.

Positive

The company previously used an in-house system, but that was before my time. Auvik has been in place since my arrival. 

I wasn't involved in the deployment, and the product doesn't require any maintenance on our end, as Auvik Networks Inc. handles that in the cloud. 

I don't have any insight into the cost, as another department handles that.

I rate the solution eight out of ten. 

To someone comparing network monitoring solutions but concerned about pricing, I'd say Auvik is a good solution, and I recommend it.

Comparing Auvik's cloud-based solution versus on-prem network monitoring solutions, cloud-based is more straightforward and always available, so I prefer it over an on-prem tool.   

Our visibility into remote and distributed networks is about the same as before.

I advise anyone evaluating Auvik to try their POC, as it's straightforward to install and get working.

We needed a solution to monitor all of our systems. We were using another system, but it wasn't up to par. Auvik gives us everything we need plus some. Right now, we're using it to monitor all of our virtual machines and switches. We can do configurations on any of our switches directly through Auvik.

Right now, another engineer and I currently use the solution. We're going to allow other IT staff to view it, but nobody else will have access. There will be another five staff members who will see all of the data.

We're able to have a visual dashboard in one central location, so we don't need to have multiple dashboards. If we're going to configure an API, we can have it displayed on a board for our team to see. We didn't have anything like that before, so the ability to see insights on a dashboard is very important to our organization.

Auvik has saved us 50% of the time we used to spend because we get notifications fairly quickly.

We have seen a reduction in our MTTR. We notice that some of our devices are going offline five minutes sooner per incident than when we would first get reports.

The most valuable feature is the ability to see usage alerts on all of our devices. That's not just from our servers, but on all of our machines and user computers.

The ability to see utilization at one central location is easier than having multiple windows. We couldn't configure alerts on everything because it just wasn't available. Auvik provided the solution for us.

The use of the monitoring and management functions is of a medium difficulty level. With some aspects like trying to filter devices, it's a little cumbersome to type in the product. You have to click and apply it like a filter. When you click on the search button, it automatically populates it. It's a different step, so it's a little cumbersome and slow. The interface is quite slow, but that's likely due to it being on the cloud.

Auvik provides a single integrated platform. It's very important for us to have a single integrated platform because the interface shows us everything: all of our interfaces, switches, servers, and virtual machines. We can see it all in one central location instead of needing to pull up multiple windows.

Auvik helps us visualize the network mapping and topology for our organization. The ability to see all of our switches and what's connected to the switches is very helpful for us because not only can we see the device, but sometimes we can even see the device name. When we have an issue, we don't have to try to find it with an IP because we can already see the name of the device.

The solution helps reduce repetitive, low-priority tasks through automation. There are certain tasks that we know are repetitive, and we can't do anything because of the way that the system is built. We can suppress those unless they are over a certain threshold. There are other notifications that we always look at when they pop up.

The user interface could be a little bit faster, and there should be a legend on the map. Trying to filter devices could be easier. Those are probably the top three improvements I would like them to address.

I would rate the overall intuitiveness of the network visualization an eight out of ten. There are some aspects that could be better mapped out or better described. Some connections are confusing to look at. We don't know why one is yellow and why one is blue. It would be nice to have a legend included on the map.

I have worked with Auvik for about two and a half months.

The stability is top-notch.

It's highly scalable and available because it's on the cloud. As long as the correct configuration is done, it's highly available.

Technical support is very good. Our questions were answered right away. It seemed like they already knew what we were going to ask. Maybe they were just judging the situation by the deployments that they've done.

I would rate technical support as ten out of ten. 

Positive

We used Libre, but it wasn't giving us what we needed. Auvik gives us the ability to monitor the network.

The setup was straightforward. We implemented Auvik out-of-the-box. It was immediately available to use. The moment we connected our entire network, it was up. There were some configurations that we had to do on the backend, but it was pretty straightforward. The moment we connected, it was immediately available.

We required two people for deployment, including an engineer and myself. Our responsibilities were to make sure that our credentials were correct, our host was the correct address, and that we could connect to it. We also made sure that certain settings were turned on.

It doesn't require maintenance primarily because it's on the cloud, so Auvik takes care of that. If there was any maintenance, it would just be with our devices on our end.

Auvik is fairly priced. The cost is what we expected considering network management. The benefits outweigh the cost for us.

We evaluated other options, but they didn't offer what we needed.

I would rate this solution an eight and a half out of ten. 

Comparing Auvik's cloud-based solution to an on-premises network monitoring solution, I would rate the usefulness a ten out of ten. I would rate the interface an eight out of ten. I would rate the speed a six out of ten because when it's local and on-premises, it's faster because it doesn't have to go through the cloud or through Amazon.

The benefit outweighs the cost because we're able to see everything in one central location. It gives us one interface to do multiple functions.

The time it took to set up and maintain Auvik was twice as long as our previous network. With our previous solution, we just connected our devices and that was it. Auvik took a lot more time.

It is used for network monitoring.

Auvik hasn't really improved things for us. We tried Auvik, but it didn't meet our needs.

I found the ease of setup to be a helpful feature. The appliance was quite quick to get running. The fact that Auvik is a cloud-based solution, as opposed to an on-prem solution, meant there was one less thing to worry about. I didn't have to configure another device or provision a server and support it myself. It was easier having it supported by someone else.

The interface is also quite nice. Another part that is very easy to use is the monitoring and management functions. Ease of use is awesome.

The overall intuitiveness of the visualization was very good.

I require the monitoring of Linux devices and it doesn't support them. Although we've done a trial, we're not going to carry on with it. We've already gone with another product.

Also, seeing the topology is quite useful, but it's not really suitable for a large enterprise.

It also wasn't able to inventory everything. We're using Lansweeper, which pulls the serial of every single IP device, but Auvik only seemed to be interested in SNMP. It didn't care about non-SNMP devices. The solution needs to move past just having SNMP. If it could have other ways, like an agent, that would make things easier. The lack of being able to communicate with non-SNMP devices was the issue.

I used Auvik as a trial for a couple of weeks.

It was very stable. There were no outages that I was aware of.

Because it's cloud-based, it scales almost infinitely.

I didn't need to contact their technical support. The documentation was quite good. It was quite easy to get going.

Our current product was out-of-support, so we were looking for alternatives.

The initial deployment was very easy. We used the VMware template. It took under an hour after the collector was implemented for the network to start to populate. The actual deployment took about 20 minutes.

We deployed it in a test network. Obviously, we were not going to let an unknown product loose on the entire enterprise network.

It was just me involved in the deployment and there was no maintenance required.

If you're a small company, Auvik is probably quite reasonable. But we've got 500 servers, so pricing suddenly became a lot more of an issue. There needs to be better bulk pricing for it.

We evaluated Nagios and Spiceworks as well. We decided to try out Auvik because we were looking around and wanted to try everything we could.

Make sure that all your devices are SNMP-capable before implementing it.

Auvik was quite good at what it did, which is monitoring SNMP devices, but it didn't have enough there to monitor an IP generic device. If it wasn't SNMP, it didn't really work. It needs more agents and more monitoring methods.