SolarWinds NPM Reviews

SolarWinds NPM is used in our organization as a monitoring tool for network devices. As a network administrator, I use this solution to monitor devices like switches, routers, interfaces, and tunnels. 

The tool monitors tunnel utilization, interface status, UBS, data center humidity and temperature. 

It's a highly reliable product. SolarWinds NPM is one of our company's most valuable products. SolarWinds NPM immediately notifies via email in case of any downtime situations. 

The response time of the support team needs to improve. Sometimes, there is a wait time of three or four hours to obtain a response from SolarWinds NPM. The consistency of support also needs to improve, in some cases a quick response can be noticed from the support team of SolarWinds NPM. 

I have been using SolarWinds NPM for one and a half years. 

I would rate the stability a ten out of ten. The solution is highly stable. SolarWinds NPM has showcased the utmost stability for one and a half years of usage in our company. 

I would rate the scalability an eight out of ten. SolarWinds NPM adapts well enough to the workflows in our company. The solution is used in our organization to monitor more than 200 nodes. At our company, we are already using the maximum user license of SolarWinds NPM.  

The customer support is satisfying for SolarWinds NPM. I would rate tech support a six out of ten. Quicker responses are expected from the support team. 

Neutral

I would rate the initial setup a nine out of ten. Our company team effortlessly deployed the solution. Only a few free resources, like YouTube, were utilized by our organization's professionals to learn the product installation process.

The deployment of SolarWinds NPM took one or two hours in our organization. After the primary installation of SolarWinds NPM, every node needs to be restarted, it takes time to add the nodes at the monitoring end. Only one or two professionals from our company were needed to deploy SolarWinds NPM. In the post-deployment monitoring, only one professional is required.  

The product was implemented in-house. 

We have realized ROI in terms of saved time in our organization. The product has also contributed towards ROI through accurate and reliable downtime alerts. For instance, the exact number of down switches is notified by email. I would rate the solution's ROI a ten out of ten. 

The product price can be considered to be affordable in economically strong countries like the US but it appears as a bit expensive in Egypt. I would rate the pricing a five out of ten. Our company pays for the license on a yearly basis. The price of the solution is fixed and can be checked by anyone on the vendor's website. 

I would definitely recommend the solution to others. SolarWinds NPM has also helped improve our organization's network performance. The alerting and reporting capabilities of the tool are impressive and can be customized easily. The alerts or reports can always be obtained via email. I would overall rate the solution a ten out of ten. 

We're using SolarWinds NPM for server monitoring, report monitoring, and application monitoring.

I found a lot of valuable features in SolarWinds NPM, such as the customized application monitoring that allows you to customize any monitoring and script customization, and you also have the option to deploy and upgrade SolarWinds NPM online, which is very useful for my organization.

An area for improvement in SolarWinds NPM is the short retention period. Currently, it's just for seven days of data, which is very low, making it hard for my organization to keep that data.

SolarWinds recommended a seven-day retention period, but my organization needs a fourteen-day data retention period. Hence, I'd like an increase in the retention period or the database limit in SolarWinds NPM because you can't go back to the data for any investigation if seven days have passed.

Another area for improvement in SolarWinds NPM is the database, which needs to be a bit more mature.

I want a modified database in the next release of SolarWinds NPM. I'd also like more options added to groups because, currently, it's very limited.

I've been working with SolarWinds NPM for almost two years now.

SolarWinds NPM is a stable solution.

SolarWinds NPM is a scalable solution.

My team contacted technical support for SolarWinds NPM a lot of times. On a scale of one to ten, I'd rate support as seven because one of my cases remained open for a year without the perfect answer or resolution, though the SolarWinds development team has been working on it.

Neutral

I've previously worked with HPE and IBM, but that was for another organization. My current organization uses SolarWinds NPM.

The initial setup for SolarWinds NPM is relatively easy, and anyone can do it.

As I deployed SolarWinds NPM in a huge environment, the deployment took almost six to eight hours for fifteen servers.

