SolarWinds NPM Reviews

The primary use case of this solution is for network monitoring.

The biggest thing for me is that it provides enough information for me to monitor. It alerts and provides you with the information that you need.

SolarWinds is one of those tools that work across the spectrum with different products, such as Cisco HP.

It is very customizable. I am quite happy with what it gives me.

I can say that SolarWinds is good on the market, but it's also expensive. The price is an issue.

It would be nice to have the device tracking software as part of the Network Monitoring suite. If you go with Spiceworks, which a free shareware product, they will give you all of that type of information. They will tell you that this is all of the features you have and this is what is up and what is down, and they will tell you if the device is a laptop or if this computer is plugged into this port, which is handy. SolarWinds has that tool, but it's an additional license.

Sometimes there are issues when upgrading to a new version of the product.

The market is always changing, but one thing that would add value would be analytics. Many put that into a SIEM-type solution, but from a network point of view, if I had analytics on my network to expand with then it would be helpful. I would say normally this port does this much traffic and over the last six months it's doing that much traffic, and then all of a sudden, today, it's doing an amount that isn't normal. It means that something is wrong in your environment and you can start an investigation.

When you are dealing with a large network, there is a lot of information coming through. If you had a system that did some sort of analysis and collating of information into smaller blocks, you could quickly look at a dashboard and say these are ten points I need to go and look at because these are things that are not 100% correct in the environment.

I have been using SolarWinds for about ten years.

We have four or five users, and we have approximately 150 devices that it's monitoring.

I have contacted technical support once or twice. I logged a ticket and they responded quite promptly, and they tried to help me with it.

The only time that I have had any issues was when I was upgrading. I had one surprise in my ten year period. When I upgraded to a new version of the product, the upgrade failed. It leaves you in a position where you can't go forward and you can't go backward. You're stuck. You almost have to reinstall it from fresh and start over, which is not a great point to work from. You would like to keep all of the history and information that you have built.

It's expensive and there are costs in addition to the standard licensing.

They have additional modules, for instance. They have a device tracking software that is an extra module. It tells you which device is connected to which port on your switch. It's a module that you have to pay extra for, at about $2,000.00 to $3,000.00.

It becomes expensive when you add all of these modules, just trying to do work with basic network tools.

We don't have any plans to increase usage in the future, but we do have some additional plans on providing it as a service to other companies. That said, I don't think that we will be changing anytime soon.

I have recommended this product more than once. It's one of the better products on the market, and it also has an extensive suite.

If people are looking for network monitoring software, and are willing to pay for it, and don't want a free version, I have always said that SolarWinds is one of the better options.

I think that there is room for improvement. I have seen other products that do similar, where some elements are better and some are worse. I think that it's a good all-round product, but it can be better.

I would rate this solution a seven out of ten.

The primary use case is to to know what nodes or devices are up or down in our environment. I can also provide a performance report, if needed to anyone who asks, by pulling it out from SolarWinds NPM. We have it integrated with other SolarWinds products, like NDM.

I have been using the solution for the last seven years. The company has been using the solution for over nine years now.

This solution provides us with proactive reports.

We use it to understand our historical reports, since we keep these reports for 365 days per our compliance requirements. We can proactively fix historical issues, so we won't face those problems in future.

At this moment, we are facing some problem with Zoom and our web content sync. We are having trouble with the quality of our user experience. A lot of users are reporting that their calls and screen shares are getting disconnected, and it is happening very frequently. Therefore, I would like to monitor the Zoom application from SolarWinds NPM. Unfortunately, it doesn't have this capability right now, and I had to find another application for this.

We would like a single application from SolarWinds that incorporates all their products.

It is not that stable. As a Windows software, I have seen issues with SolarWinds. While it is very flexible, and you can do lots of things with the SolarWinds, the down side is that the product can be unusable. Also, sometimes, the performance is slow. In comparison, I have tested some Unix-based applications, which are very quick. However, SolarWinds is Windows-based, so we are seeing a lot of performance issues.

