SolarWinds NPM Reviews

We use it for network monitoring, internet monitoring purpose and server monitoring purposes.

It allows me to see a summary of the network being monitored at a glance.

SolarWinds dashboard is very fast. Also, their interface is very good, it looks very user-friendly.

The time monitoring could be improved from every five seconds to every second. If they can move to an every-second basis, then it will improve the monitoring analysis.

I would also like to see the security system updated to prevent virus attacks.

I have been using SolarWinds NPM for around 10 to 12 years.

We have found it is definitely stable.

This product is scalable by purchasing extra modules for more servers.

They're one of the most responsive companies when it comes to support.

Positive

The initial setup wasn't complex, but not as easy as some systems either. It requires someone with experience with the network monitoring system. 

It was implemented in-house.

The charge is currently made per module for the product, and there is no option to buy it as a full system bundle which makes it costly. Also, charges are made annually, it's not a perpetual purchase.

It would not be affordable for SME level organizations.

The other solutions I evaluated were:

• PTRG
• Cisco
• WhatsUp Gold.

I would rate this product at 7.5 out of 10.

The two most important features are SNMP monitoring capabilities and the beautiful web interface. SNMP is all about being able to access devices, it's a must have, and every monitoring tool will have these features. Not all monitoring tools will have a beautiful graphical user interface that includes charts and graphs and reports. It's very, very easy to read and work with. This is important because we are all humans, and we want nice things. We want nice gadgets and the people who are actually using SolarWinds are engineers. They are all humans, as well, so they want nice things.

It may sound trivial and pathetic, but it's really important. One tool can do a hundred times better than the other, but if the presentation layer lacks this beauty, then people just won't use it. They will be lost and they won't use it and they won't appreciate the complete power of the tool. The elegance and the way it's implemented is very important. It's very, very important from the elegance perspective alone, not just from a usability perspective.

There are multiple examples of how SolarWinds improves how the company functions. The most obvious is that the engineers are much more willing to keep an eye on network health and to work with the dashboards. That leads to faster resolution of problems and better communication between the teams. Instead of explaining and spending a lot of time, they can simply send the link to SolarWinds and directly access what they need.

Additionally, there is the flexibility to automate or semi-automate functions completely. As a result, we don't need as many people as before when we were working on the reactive side of things. If our service desk had five people before, now we have none. Infrastructure engineers handle most service desk functions, such as ad-hoc or BAU tasks. But we don't need dedicated service desk people anymore.

I work for multiple clients, so I'm just giving examples from them. Some clients do need to maintain service desk functionality as a business function. SolarWinds certainly helps to reduce the workload on the front end at level one and level two escalation. Clients have much more free time to focus on the things they like doing and leaving all the mundane tasks to SolarWinds to sort out. It's a definitely time saver. I love everything about SolarWinds.

We have been using SolarWinds NPM for about three years.

We have not had any problems with stability. I think the way it's implemented it's pretty robust. I started to use SolarWinds three years ago; not from the beginning 15 years ago. So, I don't know what it was like then. From my experience over the past three years, it has been a fairly stable system. Often, clients underspec the platform and SolarWinds requires quite a lot of resources, especially on the database and on the disk-use side, and it needs to be planned. Some customers simply get a box, install all the modules in one box and then complain that SolarWinds is slow. It's not SolarWinds. It's an underspec'd platform.

Some clients think, "Oh, it's all SolarWinds' problem. SolarWinds doesn't perform well." When I come to consult them, we quite easily find that it's the server struggling and not SolarWinds.

The bottom line is this: I am a SolarWinds expert. I know what I'm doing. They are not experts in SolarWinds. From their perspective, what they see straightaway is SolarWinds is not performing well and it can mislead them to think that it is SolarWinds when it's not.

Again, to summarize, I don't think SolarWinds has any performance issues or problems if correctly planned. Go through the documentation and make sure your environment meets the recommended minimums.

The most important point I'll make is that SolarWinds markets its product as an out-of-the-box, click-click-click, do-it-yourself solution. It may work like that for very small organizations, although very small organizations will probably go for Nagios or other free tools. For larger enterprises, this is not the case. Just clicking next, next, next to discover nodes, and everything just works, is not the case. It appears to be working, but when you go beyond that and start to understand how the workflow operates, how people respond to alerts, who receives them, who is not receiving them, how to manage thresholds and many other issues, they all add to a much larger picture. That then becomes a not-out-of-the-box solution.