We deployed SolarWinds NPM in-house.

Though I don't remember the price for SolarWinds NPM, its price is somewhat okay when you compare it with other tools in the market. The price isn't too high and isn't too low, so it's okay.

I'm an end-user of SolarWinds NPM.

In the organization, over a hundred people use SolarWinds NPM, with five to six administrators. The solution requires specific maintenance, mainly because it has a lot of DW issues.

My advice to people looking to start working with SolarWinds NPM is that it's the best solution for a medium-scale environment. For a large-scale environment with many requirements, such as a vast number of nodes, for example, more than twenty-five thousand, SolarWinds NPM may not be as scalable, DW-wise. If you have below fifteen thousand to fifteen thousand nodes, then it's okay to use SolarWinds NPM.

My rating for SolarWinds NPM is eight out of ten.

This solution has many different roles in our company. There is the application support group who configure it for monitoring specific services within applications and our desktop or operations group which monitors toner in laser printers. My group, which is primarily networking and servers, use it for bandwidth monitoring, server processor utilization monitoring, and for disk space monitoring. So we use it for a lot of different things. There are probably 200 services that are being monitored within our financial system to make sure that it is running optimally. I'm an infrastructure supervisor and we're customers of SolarWinds.

The outcome of using this solution is that we've been able to become more proactive on really resolving issues before users know that there's a problem. Outages have reduced by probably around 90% because we're able to take and proactively add space to a disk or add processors to a server before users know there's a problem. It means we can take something down at night and fix it, rather than disrupting work in the middle of the day. 

The alerting and usage tracking is a valuable feature because it alerts us when we're getting near capacity on disk space, network utilization or processor utilization. It helps us manage our capacity and enables us to be proactive.

This is a complex product to set up and I think it's really too detailed and could be simplified. It's a change from their older product which was very easy to set up and manage. The new one is more difficult because it's far more detailed. The solution does everything we ask of it, but it takes a long time to deploy.

Additional features and improvements would be to simplify initial data gathering so that we can deploy easily and then refine it over time. Ideally, we'd like to be able to get something up and running in a week and then go through and decide, for example, to monitor things on one particular server and not necessarily on others. They could possibly create a generic installation and then let us go back and refine it. We spend a lot of time without having all of our equipment monitored because it takes so long to initially set up each server. 

I've been using this solution for three years. 

I think this is a very stable solution.

I think the solution is easy to scale although it does require a lot of resources. When we initially set it up, we had about a quarter of the resources that we currently have and we set it up too conservatively which caused a lot issues. When the consultant reset it, we quadrupled the amount of resources that the system has. We have about 10 people that get alerts and are actively involved with the system. The system requires about 10 staff hours for maintenance, updates and verification that everything is working.

As we refine it to monitor services, we are going to increase the usage. So right now we have it monitoring a database server, but we're not monitoring all of the services within that server. So we might have 30 databases in there. We're not yet monitoring each of the individual databases.

We have very few issues that require technical support, we only contact them a few times a year. They generally resolve things pretty quickly and our issues are generally related to improving deployment. 

We used to use a product called ipMonitor, which is a much simpler solution. It's one-tenth of the cost and we used it strictly for alerting. It would tell us when a server was down, but not that the server was running at 70% utilization for the previous week. ipMonitor was strictly a something is working or a something is not working solution.

The server configuration for installation took about a week. And then another two to three weeks to get it installed across all of our servers. We're making modifications every day. We initially set it up ourselves and then about two years after the initial installation, we hired a consultant to redo the installation and make it more efficient because it wasn't initially configured optimally. It's the amount of detail you need that will determine how much time you spend setting something up.

Our ROI has been in the savings in downtime during business hours.

Our annual maintenance fee is USD $15,000. 

HP had a similar product that we looked at but it wasn't nearly as universal as SolarWinds products. HP has a product to monitor servers and a product to monitor networks, but they don't have one product that does both well, SolarWinds monitors everything very well.

