SolarWinds NPM Reviews

I use NPM for traffic monitoring in my network. It monitors all my traffic.

It is good for notifications and monitoring traffic, especially since most of them are remotely done.

The abnormal traffic notifications are good. Most of them are remote, and it is very good for notifications and monitoring for the traffic.

The price could be better. The maintenance or upgrade system regarding the payment is not good. It must be upgraded and is not related to the additional support payment. 

Also, if I need to make a feature enabled, I have to buy another edition and include support, which is unnecessary for me.

I have been working with the product for six or seven years.

There are points where the system drops, and you need to restart or monitor the system itself. It is not a SaaS system; it is an on-premises system.

It is pretty scalable. I would rate scalability as eight out of ten, with no issues.

Customer service is linked to payments. If you do not have a license or renewal supported, it is not supported for you.

Positive

I also use Microsoft Defender as it is good. However, the user needs a license for any additional user in SolarWinds.

The initial setup is simple. Sometimes I do it by myself, yet at other times, I do it with a consultant from SolarWinds teams.

I did the setup with the help of SolarWinds teams at times and by myself at other times.

The price could be better, and the system has a payment structure linked with upgrades, which I find unnecessary.

I use Microsoft Defender at times due to licensing restrictions with SolarWinds.

I can recommend the product, especially for small or medium-sized companies.

I'd rate the solution eight out of ten.

We have a lot of “home-grown” apps to handle the interesting and challenging monitoring requests and alerting needs.

This product is extremely flexible and customizable. It will do just about anything you need it to do. Out of the box, there is a significant amount of monitoring you can do with very little setup. Then, with custom properties and some ingenuity, you can get it to do pretty much anything else. Additionally, there are a lot of ideas and support in their forum, Thwack.

With custom properties and the alerting flexibility, we’ve been able to customize the alert trigger and reset logic to meet the needs of our users, as well as eliminate the likelihood of making mistakes in the operations center.

We used to be fraught with scenarios, such as:

• Only call if the alert doesn’t clear after 45 minutes.
• Ignore that alarm.
• Don’t call on that night.

The SAM custom script for running component checks only supports 10 pairs of results. I am not sure whether this is a scalability issue. It would be nice to have the option to do more. We worked around it by doing a component check per pair as much as we needed.

The product is excellent at taking feedback, especially from the Thwack form, and implementing popular feature requests.

We’ve been using it for almost 10 years.

Back in the early days and new major releases, of course, there were some hiccups and gotchas. Bleeding edge, baby! It’s all a matter of risk assessment with new feature needs, etc.

We have not run into scalability issues.

In general, the technical support is great. Around new major releases, you do experience longer waits; and every so often, you get a support technician who is newer. Still, if you call in and it’s critical, they fix your issues in a timely manner. This is to be expected; and you need to take this into account in your risk calculation when you schedule upgrades.

We were previously using HPE OpenView. The biggest reason was its lack of mapping flexibility at the time. The ops part is still very visual with the green/yellow/red color-coding of icons. Our systems side is based on alerts and emails.

I don’t recall any troubles during the initial setup. It was a long time ago. I was enamored by its mapping capabilities.

• The software is structured and priced well. It’s not cheap; but it’s not overly expensive either. You get what you pay for, and they are well positioned.
• You are able to spread the costs out by implementing it in steps. Your team is probably not huge. You don’t need to sit around waiting to install and configure the entire monitoring solution. Start with NPM, and start adding modules and capabilities as your existing implementation matures.

We were required to assess alternatives, but I don’t recall the specifics. When implementing SAM in the last 2 years, we moved from Big Brother and evaluated Nagios.

• Gather the official requirements for a monitoring solution, and alert all the consumers. The consumers here are the owners of the monitored gear and apps, and the engineers in the support and ops teams.
• Set a good chunk of time aside to test drive the solution, and get creative with the custom properties.
• Learn SQL or SWQL, a SolarWinds query language that is easier than SQL. This will expand your potential capabilities for customization significantly.
• I am very active on the forum. I get a bunch of ideas and help; so I like to give back.

We use SolarWinds as a monitoring platform.

It monitors all of our network gears for up-down status, for the most part. We can also see utilization being high at a given location.

The alerting has been the biggest aspect we appreciate. In regards to utilization, it can be proactive in regards to addressing situations before some cases arise before the users even see them.

The initial setup is simple.

It integrates really well with the Cisco platform. We are a Cisco shop. I don't know how well it's going to integrate with us moving to Aruba or going with other vendor hardware, how well it's going to integrate, I guess we'll find out.

It is scalable.

Technical support is helpful.

The stability is good. 