To work with it properly, you need to have extensive skills and knowledge around the SolarWinds product. I'm not saying that you need to be a geek who knows coding and APIs. But you do need to be well aware of what's possible. That helps you set up SolarWinds the way the client wants. Once it's set up, running and maintaining it takes pretty much no time. It functions almost on automation. This is why I think there's still a huge need for consultancy work. Organizations need experts to deploy SolarWinds and to help them to define exactly what they need. Then the organization can manage themselves. They just need to be properly trained.

Many times I have seen SolarWinds installed and then it would sit for years doing nothing simply because the people there don't know what to do and there's no time for anyone to actually to dig in and make a masterpiece out of it. It probably shouldn't be advertised as an out-of-the-box solution.

SolarWinds has scalability solutions and it's completely extendable and expandable and the licensing model is just beautiful. I love it. It can be as cheap as a few thousand pounds, which is very affordable to smaller organizations. It can also be as expensive as tens of thousands of pounds, which is still very, very cheap even for enterprises and bigger organizations. If you compare it to other solutions, it's at least 10 times cheaper. The scalability models are beautiful and there are no problems whatsoever handling a large amount of work. If you need more nodes, you can always add more servers and expand your platform with an additional poller. There's always a way to manage it.

Technical support is probably 8/10. Sometimes they tend to respond a little bit slower than I would want, but it's not unusual. If you want something, you want it now and that doesn't always happen. Sometimes I need to wait a few hours or even a few days. Sometimes I need to chase them a couple times. Other than that, the level of skills and the support I receive to actually solve the problem is next-to-none. It's probably a 10. I'm giving it an eight just because of the response time, but other than that it's really good.

However, the sales team at SolarWinds is extremely aggressive and I would give it probably a 1/10. It's very interesting that these different teams are working in the same company. The support is so wonderful, and I know a lot of product managers there. I know them personally and they've been in London and we've talked. They're all techie so they're all great guys. When it comes to sales, they are very, very aggressive. I keep receiving calls and they keep pushing and they keep offering discounts. I don't need those discounts. Just give me my time, you know? When I'm ready with a decision, I'm ready. The way I see it, I'm an engineer and I'm doing the solutions. Aggressive sales is not good. It can be frustrating.

I tried different alternatives, but I was never really able to set up other tools the way I wanted. I consider myself a very creative person; an artist so to speak. I come up with something in my brain, I like it, I make a note and then I try to implement it. Very often, with other tools, I was just stuck. I wouldn't be able to do this and that and then I would be coming up with my own bespoke solutions, using my own bespoke scripts. I'm doing them manually and sending manually.

With SolarWinds, everything just works. It's not that SolarWinds has everything I need. It's that SolarWinds gives me enough power to implement everything I need. It's a proper platform. I don't think about it as a tool. When I have an idea and SolarWinds doesn't provide it, I implement it. I write a script or a SQL script or VB, or PowerShell, or whatever. Then I simply attach it to SolarWinds and voila, suddenly SolarWinds is actually is giving me the output that I need; drawing charts and graphs and generating reports and it all works. Then, in a click, I can apply the same monitoring to hundreds and hundreds of nodes, which is awesome.

When working with clients, I tend to compare my experience working with different monitoring platforms to SolarWinds. Without really going too deep in understanding how things are done there and here, they just say, "Oh, you know what? We want SolarWinds." I'd say, "That's fine, so let's do SolarWinds."

I’m doing initial setups all the time. As a consultant, I go from client to client on a regular basis. The setup is by far the easiest setup of any software that I know. Not only monitoring software, but any software. Even installing Microsoft Office is more complex than SolarWinds. It is really, really easy and straightforward. The wizard provides many guides and notes. The deployment is so well tested and structured that I literally click through the wizard.

Out-of-the-box, it works beautifully. But when it comes to the logic and company workflow, that's when I need to add a bit of a creativity.

I'm not doing sales and marketing, so I'm not really trying to sell the product. Usually, they have already done their thinking and decided to purchase SolarWinds. Then they call me to implement it. I evaluate what they currently have in the infrastructure in terms of devices and interfaces and the whole network structure. I make sure that whatever they have matches what they need. If it's too much, most of the time they say, "Okay, so we overestimated." I'm like, "That's fine. Let's just be more rather than less." Sometimes they purchase unlimited licenses when they don't really need them. Often they purchase too little and we simply go and purchase a license, which is a fairly easy process. The customer portals are all managed very well.