I would recommend taking into consideration that you will need more server resources than you think. Knowing that means you can save on having to rebuild the whole environment later on. We ended up going from one server to four servers and it's running much better now. Don't skimp on the server resources you get with the application.

I would rate this solution a 10 out of 10. 

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 are using Solar NPM to send alerts to the NOC and SOC teams. Some reports are used for our network to link to the router for internet utilization. We are also monitoring wireless access points using SolarWinds. Our network, security and system teams use this solution and its dashboards. 

This solution offers a very good view of our network and allows us to effectively monitor performance.

The dashboards for this solution could be improved. We would like to divide the dashboards to give a clear view to our management team to show what we have and what deficiencies exist in our network. We would also like to show the number of devices which we need to improve our service.

I have been using this solution for ten years. 

It is a stable solution. 

This is a scalable solution. A few months ago I had a problem with the number of nodes on the system itself. We have the SLX NPM license which is unlimited and I can add an unlimited number of nodes. It seems there was a limitation on the one server. When I contacted support, they told me that I either need to delete some nodes or add another server to scale.

Whenever I have a problem or I need to ask a question, I contact the SolarWinds support team. I would rate their support a four out of five. 

Our company decided to change to SolarWinds due to a security breach they experienced. Other solutions that were considered were more expensive than Solarwinds. 

The initial setup is straightforward. 

To install the SolarWinds for the first time, you need a virtual machine to install the demo or trial version of SolarWinds. You can then add some devices, monitor and try to use whatever dashboards or reports you think you will need. Installing NPM itself and adding the nodes took us three months.

We implemented this solution in house with the help of a third party who were Solarwinds experts. 

We have seen a return on our investment using this solution. We are now working on a re-innovation project for the whole organization's network because our network is very old. Some vendors offered us a management solution for network performance monitoring but their devices offer the same functionality as SolarWinds. Based on what other solutions charge, the $700 we pay for this solution is fair. 

We pay approximately $700 per year for renewal of the license.

I would advise others to test the environment before deploying the whole solution.

I would rate Solarwinds an eight out of ten. I would give a higher rating if I could use root cause analysis to point to one device in the stack to understand which device has a problem. In general, I think SolarWinds is one of the most stable solutions and it has a lot of useful features for network performance monitoring.

We are using SolarWinds NPM to monitor our network. For example, we monitor Cisco Meraki for WAN, and other Cisco routers, and for LAN we monitor Cisco switches and firewalls.

There are a lot of valuable features with SolarWinds NPM. We can receive a lot of detailed data from the monitoring that can use useful for investigations, especially when you are troubleshooting. It is very helpful. Overall it was a very good experience.

SolarWinds NPM could improve the graphics of the interface and more customized reporting.

I have been using SolarWinds NPM for approximately one year.

SolarWinds NPM is stable. We haven't faced any major outages.

The scalability of SolarWinds NPM is good, and it is simple. We have approximately 5,000 nodes.

The support we have received from SolarWinds NPM has been very good. Initially, there were some issues with the solution but the support help us figure it out.

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

The knowledge base of the support could improve. However, every organization has its own use cases. Sometimes it's not a common use case and the support has not seen the particular problem. We might have something unique, which other clients never faced.

We have used Centreon previously. We have evaluated it for some time. It was very easy to use but the requirements we had, were not fulfilled. We have engaged with some Centreon providers, and the support was not great. We bought a license for one year for Centreon, and the support from France was not great. That's why we decided that we cannot go with it for a longer time and on a larger scale. Additionally, we have used Alaloop for quite some time, and it was good.

We switched to SolarWinds NPM mainly because we were expanding, and in Alaloop we were mainly using it for WAN only, not for the LAN. Additionally, Alaloop was much more expensive compared to SolarWinds NPM.

The initial setup of SolarWinds NPM was not straightforward. We had some difficulty configuring some of the new features for the devices properly. However, this was because we were new to the solution. We had the documentation which was helpful.

The full implementation took approximately one month.

I rate the initial setup of SolarWinds NPM a three out of five.