The only real caveat that we have or that I have an issue with is when I go on vacation, it's a little hard for me to go and modify alerts so that I don't get alerted about things when I'm on vacation. There's not a way to turn me off from alerts easily.

There really hasn't been anything that we've needed that it hasn't been able to provide. 

I've used the solution for at least 17 years. 

The solution is stable. there are no bugs or glitches and it doesn't crash or freeze. It's reliable.

We've got about nine different Sys admins that use it on a day-to-day basis, at different locations, to check on different things.

Contact support was great. They're very knowledgeable. They knew what we needed, once we explained our problem. In some cases, they helped us figure out a different solution than what we were looking at. They knew the product pretty well for everybody that we've dealt with.

Positive

We didn't use a different solution. That's what was here when I started 17 years ago and that's what we've stayed with.

The setup was pretty straightforward. We just went through a complete redeployment part of upgrading to the latest and greatest as we upgraded servers and databases and the whole nine yards. We just simply did a fresh install. It was pretty easy.

It probably took us about a couple of days. We had to go back in and once we re-added the location, we had to go back and tweak what we wanted to monitor, and that kind of stuff. We didn't simply just do a migration. It was a little bit of doing the network re-discovery and then going in and tweaking the individual locations. 

The one thing we did migrate over was the alerts. We didn't have to recreate alerts from scratch, however, it took us a while. We've got 400-plus devices that we monitor. It took a little while to get all of the devices back in the way they originally were.

We did everything in-house. We did not use consultants or integrators. 

I don't know anything about pricing. It's not an aspect I deal with.

We deal directly with Solarwinds. 

We have been keeping the solution updated. 

I would recommend the solution. A lot of our colleagues use it and we like the way it works. I'd rate it ten out of ten. 

I'd advise potential new users to give it a good rundown and see if it really fits what they need. Don't just try it with one or two things. Do the 30-day evaluation. I have folks that have used it and try to find some way to break it really. Load it up the way that you want to run it and actually take time to dig down into it. So far, there hasn't been anything that it hasn't been able to do for us. However, it's designed for that Cisco environment and that's what we've always been. I can't really talk about it outside of the box.

Our primary use case for the solution is to monitor whether certain devices are up or down, monitor bandwidth utilization and have a network performance monitor.

The ability to quickly identify downtime is the most valuable because we use the solution for monitoring. For example, a map that shows all of our switches, which make up our core infrastructure, and then the small firewalls that connect to the other locations so that we can see how our devices are running. Hence, the monitoring ability to create those maps and monitor everything on warmup is a very valuable feature for us.

The solution works very well for our current use case, but the price of the solution can be improved.

We have been using the solution for a while and are currently using version 12.4, but we are considering upgrading it.

We have not had issues with stability. I rate the stability a nine out of ten.

The solution is scalable, and there is currently only two staff utilizing the solution in our organization, but we have plans to increase usage further.

We have a fairly small environment, but this is because we only have about 15 switches, some servers, and our remote locations, so we're using a couple of hundred nodes altogether, but we can scale up to probably thousands or even tens of thousands because there is room to add additional servers. I rate the scalability a nine out of ten.

We dealt with customer service and support once for a license issue, and they resolved our concerns swiftly.

Positive

SolarWinds NPM was the first network monitoring solution we used

The initial setup was complex as there was quite a bit of work that had to be done in terms of setting up databases and making sure the database was linked to the application.

We implemented the solution through a vendor team the first time, but further installations were done in-house.

The licensing costs are fairly high. I rate it a five out of ten.

I rate the solution a nine out of ten based on our current version. The solution is a robust and stable product but can be improved by reducing its licensing costs. Therefore, I recommend the solution to users considering implementing it.

We are customers of SolarWinds and I'm the corporate IT infrastructure manager.

SolarWinds provides a good enterprise level of tools and covers the essential components. I like the new GUI. 

The solution could be enhanced. It currently lacks integration with SMS services which is something we need. A cloud-based option would also be helpful so we can monitor at any time and from anywhere; for now, we need to VPN to our environment. 

I've been using this solution for six years. 

The solution is generally stable although there are occasional bugs when updating to the latest version. 

The scalability is good, we currently have around 2,000 users. 

The initial setup is simple.

Compared to other products, SolarWinds is not expensive. 

We evaluated Zabbix and Nagios but SolarWinds is better for enterprise organizations. Other solutions are on a smaller scale and only provide basic monitoring; SolarWinds has a better engine.

I rate this solution eight out of 10. 

• Extensible REST API
• Excellent technical support
• Mature product, strong brand, Gartner awards
• Custom MSSQL scripting support in both alerting and reporting.
• Support for a wide variety of makes and models of network equipment/appliances.
• Support for monitoring Windows, Linux, Unix, and some other server OSes.
• Consistent and constant application improvements.