New clients will sometimes ask, "Okay, so let's run through today's simulation, let's see how it works and then we will make a decision." They know I'm going to install it and then they'll evaluate it and find that they're happy. For me personally, I know SolarWinds is releasing new, major releases at least once, maybe twice, a year. I'm on the forum watching all the new features and releases, and adding my own input. I'm pretty much in the know about what's going to happen next, and I'm always anticipating starting working with new features. I don't go and explore anymore; I already know what's in there.

Obviously, the actual process of testing is very fulfilling, as well, especially after we've been communicating on the forum and suddenly it's all live and working. The forum is the number one place I go for my information.

I would advise to get a consultant, at least short-term. I have found that companies, especially big ones, and even some small ones, don't need a SolarWinds expert on site all the time. It's too expensive and unnecessary. At some point, the expert will just sit and do nothing. I think it's absolutely proper to get someone at least for a month, maybe two or three. They can then advise you to pick the right product, choose the right tools, implement it in the right way, and to set up the workflow alerts to make sure it's working.

It seems like the sales team has a slight disconnect from the presales guys. It all works well, but as I said, the sales team sells a product. They do not actually help deploy and implement workflows. They expect the company themselves to deploy and set up their own workflows and then to rely on the documentation and the forum. In reality, they just don't have time. They have their own functions and responsibilities and SolarWinds is a new project for them. It's a huge stretch to learn something new. You know that. It's human nature. That's why my advice is to get a consultant.

SolarWinds NPM is used for searching equipment in the network, troubleshooting the network, and mapping the networking.

The most valuable features in SolarWinds NPM are the network search and diagnostic tools.

SolarWinds NPM could improve by adding the deepest inspection, performance networking, and IP address discovery.

I have been using SolarWinds NPM for approximately three months.

SolarWinds NPM is stable.

The scalability of SolarWinds NPM is easy to do.

We have three or four users using this solution.

The support is very good for SolarWinds NPM.

The initial setup of SolarWinds NPM is easy.

The cost of the personal perpetual license for SolarWinds NPM is approximately $2,000.

I recommend this solution to others.

I rate SolarWinds NPM a nine out of ten.

It is for our current infrastructure or servers and storage system. We're using it globally to monitor our global network. We are currently monitoring all the infrastructure APM, network, switches, and routers. We have some elements in the UK and the USA. 

It covers everything from end to end, from the standpoint of endpoint machines and the routers and switches. The switch port also comes there.

It has covered everything, so no improvement is required at their end. The only thing is the price. 

We have been using this solution for around eight years. 

It's stable. We didn't face any issues in the last period.

It's scalable. We see expansion there. More than 500 users are currently using it.

We contacted them once last year. We requested their support with an upgrade. They were very helpful.

It's easy and straightforward. There is no complication. 

We deployed it in one day. We had POC in one day, and we prepared the servers, virtual machine. We did the installation, database setup, and firewall setup in one day. It was easy.

We get some consultants. If there are some challenges, then we definitely need a consultant.

It is too expensive.

We also use Microsoft Operation Manager SCOM. Microsoft is dedicated to monitoring servers, but it needs some improvement in network monitoring. SolarWinds is more appropriate.

We are also comparing SolarWinds NPM and Zabbix. Currently, we have SolarWinds NPM, but its license is about to expire. We need to see which product is suitable for our environment.

I would recommend SolarWinds NPM. From the product side, it covers everything. It is perfect.

I would rate it a nine out of ten.

I am working at a company which is an Internet service provider (ISP). So, I'm monitoring the traffic on some nodes, like switches, routers, firewall, the traffic, and the CPU.

I am using the latest version, which I just downloaded from their site.

There is a customization feature, but it is not a good feature. While it's somewhat good, it is too complicated.

The aesthetic widgets should be dynamic widgets, so the customization can be even more customizable.

It is stable.

It does not take much staff to maintain.

It is scalable, but my network is not that big. We have just a few nodes.

For technical support, we are dealing with someone in Ireland. I have not always received responses to my inquiries.

I previously used PRTG, but PRTG is now forbidden in Libya. So, we switched to using SolarWinds and ManageEngine OpManager.

