SolarWinds NPM Reviews

We use the product for network monitoring. 

SolarWinds NPM provides an overview of network monitoring, extending its capabilities to cover other aspects, such as virtual machines and servers. The platform has features like NetPath, which is particularly beneficial for end-users, offering insights into issues like latency, packet loss, and connectivity problems with routers, switches, or servers. NetPath helps identify where the network path is disrupted or experiencing problems. For instance, if accessing Google services encounters issues, NetPath can pinpoint where the problem lies.  Another valuable feature is that it provides real-time data on device performance, including resource utilization, RAM status, and responsiveness.

The tool can only monitor up to 1000 instances in a single SolarWinds console. Customers may have over 1000 instances. Hence, it needs to support a minimum of 1500 instances. It should also improve support. 

I worked with HPE for about six to seven months in 2016. It had similar features to SolarWinds NPM. However, the deployment process was complex.

Deploying SolarWinds NPM is a straightforward process. The deployment steps include extracting the files, mounting them on the server, and deploying them. The documentation provided by SolarWinds is clear. 

While I haven't extensively worked with ManageEngine, I've observed some of its features, and customization stands out as a strong aspect. ManageEngine can be a good option for those with budget constraints, as it offers similar features to SolarWinds NPM at a more affordable price. I rate the solution an eight out of ten. 

I primarily use it in the OT environment. We use it for important equipment, voice equipment, safety devices, and to alarm and report on.

Solarwind NPM gives you a quick overview of the OT environment. This greatly  improves response times on down equipment.

The solution is quite customizable. 

The initial setup is straightforward.

The solution is stable.

We have had a good experience with technical support.

The product is scalable.

So far, we have found the pricing to be reasonable. 

It meets expectations. With a bit of SQL knowledge, you do manage to get a lot out of your reports.

There are still huge concerns about security. The image of Solarwinds NPM took a huge knock due to SUNBURST and SUPERNOVA. Security experts are still concerned. I would suggest that Solarwinds put more effort into rebuilding trust with the customers and the market.

I've been using the solution for five or six years. I've been using it for a while. 

The stability is great and any issues we face are addressed very quickly by technical support.

The scalability is there. If you need to scale the solution, you can. 

Technical support is good. All of the issues I had were addressed by the support team within hours. They are helpful and responsive and I am satisfied with the level of support.

The initial setup is not difficult or complex. It's quite simple and straightforward.

We have an internal team that can handle any maintenance we need.

In-house

As we monitor safety equipment and underground phones, the first incident you can prevent and save a life, the ROI is instantaneous. 

The product compares well against all the other monitoring software out there. It is not overpriced at all.

We're just customers and end-users.

The solution is easy to use and customization is possible. It is extremely powerful when set up correctly.

I'd rate the solution at an eight out of ten. We've been pleased with its capabilities, although its level of security is still worrisome.

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.

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.

• 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.

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 6.3.1.575

Scalability and HA will impact larger customers. The current HA release requires the redundant nodes to be on the same VLAN. This limitation is being actively addressed in version 12.2 which is in beta testing as of the writing of this review.

Scalability is fit for most customers with capacity for over 10K devices (~100,000 elements). As with all applications running at scale designing your infrastructure is key. The published specs will need to be tuned for your environment at both the polling and database layer to push your implementation beyond 10K devices. (See notes below on scalability)

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.

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.

Customer service is exceptional if not a little too communicative at times. SolarWinds does an exceptional job of engaging their customers.

Technical support is currently the achilles heel of SolarWinds.

• Non-critical issues can be handled through an extremely active and passionate user forum (at thwack.solarwinds.com), 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.

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.

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.

We implemented through an in-house team but that team consisted of a lead engineer who is now a SolarWinds Head Geek. You can absolutely deploy this without professional services but depending on your timeline, objectives, and workload within your organization you may need to engage the services of a consultant. There are many freelance and corporate freelance options out there but be sure to ask around about their experience.

Reduced annual support costs by 75% year-over-year based on our prior solution.

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.

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.

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.

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.

We use SolarWinds for network monitoring. It's suitable for mid-sized or enterprise-scale companies. It can work for a small business, too, because it's not too expensive. 

SolarWinds' network and server application monitoring features are strong.

SolarWinds could offer more support and insights for a broader range of devices. Currently, it focuses on routers, switches, and some load balancers. However, it lacks an out-of-the-box dashboard for monitoring firewalls and some other modern network security devices. We have to customize it a lot.

At the same time, some tools don't have the ability to customize, so SolarWinds is ahead of the competition, in that regard. I would also like to see more support for software-defined network platforms and enhanced API monitoring capacity.

I have been using SolarWinds NPM for more than five years.

SolarWinds offers some options for scalability, but there is a bottleneck on some features. I hope the scale of NetFlow can be increased. Also, SolarWinds uses the Microsoft SQL database, which doesn't allow distributed architecture or scaling options.

I rate SolarWinds support seven out of 10. The quality varies depending on who picks up the phone.

In most cases, setting up SolarWinds is simple. However, when customers have some special requirements, the deployment can become highly complex.