• Our ability to locate the source of a network issue has dramatically reduced our mean-time-to-resolve.
• Helped us to consolidate different network and server monitoring needs under one product.
• Low administrative maintenance compared to alternatives. The system simply 'works' most of the time. Our previous tools required constant maintenance by admins just to keep them running.

• Failover functionality does not exist without the purchase of the "Fail Over Engine (FoE)" license.
• Software upgrade and installation procedures are time consuming, especially for large/multiple site installations. Consulting the support matrix for software versions and modules is critical.
• Multiple server software upgrades still require a planned downtime outage window for the entire NPM instance regardless of the size of installation even if using the Failover Engine module.
• Each NPM polling server require a full Windows Server with GUI operating system to install and administer.

5 years

Yes. Remember to do your homework on required ports, especially for when installing a polling engine server across the WAN in a different domain.

Yes, multiple times. Some of the areas of stability had to do with 'monitoring capacity' per polling server several versions ago. Official documentation claimed each server can handle monitoring for up-to 10,000 elements (i.e. ports, volumes, nodes, etc.). In reality this number was more like 5,000. However, monitoring capacity improvements have been made with each software release and we are now back up to the 10,000 element.

Another area of stability issues we have experienced are with the dependency on MS SQL. There were a few times where we had stability issues with SQL server, which in turn impacted NPM performance. When there are issues with the SQL database NPM doesn't make this known and is up to the admin to figure it out.

Yes, every once in a while. SolarWinds defines 'scalability' in the same manner as 'monitoring capacity' --- which is incorrect. This is a huge issue and is one of the hits against the rating I gave NPM.

Excellent. Customer support is knowledgeable about the product line and will engage with technical resources if needed.

Excellent. Technical support is responsive, knowledgeable, and friendly. My team and I do not hesitate to contact support if we have a question or need immediate assistance. They will also escalate to a higher support tier if the issue is not resolved in a timely manner, or if we request them to do so.

Yes, multiple products were used previously including Microsoft MOM 2005 (current versions are System Center Operations Manager) and What's Up Gold. Switch was made to attempt to consolidate various monitoring tools into a single space.

Initial setup of the application servers were very straightforward. It is possible to get started with one app server and the main SQL server then add more polling engine servers as your monitoring needs increase.

In-house installation was done. The product is designed for self-installation and self-maintenance in an on-premise mode.

Unknown at this point.

Always contact your sales rep for best pricing. There are multiple times per year where the vendor will make special licensing offers that you can take advantage of.

The official North America pricing list is available at solarwinds.com. Use that as your pricing baseline for your monitoring project.

NPM licenses by "element" you want to monitor, not by device as a whole. Take this into account while you evaluate monitoring software vendors.

Yes. We looked into Microsoft System Center Operations Manager 2012 R2, What's Up Gold, ManageEngine, AppDynamics, NewRelic, and Nagios.

We use SolarWinds NPM for network monitoring.

The most valuable features of the solution are its graphical interface and reports.

The solution's customer service is not very good because the support takes too long. The solution needs to provide better training videos, especially on creating individual reports. It would be good if reporting were made easier with SolarWinds NPM.

I have been using SolarWinds NPM for five years.

SolarWinds NPM is a very stable solution.

I rate the solution ten out of ten for stability.

I am the main user of SolarWinds NPM in our organization.

I rate the solution a five out of ten for scalability.

The solution’s customer support is not very good.

Negative

The solution’s initial setup is easy.

SolarWinds NPM is very expensive, and we pay ten thousand yearly.

The solution’s maintenance is easy. The solution can be easily integrated with other services like Cisco. There are issues with the solution's updates, and our security team has not approved them. So, we are waiting for the new version to be approved.

Overall, I rate the solution a seven out of ten.

The most valuable features of SolarWinds NPM are network performance monitoring and the overall benefit for servers.

SolarWinds NPM needs to increase its elements. One polling engine can only support 10,000 elements then it becomes slow. There are limitations even if you have the full SLX version license.

If we want to have more polling engines it will cost an additional 20 Indian rupees.

I have been using SolarWinds NPM for approximately nine years.

SolarWinds NPM is a stable solution.

The scalability of the solution is good. It is easy to do.

I would recommend this solution to enterprise-sized companies.

The support is good.

I rate the support from SolarWinds NPM a five out of five.

Positive

The solution can become very expensive and commercially not viable in countries, such as India.

I find this solution to be better than others because we are familiar with it.

I would recommend this solution to others.

I rate SolarWinds NPM a nine out of ten.