The scalability is good.

A number of times, I have contacted SolarWinds technical support. Depending the issue, sometimes they will just ask me for the diagnostic. However, if we call support for critical issues, we expect immediate solutions. However, sometimes in these cases, they still just ask us for the diagnostic report and tell us that they'll get back to us within 12 to 24 hours. But, if we are in the critical state, we need to answer to our management about what is happening. We cannot wait 24 hours. That is too much time for us. There are times that they do resolve issues quickly. Therefore, sometimes they are good, and sometimes they are bad.

We used to be on NetIQ, but were scaling very fast. This product was very scalable and flexible, which is why we went for it.

The initial setup was straightforward, not complex.

The pricing needs to be improved. It is too high. One full engine costs around $10 000, which is why we don't have high availability right now.

We are currently exploring New Relic as an alternative product. The Zoom monitoring issue is one of the reasons that we are looking at New Relic and willing to pay their higher price.

The most important criteria when selecting a vendor are support and flexibility.

• Ease of use
• Ease of training for others
• Good reporting
• Nice dashboard customization options
• Good map building capabilities
• Good integration with other SolarWinds tools to provide a “single pane of glass”
• Great support
• Great online community, “Thwack”

We were able to unify our entire company under one monitoring solution that works for everybody, saving a ton of time and significantly speeding up problem-resolution time.

• More automation around node additions and management

With regard to this I am looking for a faster way to add nodes. Currently we deploy nodes in bulk into different environments for our clients and having the ability to have monitoring deploy equally fast would be helpful versus having to spend a significant amount of time manually adding each system. I did recently open a Feature Request for this HERE

• Adding multi-tenancy into the product

We are a hosting provider and we give our clients access to Orion to see their nodes. Orion is not a multi-tenancy platform by design so I am continually challenged to provide clients access in a way that limits them to only see their stuff. In a more true multi-tenancy platform, it would be easy to choose what a client sees and what they don’t and not have to worry if there is a way to work around or break free of the limitations.

• Providing more monitoring capabilities for public cloud such as Azure, AWS, etc.

We are a Hybrid Cloud service provider and we work very closely with Microsoft and Azure. Currently, I am able to monitor nodes in Azure just fine, but I don’t have a good way to monitor PaaS based services.

I have used it for about 10 years.

There have been some versions that have had stability issues, but the current version seems pretty stable.

Technical support is fantastic.

We previously used HPE OpenView, OpenNMS and Zenoss.

The initial setup is very straightforward; you can have it running in about an hour.

Compared to other solutions on the market, the pricing is very good. The licensing is a bit confusing, though.

We evaluated:

• OpenNMS
• ScienceLogic EM7
• Ipswitch WhatsUp Gold
• A few others that either no longer exist or were consumed by other companies

Take advantage of their free, 30-day demo.

Definitely leverage the online community, “Thwack”.

SolarWinds NPM is used for searching equipment in the network, troubleshooting the network, and mapping the networking.

The most valuable features in SolarWinds NPM are the network search and diagnostic tools.

SolarWinds NPM could improve by adding the deepest inspection, performance networking, and IP address discovery.

I have been using SolarWinds NPM for approximately three months.

SolarWinds NPM is stable.

The scalability of SolarWinds NPM is easy to do.

We have three or four users using this solution.

The support is very good for SolarWinds NPM.

The initial setup of SolarWinds NPM is easy.

The cost of the personal perpetual license for SolarWinds NPM is approximately $2,000.

I recommend this solution to others.

I rate SolarWinds NPM a nine out of ten.

We use SolarWinds NPM for monitoring. We don't change anything, and we just look at it.

I like the tracking feature to track devices and see where they are connected. This is very practical.

The console could be more user-friendly. It would be better if SolarWinds updated the user interface.

I have worked with SolarWinds NPM for two or three years. 

SolarWinds NPM is a stable solution.

SolarWinds NPM is a scalable solution, but it costs a lot. As long as you pay, you can scale it as much as you like.