I rate SolarWinds NPM six out of 10 for pricing. It isn't the cheapest solution, but it's still affordable.

I rate SolarWinds NPM eight out of 10. I would recommend this product for medium-sized and enterprise-scale companies.

We are a mining company, and we use this solution to monitor our system operations. We monitor the truck service, and we have the network devices installed onto the equipment.

Their support team is efficient, and it is easy to set up.

The root cause analysis and installation faults are not clear.

I have been using this solution for two years.

It is stable.

Their support is good.

It was easy to set up. It took less than a month.

I would recommend this solution. I would rate it an eight out of 10.

We primarily use the solution for network health.

The ease of deployment is great. I also would say that it gave us good capabilities to tune alarms. 

I'm overall a huge fan of Solarwinds. To me, it's a top quadrant for a solution and I would be pushing for it internally were it not cost-prohibitive for startups.

The solution is stable.

The scalability is good.

The initial setup is easy.

The downside was the expense. At large, large companies, that's okay. However, at companies like mine where we're building a tech startup, it can be cost-prohibitive.

They've had some issues with security, and confidence in their product is probably down.

Technical support can be slow to respond.

I would like to see more of a focus on edge computing and edge device monitoring.

I've used the solution for several years.

The stability is good. Aside from the very public hack, from a user's standpoint, it's good.

It's easy to scale. I'm probably an avid fan and I'd say it's easy to scale. 

We have around 100 to 150 people using it at our company.

We didn't always get the responsiveness that we needed in terms of the level of urgency. If it was something where it was potentially project-related and very time-sensitive, they didn't match our level of urgency which could be frustrating. 

That said, overall, when it came to deployment or wanting upgrades or improvements or changes, that we would get good support. 

Still, for incidents where you are in a mission-critical and you have an incident that you need assistance with, they weren't always as quick to respond.

The initial setup was pretty straightforward and simple. A company wouldn't have any issues with it. It's somewhat easy to deploy, however, I'm not the engineer. I was the business leader. I just know that I never received any complaints.

The solution is expensive and may not be very affordable for startups or smaller companies.

We're just customers and end-users.

We are likely using the latest version of the solution. I cannot speak to the exact version number.

We use both the public and private cloud deployment models. 

I led a team of several hundred engineers who used SolarWinds every day. I would be involved in making the decision of a product to go through. Once they came in and recommended me their top three, I would choose it.

I would advise potential users to first take a look at some of the newer vendors on the market who may be a little bit more nimble and are coming out of the box with a focus on edge and edge devices. SolarWinds has a heavy, heavy background. There are lighter options. 

I'd rate the solution at a seven out of ten.

We have been making use of the most recent version.

We use it for monitoring our uplink ports on our routers and switches. We also use it to monitor our servers and we utilize its disc space and processor memory. We do the same thing for the routers and switches.

An improvement the solution has brought to our organization is that it enables us to track down what I call brown outs in a multi-host, multi-guest virtual environment. It allows us to see why and when this occurred and to know what else was transpiring at the time that we had received an end-user complaint of the system running slowly. 

As we look to add more servers to our virtual environment and to understand the impact, the solution allows us to dig into the historical charts related to capacity planning. It also gives us visibility of spikes and allows us to track down the reasons for their occurrences. So too, it makes room for potential processes that have gotten hung or runaway and to know when it's time to reboot a server or service. 

The solution should make things easier to set up on a node by node basis. When turning on the network scanning to try to set up nodes, it has a tendency to grab everything in site, every port on a firewall, for example. One should have the option of picking through these before they're automatically added, so that there should be no need to go through them manually and delete them. The solution's network discovery and node addition processes need more work. Once the nodes have been added, there is a need to go in and delete them manually. 

I cannot think of additional improvements that are worth mentioning. The solution does a pretty good job all around. 

We have been using some version of SolarWinds for 20 years.

The solution is very stable. We don't see many outages of the actual platform. The sole exception would concern us taking a process in which we would be restarting it on a monthly basis. 

The solution is very scalable. I've never seen a problem with this.

I don't have any plans to increase the usage in the future. I would not say that the solution is being extensively used, as we're not necessarily monitoring everything that we could, there being no need for some of this in our environment. I would make use of the performance monitor should I wish to dive deeper into a running system for detailed analysis.

As I have been using the solution for so long, I have not had any need for technical support. 

I have used other products prior to SolarWinds NPM. I switched because the solution provides a consolidated view of everything. 

A moderate level of knowledge of the product's use is required for installation. 

The initial installation occurred a long time ago. While, for me, this process would not take long, somebody who is new and who has never used the solution may take a day or two to do installation and to become fully up to speed of what is being added, the reason for doing so and how the solution should be configured. 

Installation is not easy for a person who lacks the requisite experience. 

I did the integration myself. 

I renewed the licenses around two-and-a-half to three years ago and do not have the relevant numbers off the top of my head. 

I would estimate there are three insfrastructure managers, with myself as the head of the IT department. There is at least one other technician working on the wide area, local area network.

My advice to others is to add their nodes manually, not to let the network discovery and auto ad run.

I rate SolarWinds NPM as an eight out of ten.