We used third-party support for the implementation. The solution requires maintenance but we have not had any issues.

SolarWinds NPM has different pricing models available. The cost of the solution is less than some competitors.

I would recommend SolarWinds NPM to others but it depends on how complex the network they have is and how large it is. Based on that information, you need to make a decision if the solution is the best fit. If their infrastructure is quite large, the good thing is they can expand it, even for the server infrastructure, not only for network infrastructure. 

I would recommend the solution for a larger organization.

I rate SolarWinds NPM an eight out of ten.

I believe the ease of setup and use, including everything, from the initial installation to the discovery of devices is the most valuable. The advanced alerting and notifications capabilities are helpful as well. Devices can be discovered automatically on a schedule, and grouped by vendor automatically, which makes it very easy to track down devices. The customizable dashboards and reporting are flexible and tend to come in handy as well.

SolarWinds NPM allowed the IT department to take a more proactive approach to troubleshooting, and gaining insights on device availability. We were able to use the integration with Storage Manager and Virtualization Manager to gain valuable insight into our storage and virtualization environments. We were able to readily pull reports on device availability, and other metrics, to provide to our senior management staff and external security auditors.

The SolarWinds notification and alerting configuration could be simplified as it would be easier to find if it was within the NPM web application instead of in a separate client application. The SolarWinds Orion/NPM installation comes with a few Windows client application “add-ons” that would be better served if they were built into the SolarWinds NPM web application. Another area for improvement would be better integration between Solarwinds NPM and Solarwinds NCM as it seems that Solarwinds NCM installs a separate version of NPM/Orion console.

I used this product for a little over two years in two different companies. I implemented the product for the first organization I was with to gain visibility and performance monitoring for the network and servers within our data center.

Yes, there can be issues with deployment if you try to install/uninstall or re-install under different account types (i.e. Local Administrator vs. Domain Administrator). I would recommend sticking to one or the other and you won’t run into any problems.

I have never had an issue with stability or performance. I recommend following the SolarWinds documentation (which is very detailed) and you can be assured not to encounter a single issue in regards to stability.

We setup a standalone instance of SolarWinds NPM. However, SolarWinds NPM offers a couple of different HA architectures that will allow you to scale locally (within the same data center) or globally (across multiple data centers in different geographic locations).

The customer service experience was always top notch and I don’t recall ever having a bad experience. The customer support staff were friendly, courteous and always there to help you out. It was also very easy to get in touch with a technical support engineer, all who seemed very knowledgeable, within just a couple of minutes or less.

SolarWinds technical support was one of the best support departments I’ve ever dealt with. All of the technicians were very knowledgeable and technically capable. Also, when you call into their technical support number, you don’t have to jump through multiple departments to get to a technician, which is very nice and not the same with other vendors.

No, SolarWinds NPM was the first network/server monitoring product that was brought into the organization. Other network monitoring products were researched, but didn't have the feature set, didn't seem as easy to use or as robust as Solarwinds NPM.

It was very straightforward, as you basically just have to start up a Windows Server, and click through the SolarWinds NPM installation wizard before you are ready to configure. You can configure most of the basic settings using the installation wizard (i.e. the database storage location).

We implemented it using an in-house team. It should not be necessary to use a third-party team unless you are performing a massive roll (5000+ endpoints) out across multiple sites.

I believe the original setup cost was around $3500 with an annual cost of around $1200-$1500 to renew the support license. This would bring the average day-to-day cost of around $5-$6 over three years.

We also evaluated ManageEngine OpManager and AdRem NetCrunch before deciding to purchase SolarWinds NPM in conjunction with the SolarWinds NetFlow Traffic Analyzer (NTA) module.

If you’re looking to get a lot more insight and visibility into your network devices, servers, applications, and other devices, along with real-time alert notifications, SolarWinds NPM should be towards the top of your list. You will be able to view devices by type or by location and poll all sorts of different data using SNMP or WMI or other methods. Out of the box, you will also receive customizable dashboards, alerting, reporting, and Active Directory integration.