Technical support is quite efficient, but they have to be a little more responsive.

On a scale from one to five, I'll give them at least four.

Positive

The initial setup was quite complex and took a while. You need an engineer to install the solution and the database and configure everything. We have only two people accessing and maintaining SolarWinds.

We had a contractor implement this solution.

I did a proof of concept with ManageEngine. The functionalities are similar, but the ManageEngine interface is way more user-friendly.

On a scale from one to ten, I would give SolarWinds NPM a seven.

The most valuable feature is the way it monitors the environment, and how user-friendly the console is for the end-user. The interface is also very easy and it captures all the information very well.

This product could improve by adding cloud monitoring. I want SolarWinds NPM to do much more integration, and have more involvement in cloud monitoring, like AWS or Google, or Azure. I feel like it requires lots of improvement for cloud monitoring in NPM.

I've been working with this product for almost ten years.

The support could be improved. Within the last two, three years, I would say the support has declined. It has degraded, but not that bad. We are still getting solutions, but sometimes, calls stay on hold. When we try to call the support team, it continues to ring on their side. About half of the time it gets connected very quickly, but the other half takes some time to connect. Sometimes I wait more than 10 minutes. It's not totally bad, as we are still getting support. Nowadays, we prefer to send emails to them, so whenever they have someone available, they can revert back to us and we can schedule a call with them.

The pricing is reasonable. In the last year we tried to look for different applications and those other applications are even more expensive. 

If someone wants to install this application, they need to be very specific what environment they want to monitor, whether they want to monitor in a hybrid environment or just cloud, or just on prem, because the setup is going to be quite different in all aspects. When it comes to installation, someone has to have a better understanding of what they're actually going to monitor, how many nodes they are going to monitor, how many network device they are going to monitor, etc. With respect to that, the licensing changes.

I would rate SolarWinds NPM an eight out of ten.

My team uses SolarWinds to do some of the network monitoring. I look at the reports.

One of the challenges with SolarWinds is that in order to pull the data, we have to have a lot of false positives.

False positives or positive falses are a concern because you want to be as accurate as possible and get them down to zero, which is what you want on your network. Once a week with the reports there, is always a false positive or vice versa where it's showing that it's up and really it's down.

We are looking at how we can overcome that issue. Is it a work issue, or does it come from the tool itself? It will show that something is down when it's up and every once in a while if something is down it shows that it is still up.

We would like to be able to pull information from the vendor's OEM. It would be helpful to have crosswalks or if it could have a running list that goes out of models, software, and it can pull out the end of life, or end of service life dates. Also to suggest the recommend current version to use, that way you can do the comparisons without having to do a manual search. That would be beneficial.

Similar to other tools, I would also like to see a graphical map of your network that highlight in green, red, or yellow, and if you see a specific device you can click on it and it will help you drill down on the details of that device.

There are other things that it should be able to do, such as when it comes to monitoring the infrastructure and my server, and there are issues developing like the circuits degrading or latency is increasing it should give you a notification to know what is going on, rather waiting for the device to go down which at that point it would be too late. You want to be able to do proactive monitoring and reaction.

We want to get to a monitoring level where if it is monitoring the server, the CPU, or the storage level you could have presets where it will identify and give you warnings to say that you are at 70% or 80% storage capacity. This would allow you to get ahead of it before you run out. 

It would be the same for the CPU utilization and knowing if it is running 20 or 30% premiums normally or is it running at 90 or 100% and you have to add CPUs.

It could let you know if you have other tools or applications that are running too hot or if they need to be changing out that tool or is it something else.

To have something in place where it can help us to do some analysis and be proactive would be helpful.

I don't use this solution, I oversee a team who uses it.

We don't have any issues with the stability of SolarWinds NPM. 

We had one problem, but it wasn't a stability issue, it was a hack that occurred earlier this year that affected everyone using SolarWinds. After that, it took a bit to get it stabilized to where it is now. 

