SolarWinds NPM Review
With an easy-to-use interface for both admins and users, we use it to provide infrastructure monitoring services.

Valuable Features:

An easy-to-use interface for both admins and users is key. Adoption of any product can be constrained by a UI that is neither intuitive nor visually engaging. The SolarWinds NPM framework, upon which most of their flagship products are built, empowers a wide variety of admins and users to quickly find value in their installed products.

Improvements to My Organization:

We used a monitoring platform from an enterprise vendor that was so complex to manage that we struggled even to deliver the base infrastructure monitoring services. This is not a unique position as many IT departments manage by the mantra of "Nobody was ever fired for recommending [insert enterprise vendor here]". 

In a few short years, SolarWinds has empowered us to provide robust infrastructure monitoring, including a converged view of our servers, both the physical and virtual servers, and the storage and application environments.

Room for Improvement:

  • Real-time analytics is the major weakness of the SolarWinds NPM platform today. They've done a fantastic job enabling the collection of data. Users are now demanding the ability to generate their own graphs, views, and so on; all of this must be done by an admin today.
  • Scaling to the enterprise level is also an issue. SolarWinds NPM officially supports up to 100K elements (the number is unofficially about 50% higher), but enterprise customers could scale beyond that limit. However, this would only be applicable to environments with extensive interface monitoring requirements (where every interface is an element) or there is a node count > 10,000. SolarWinds is committed to growing that threshold in the near future, but no official announcements have been made.
  • Enterprise customers would also like to see high-availability and fault-tolerance. HA v1 was implemented in the latest release at an additional cost. FT has yet to hit the current release but is something we regularly discuss on the Thwack forums.

Use of Solution:

I have been using various versions for the past 10 years.

We are currently using:

  • SolarWinds Network Performance Monitor 12.0.1
  • SolarWinds Server & Application Manager 6.3.0
  • Storage Resource Manager 6.3.0
  • Network Traffic Analyzer 4.2.1
  • Virtualization Manager

Stability Issues:

Again, enterprise-scaled customers are probably the only ones to notice issues here and it usually happens post-upgrade. We process 4,000 transactions per second in our monitoring environment and that scale exacerbates any code inefficiencies or bugs. However, the platform is generally very stable and any issues are dealt with rapidly via tier 3 support and the development team.

Scalability Issues:

SolarWinds NPM officially supports up to 100K elements (the number is unofficially about 50% higher), but enterprise customers could scale beyond that limit. However, this would only be applicable to environments with extensive interface monitoring requirements (every interface is an element) or a node count >10,000. SolarWinds is committed to growing that threshold in the near future, but no official announcements have been made.

Virtualization Manager can scale almost infinitely, but we found that it performed best, especially when integrated with the SolarWinds NPM framework, with more moderately sized vCenters rather than a fewer large vCenters.

Technical Support:

Technical support is currently the achilles heel of SolarWinds. 

  • Non-critical issues can be handled through an extremely active and passionate user forum (at, but actual technical support requires engaging their team via a case that can be opened from the support portal or by phone. 
  • Every customer receives the same level of support regardless of their size, and there is no option to purchase 'advanced' support at this time. Enterprise customers will find this model challenging. This is mitigated by hiring experienced SolarWinds engineers, especially SolarWinds MVPs.

Developing an enterprise support model with measured and reported SLA and OLA targets should be at the top of the SolarWinds support model to do list.

Previous Solutions:

In every case where I have used SolarWinds, I have displaced an enterprise platform from a larger software company including, but not limited to, IBM, HPE, NimSoft, and so on. I've also displaced segment competitors because of the aggressive pricing model from SolarWinds and their favorable cost-to-value ratio.

Initial Setup:

The initial setup is as about as easy as they come. SolarWinds products are renown for being easy to install and configure, and for rapid time-to-value; but the devil is in the details. 

As an experienced enterprise engineer, I often see inexperienced engineers jump into the product and start producing metrics that add value under the assumption that everything out-of-the-box adds value. This is not the case; and it is a weakness of the installation model. Customers can be lulled into a false sense of success by their rapid deployment and TTPP (time-to-pretty-pictures). Understanding the data is just as important, perhaps more important, than getting the data.

Cost and Licensing Advice:

The licensing model is such that you can purchase only what you need; and then grow into the next level by paying only the difference in price and the associated maintenance costs. The first year of maintenance is included in the initial purchase. This helps drive down the ROI in the first year. Subsequent years are a percentage of the retail cost. They are on par with similar service offerings from other companies.

Other Solutions Considered:

We considered options from most major vendors. SolarWinds won out because of the low price-to-value ratio; and the immediate and long-term cost savings made by displacing other products.

Other Advice:

Avoid the urge to go quickly. Take the time to forecast your growth in the next 12-24 months and plan the infrastructure for that target. Always follow the size and scaling recommendations, especially for your database environment. Do not use RAID5 for your database as the transactional environment or SolarWinds Orion will overwhelm your storage environment.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
1 visitor found this review helpful
Anonymous avatar x30


Anonymous avatar x30

The REAL user of this article is accurate about the SolarWinds products mentioned. For small implementations initially targeted (SMB), the person installing it will get a WOW factor.
Yes you have to tune the system and adapt alerting accordingly that should be in line with the information needs of the enterprise users groups (the internal customers). There is a real need to interface between the project and ongoing support and the customers in an enterprise environment (operations, projects, migrations). Yes there are a number of weak points in the SolarWinds system. You will only bump into them when you are scaling up and want more structured data exchange between other systems like ServiceNow, CMDB repositories. Currently I use a third party tool that gives a complete physical layer view of the environment (cabling, racks, floor space, UPS, PDU and more) that integrates with SolarWinds. The next step is to create application visibility that drills down into the platform resources.

Like (0)04 January 17
Anonymous avatar x30

Update on - Room for Improvement: Real-time analytics -
There has been a new release of a number of the SolarWinds Orion modules including NPM v12.1 and this includes a new PerfStack feature allowing users to select and graph metrics from any monitored system and create their own timelines which can be saved and shared with other users.

Like (0)03 April 17
Why do you like it?

Sign Up with Email