SolarWinds NPM Reviews

The ability to pick and chose modules per need, but at the same time close and seamless integration once deployed: While everything is pretty complicated and fast moving, we do not want the monitoring and management software to be complicated. That is the reason the ease-of-deployment and ease-of-use is extremely valuable.

Proactive alerting helps prevent outages to meet our SLA, as well as in forecasting.

Some features are missing (which will be in any product out there) but there is a community that either provides workarounds or the ability to request the improvement.

I have been using SolarWinds for nine years.

For the most part, it is just like any product and is as stable as it could be. At the same time, it is just as vulnerable as the infrastructure it uses (server/VM, storage, network and database).

SolarWinds has come a long way to provide scalability. What initially used to be for small enterprises is now much more expandable and can accommodate larger enterprises. The implementation is easier by deploying additional polling engines (of course, with limits like in any other product).

Other than some occasional delays getting hold of someone in the telephone queue, technical support is good for the most part.

We were using Big Brother, HostMonitor, OpManager and HPE OpenView. We migrated as a part of the initiative to consolidate the monitoring system into one platform.

Installation is very straightforward; however, upgrades are a bit tedious (though not complex). It is complex only when you have a large platform of monitoring systems. For a small implementation, it is extremely simple.

The key is not to look at the current situation but consider future needs. It should be aligned with the infrastructure growth. Unless it is a really small environment, I always recommend to go with the unlimited license because the elements get used up quickly.

I was using other products so I did not evaluate, per se. But I knew the difference between other products and SolarWinds.

It requires absolute thorough and all-round details on the infrastructure and its future needs. Once the scale is identified, get the right licenses and underlying platform (physical vs virtual and quick storage).

• If you are almost in the dark, SolarWinds can give you a quick view of what you have and you can start basic monitoring.
• The user interface is good.
• You can build a live inventory of the equipment you manage.
• You can start structuring and digging deeper into Network Performance Management and Diagnostics.

• It helped to bring a basic monitoring in place that could be a platform for additional information you need to manage a large IT infrastructure.
• IT network visibility can help the organization a lot.
• It provides a buy-in from other IT groups (database, Windows, applications)

Scalability: In general, the scalability for most organizations is OK.

The product is also used by larger companies and TELCOs. They encounter scalability and stability issues. You need a dedicated person or team to keep everything under control.

We have used the base product for more than 12 years.

You certainly can have stability issues. The system runs on Windows Server and a dedicated MS SQL Server.

You need a lot of polling engines for larger networks (50K+ interfaces). This will consume additional resources, such as licenses, support, and patching.

SolarWinds does not provide professional services. You have to rely on partners that provide this service.

If there is an issue, you will have a pretty slow response. You need access to the SolarWinds portal to register a ticket.

In general, the response time of SolarWinds should be improved.

In general, it is mainly switching from open-source systems to a supported system.

The initial setup worked fine. This depends on the system and scale you are trying to implement.

General advice is to build the monitoring as a layered approach.

Add devices/systems by categories, starting with basic monitoring ICMP and SNMP, and then add specific metrics to the system.

The pricing depends on what company you are. If you are you an enterprise or TELCO, the pricing is really great.

If you are a smaller company, it can become expensive and also complex to get it running.

For SMBs, you have to sit down and think what you are going to do. Some companies outsource a lot to get rid of the IT pain.

• Create a very simple requirements list.
• In general, do not start a paper comparison.
• Install the product or let someone help you with the install and configuration so you will get a quick start.
• Do not try to find out everything yourself.
• Based on what you have seen, you can build the so-called "gap analysis".
• If you go for SolarWinds, it will not solve all your IT problems. You will also need complementary tools.

At the time, we did not have a central repository for network mapping. This product help us with this and allowed us to drill down on the elements in the maps to get more detailed information.

It provided visibility into network performance, which at the time we really did not have.

Reporting: Generating reports could be improved.

NOTE: This is related to the version 9.5. I believe they are on version 12.1 and this may have been addressed.

I have used SolarWinds for 10 years.

I did have some issues with the stability of the database, but that was due to issues whereby nightly maintenance of the database was not running.

I had some performance issues but they were due to the need for addtional pollers.

Technical support is average. Sometimes it took days to get responses and the responses were via email.

I was using an open-source solution that was not scalable.

Setup is very straightforward and easy to install.

For the price, I would purchase the unlimited version especially for medium-size companies.

We looked at eHealth, CiscoWorks, and HPE OpenView.

Make sure you plan the implementation of the product; i.e., resources such as the number of pollers, add-on modules/product, etc.

The most valuable feature is the ability to use a few custom properties to manage multiple nodes and alerts; thus, saving hardware resource usage.

• Improved, more detailed service monitoring and reporting.