Our team that has worked with technical support hasn't had any complaints. It goes pretty well. 

I am familiar with several tools.

They will be putting NetScout on their network to look at some of the differences and to look at the pluses and minuses of each of the two tools.

I would rate SolarWinds an eight out of ten.

In my opinion, one of the most valuable features of this product is the level of customization. From web interfaces to custom monitors and alarms, this product has a high level of flexibility that can be molded to suit your business needs, regardless of the size of your organization.

It has helped to provide a user friendly interface for support to drill down and see where the issue lies and remediate issues quickly. We have other solutions that might have features NPM does not but the front end could look confusing to an inexperienced user. With NPM, we are able to fine-tune what the support accounts look like so users only see the things they need to do their jobs effectively.

Better offline license management. I’ve had to get in touch with customer support several times simply to remove an expired license from our NPM servers (which have no connection to the public internet). Also, if you add a new license and don’t remove the old one first, NPM will recognize only the expired one and ignore the new one, which prompts an additional call to support.

Personally I have been actively using this product for a little over a year but our organization has been using NPM for many years.

We had some issues with getting failover polling engines working properly and were forced to abandon the effort. So we’re currently backing up data to a warehouse database but we currently don’t have any redundancy with our polling engines.

On the whole, NPM is a very stable product. Occasionally, we might have a poller that stops communicating with the mother ship but usually a little bit of basic troubleshooting is able to resolve the issue with minimal downtime.

This is one of the strengths of NPM. As our infrastructure grows, NPM is able to grow organically to accommodate it. Scalability is as simple as spinning up another VM, installing the product, and ensuring connectivity to the primary instance of NPM.

Customer service at SolarWinds is great. I have had several issues in the past and they were prompt, helpful, and were able to resolve these issues quickly. SolarWinds also cares about what their customers want from a network monitoring standpoint. Rather than release a new version and hope that this is what customers want, they hold regular sessions to show customers what they’re currently working on and can fine tune future releases of NPM based on the feedback.

As a company, SolarWinds goes out of its way to put a human face to their technical support staff. The main way they’ve accomplished this is by creating a community out of their customer base. Using their forum, Thwack, customers are able to interact with SolarWinds staff from numerous departments, including from support, development and marketing. I’ve been a member a short while and I’ve already been blown away with how tight knit this forum can be.

The initial setup is very straightforward. It’s installed via a wizard and walks you through the steps, installing the extras it needs to function along the way. Then, it’s just a matter of activating your license and configuring the front end web page to look the way you want it. Most of the complexity of the initial setup and configuration is from custom modifications done by us on the back end. We had to modify the database to get NPM to hook into our in-house alert management system. But, for other companies' environments where this level of customization is not needed, NPM has an excellent amount of alerting methods that work right out of the box.

We do all of our NPM implementations using an in-house team. I am one of the engineers responsible for setting up new environments when new data centers come online. I’m not sure if SolarWinds has vendor teams available that can do this function but as I’ve stated, NPM is designed to be unboxed and up and running in an hour or less depending on how much customization is needed.

Due to the large size and scope of our organization, our cost of using this product is comparatively high. Excluding the costs of running VMs and physical blade servers, our licensing costs run around US$200,000/year for over 60 polling engines. Pricing differs if the NPM server is a primary or secondary polling engine and how many elements (nodes and interfaces) will need to be monitored by it (e.g. 250, 2000, or unlimited).

My advice to others before implementing this, is to attend one of their webcasts to get a feel for what NPM can do for you. The presenters are technical people who understand the product well and can answer a wide range of questions. Secondly, I’d make an account on their forum, Thwack, so if you’re ever stumped on an issue, you can pose a question to the community and glean information from other NPM users or from one of SolarWinds’ resident “Head Geeks.” Lastly, from personal experience, I would make sure you’re on good working terms with your network engineers before considering implementation. Like any other network management tool, you will likely run into firewall or connectivity related issues when adding nodes and having a good network engineer on your side can really make a big difference .