The set up was very easy. We didn't have any problems with the setup. The deployment took less than an hour.

We used a SolarWinds reseller for the deployment in Libya. We found them on the SolarWinds website.

The pricing is very expensive for SolarWinds. That's a huge disadvantage for it.

PRTG is easier to use, but SolarWinds is more customizable. SolarWinds also has more features, but they are complicated to use.

We are just trying the demo. I am not going to recommend this to my company because PRTG is much easier. We're looking for something that is very easy to export the reports from the dashboard. SolarWinds is sort of complicated.

If you are looking for something which is very customizable for the customization of your network, then you should go with SolarWinds. However, overall, the customization feature is also a disadvantage because it can be very complicated.

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 .

• Real-time netflow data
• Highly customizable alerting & reporting
• Very large base of information, further customized by high compatibility with MIBs from many, many vendors, resulting in very customizable UnDPs

Being a global company with many highly-sensitive manufacturing lines and process control environments, SolarWinds consistently delivers real-time and accurate views into the deepest parts of our environment. Though my role is 100% network-side, SolarWinds has greatly benefited our team of systems-side admins as well.

Because SolarWinds is built upon a SQL database, some level of SQL query knowledge is necessary if one really wants to take customization of alerting/reporting to a deeper level. This is really difficult for someone who

1. Doesn't have the time to devote to this
2. Doesn't have a strong background in any sort of software development/coding

I've used it for three and a half years.

I was not around for the initial deployment, but I've been responsible for maintaining the environment over the last three and a half years, including product upgrades and migration(s) to new VMs.

At times, we've had trouble with lost data within the database. These were largely resolved by moving to a more stable database server. I don't recall any recent issues now that we're on 11.x.

Yes, but only due to our own willingness (or unwillingness) to deploy additional polling engines. We're actually researching this feasibility right now, so that we can support a greater number of devices globally while maintaining a centralized "pane of glass" for administration.

This is one area where SolarWinds can do better. Customer service, in terms of account renewals, and licensing, and so on, is very quota-based. They need to make their sales/transaction quotas, and that's about all that matters. They can be very pushy when it comes to the purchasing process. I think this is probably due to SolarWinds being THE solution for network/systems monitoring, and they know they have some level of a monopoly on the industry. SolarWinds is also not a cheap product -- it's very expensive under a CapEx consideration, and annual renewals are about 10-20% of the initial CapEx. So, it's not inexpensive.

This is also an area where SolarWinds could do a lot better. Every time I've opened a case, they agree to a screen-sharing session (GoToMeeting/WebEx, etc) as an absolute last-resort. Sending me KB articles and other suggestions is always the first three to four emails, until I can formally get them to agree to take a look "in-person". I greatly enjoy working with Cisco TAC mainly because of their complete willingness to dive head-first into the issue by STARTING with a screen-sharing session. It gives me, as a customer and end-user, a much greater appreciation for Cisco's interest in resolving the issues, and making sure our production-affecting problems are no longer present.

In-house implementation.

As far as I know, SolarWinds was really the only option at the time.

It was an in-house implementation.

As far as I know, SolarWinds was really the only option at the time.

Don't assume SolarWinds is the right choice. Evaluate LOTS of other alternatives. These days, SevOne is a very promising competitor. But if you choose SolarWinds, dive into it as deeply as you can. Take advantage of their free online classroom training sessions (it's thousands of dollars for you to pay for from a third-party training vendor).

We used SolarWinds for network switches, routers, firewalls, and servers, and to collect performance data for items on a global scale. We have 1,000 to 1,500 users.

The ability to customize the views and dashboards is nice. SolarWinds also allows us to access the data via the API. That's probably the feature I liked the most.

It would be nice to have a test to check if you can access a particular device via API without installing it and waiting for a poll cycle. You should have the capacity to initiate a test to see if it was reachable and get the results almost immediately.

I have been using SolarWinds NPM for four or five years.

SolarWinds was pretty stable.

SolarWinds NPM is scalable.

SolarWinds provides good support.

Setting up SolarWinds NPM was relatively straightforward. There is always some complexity, but it's usually pretty straightforward. Two technicians were able to set it up.

We set up SolarWinds NPM in-house. 

I rate SolarWinds NPM eight out of 10. I recommend taking advantage of the online training that's available. Get an account on THWACK, the online user group. It's good for getting help.