Dependencies: Created dependencies are not visible for management/editing by default until some tweaking is done. It would be better if this is enabled by default.

I have used it for months.

We have not encountered any deployment issues.

We have not encountered any stability issues.

We have not encountered any scalability issues.

Customer service is good.

Technical support is very good.

We previously used a different solution. We switched for better, more detailed service reporting.

A vendor team implemented it.

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 .

• Reporting
• Alerts
• Network map view
• Netpath
• Interface monitoring

With reporting, we are able to spool ISP WAN links availability for the month and make necessary deductions based on the service level agreement we signed with the service providers.

Alerts have also helped us to improve network performance, keeping everyone on their toes in resolving downtime before it is escalated.

I would like to see continuous improvement on the reporting and graphical views of customized portals.

We have been using the solution for ten years.

I did not encounter any issues with stability.

We encountered an inability to display graphical views of some customized reports.

I would give technical support a rating of 8/10.

We previously used WhatsUp Gold.

The setup is straightforward if you follow the OEM administrative guides and the server specifications and deployment.

Pricing is quite competitive. Licensing should be based on projected organizational growth.

We evaluated WhatsUp Gold and Entuity Network Management solutions.

Anyone planning to implement NPM or other SolarWinds products should download the evaluation versions which give you a 30-day, free trial. This will help you make an informed decision. This should also be evaluated with other network monitoring solutions.

I find there to be three areas in which this suite provides significant value.

It integrates well as an ‘everything’ tool. We all understand the concept of “jack of all trades, master of none”, but SolarWinds tends to cover 80-95% of everything across every module they have. This means that if I have vendor A for product A and vendor B for product B, there’s a pretty good chance they can integrate it with the rest of their suite.

For example, they have a network monitoring (NPM) core module that integrates with SAM (Server and Application Monitor) and NTA (Netflow Traffic Analyzer). This gives you a very good first view of an environment. It’s very analogous to SCOM in how complete it is with Microsoft products, but with none of the limitations. For example, SCOM doesn’t handle network equipment very well.

With just three modules, I can monitor server performance (whether it’s a VM, in the cloud, or an on-premises server. They can all:

• Be monitored as if they are on-premise
• Handle syslogs/traps/logs
• Monitor most applications out-of-the-box with a lot of flexibility
• See who sends traffic to whom via NTA.

All of this tends to display on a single page for each node that I choose to monitor. Every tool tends to build on one another and SolarWinds does tend to highlight where the tools integrate and how.

With staff that has some technical knowledge, this tool is pretty intuitive out-of-the-box. Getting people to look at it may be one thing, but getting those that are at least at a helpdesk level of knowledge serves to take them very little time to orient, if the tool is set up properly.

They have a THWACK support forum that is incredibly useful. I remember the days of trying to search for Microsoft problems and running into support forum posts that range from "useless" to “actually something that would harm your environment” with an extremely high noise ratio.

With THWACK, the developers will often reply directly in the forums with helpful replies. The community is also extremely helpful and fairly loyal. I’d consider it to be more like how I imagine that the Splunk community functions.

In a more recent example, we rely on this tool to let us know when a site is about to go down, before it does so.

We do this by monitoring when interfaces drop (multiple connections to a site) or when interfaces have received errors. Both typically occur before a site goes down entirely. It has helped us a ton to actually be proactive and not simply wait for customers to call.

I feel there are two areas of improvement. One of which SolarWinds employees will probably roll their eyes about and the other one that maybe they didn’t realize:

• If they’re going for a “cover everything” approach, then they need to do so and enable a bit more of the "cover everything approach" within every one of the tools.
  
• For example, if you don’t have the storage module, you won’t be able to even do the basic monitoring (interface, memory, CPU, etc.) for a NetApp device that you can do for other device types that are covered in other modules. Install SRM and suddenly it works, like magic!
• I’m OK with the concept of “you have to pay for the storage monitoring if you want to do storage monitoring”, but this becomes an issue in certain areas depending on what modules you license. This is also something that people may run into the hard way if they didn’t realize that this was the case.
• Some of the older components are in need of updating, which is something they’re focusing on more and more. But there are some areas where new tools work this way and old tools work that way. Some of these have gone away little by little, like classic report writer (which was on the server itself requiring RDP) and the old “advanced alert manager” which required the same. In today’s environment, having to RDP to the server just to do things that you’d do on the front end doesn’t quite make sense. There are some that still exist, though they are lacking some modern features.

I have used SolarWinds for almost five years.

There are a few things to watch out for regarding stability. All of them are basic administration issues. For example:

• Do run configuration wizard after EVERY single module update
• Do not give every user of the tool view rights and report rights, etc., where people are going to be messing with everyone else’s views and reports (or creating reports that kill the DB).
• Do create custom views so that people aren’t seeing everything and stressing the web client, etc.

In older module versions, there were issues where upgrading from module version A to module version B could sometimes carry over old things that had a performance impact on the app servers themselves. But these days, you can blow away the install and do a clean one to fix that.

On new installs, as of the latest few releases, they upgrade everything for you and/or have smart installers to make this significantly easier.

Scalability is something that isn’t quite straightforward for new admins. But, you can either:

• Install an additional poling engine on a second server for more scalability
• Install an additional polling engine on the PRIMARY app server for more scalability (stacking)

I rate technical support everywhere from poor to great. Lately, it’s been getting better and better. But in the past, it was very hit or miss.

I’ve used SCOM and CA before. We switched off of both because they were awful. CA cost a boatload and had a very limited feature set.

SCOM requires too many people to be dedicated to SCOM to be of actual use.

Plus, the aforementioned scope limitations and the requirement of having to go through *every* monitoring pack with every affected group in detail, takes up way too much time.

The initial installation is super simple. Pretty much you install SQL on one server, the app on another, and then you’re done.

I’d suggest that people be aware that licensing has tiers. Sales will negotiate on new product purchases as well as upgrades. Also, remember you can always run a 30 day trial of any tool you want to consider without committing any money.

We’ve evaluated PRTG, CA, SCOM, and Splunk.

It’s a super easy tool to use, but you need to make sure you have a plan for what you want to do with it.

• How easy it is to get good metrics out of it.
• How extensible it is.
• There are many different ways to customize it to fit your environment.

Compared to many products, SolarWinds is very simple to use. When you add a node in NPM, it is easy to get it to start monitoring everything it supports and you very quickly see the results of this in the graphs and such. When you want to get some special things out of a box, let's say the number of connections on a ASA firewall, you can very easily add a UnDP, add it as a graph to your screen, and see the results right away. This is a real-world example, because the company I worked with was having Internet problems with our main firewalls due to maxing out the number of connections going through the box. Having it graphically presented makes it easy, though.

That was one way of customizing it, via UnDPs. Another, that I did a bunch of at my previous job, and ended up making generic versions of and posting on THWACK, is the ability to add new resources. Any given page within NPM can be customized by clicking "Customize" and you can add quite a few prepackaged resources to a page or change their order around to better fit you. You might even want to delete some. But, if you get to be a SW geek like myself, you start realizing that SW doesn't always display every bit of info that it has by browsing through the SQL tables and seeing what’s there. Nowadays, you can do this either directly with SQL, or via SWQL, which is a bastardized SQL that has pre-built relationships between the tables set up in a way that is very easy to leverage without complex joins and such in SQL. From that, you can do some very simple to very complex things.

An example of a simple thing I did, was I built a "CDP Neighbor" resource, which, if you click on the Node Details page, it tells you what devices are directly connected to it via the CDP protocol. Plus, SolarWinds made it simple for me to link to those nodes and you can basically traverse from node to node within SolarWinds looking at stuff.

Before NPM, we had to spend quite a bit of time using freeware tools, because there wasn't anything that offered the features we needed at a price point we were willing to pay. Most were far too expensive. Because of this, we only monitored some key devices and links. With SolarWinds, it’s easy to monitor everything and, with a little setup, everyone can help out. NTA brought things up a notch. Rather than seeing there was too much bandwidth being used and trying to guess what it was through diagnostics on the device and guesswork, we can see what is consuming all the bandwidth and easily relate it back to a specific user or device.

The module UIs can have different features based on what module you're in. I'd love to see feature parity between them. Selecting nodes, for instance. In NPM, you can use one criteria for grouping, while in NCM, you can group in multiple levels.

More granular permissions! I'd like to see a role-based system where you can granularly apply permissions for administrative tasks and be able to assign these roles to people. Just because you need to edit a node doesn't mean you should have full admin permissions!

Stability depends on the module/version. In general, it is very stable if you wait a bit before upgrading to the latest version and let some patches come out. There has been a problem in NCM when you deploy compliance remediation jobs to a large number of nodes that use config blocks that has persisted through a couple updates. But this is a pretty advanced feature.

We haven’t had scalability problems so far. The different jobs I've been in have had very different environments in terms of scale and this solution works at any level.

Technical support is very good. It might take a bit of time for initial contact, if you don't classify the severity high enough and don't call them. But a phone call will always rectify that.

At the different jobs I’ve had, it was a mishmash of different freeware tools and things like CiscoWorks/Prime or WhatsUp Gold.

Basic setup is a breeze for most folks!

In general, pricing is pretty good. Although, the jobs I've been at have usually had unlimited licenses. I have heard some people have issues with the pricing and licensing of another module (SAM).

We evaluated WhatsUp Gold and Cisco brand tools.

Download a demo and have fun! It’s easy to use and gives great outcomes.