SolarWinds NPM Reviews

We have a lot of “home-grown” apps to handle the interesting and challenging monitoring requests and alerting needs.

This product is extremely flexible and customizable. It will do just about anything you need it to do. Out of the box, there is a significant amount of monitoring you can do with very little setup. Then, with custom properties and some ingenuity, you can get it to do pretty much anything else. Additionally, there are a lot of ideas and support in their forum, Thwack.

With custom properties and the alerting flexibility, we’ve been able to customize the alert trigger and reset logic to meet the needs of our users, as well as eliminate the likelihood of making mistakes in the operations center.

We used to be fraught with scenarios, such as:

• Only call if the alert doesn’t clear after 45 minutes.
• Ignore that alarm.
• Don’t call on that night.

The SAM custom script for running component checks only supports 10 pairs of results. I am not sure whether this is a scalability issue. It would be nice to have the option to do more. We worked around it by doing a component check per pair as much as we needed.

The product is excellent at taking feedback, especially from the Thwack form, and implementing popular feature requests.

We’ve been using it for almost 10 years.

Back in the early days and new major releases, of course, there were some hiccups and gotchas. Bleeding edge, baby! It’s all a matter of risk assessment with new feature needs, etc.

We have not run into scalability issues.

In general, the technical support is great. Around new major releases, you do experience longer waits; and every so often, you get a support technician who is newer. Still, if you call in and it’s critical, they fix your issues in a timely manner. This is to be expected; and you need to take this into account in your risk calculation when you schedule upgrades.

We were previously using HPE OpenView. The biggest reason was its lack of mapping flexibility at the time. The ops part is still very visual with the green/yellow/red color-coding of icons. Our systems side is based on alerts and emails.

I don’t recall any troubles during the initial setup. It was a long time ago. I was enamored by its mapping capabilities.

• The software is structured and priced well. It’s not cheap; but it’s not overly expensive either. You get what you pay for, and they are well positioned.
• You are able to spread the costs out by implementing it in steps. Your team is probably not huge. You don’t need to sit around waiting to install and configure the entire monitoring solution. Start with NPM, and start adding modules and capabilities as your existing implementation matures.

We were required to assess alternatives, but I don’t recall the specifics. When implementing SAM in the last 2 years, we moved from Big Brother and evaluated Nagios.

• Gather the official requirements for a monitoring solution, and alert all the consumers. The consumers here are the owners of the monitored gear and apps, and the engineers in the support and ops teams.
• Set a good chunk of time aside to test drive the solution, and get creative with the custom properties.
• Learn SQL or SWQL, a SolarWinds query language that is easier than SQL. This will expand your potential capabilities for customization significantly.
• I am very active on the forum. I get a bunch of ideas and help; so I like to give back.

My company uses SolarWinds NPM for interface monitoring because we are not required to put in any keywords and do the manual thing, making it easy to onboard. In our company, we just export the device and download the configuration, while the NCM part can be enabled by going to the settings and changing the configuration. The solution becomes easy if you use everything on a single dashboard.

My customers have experienced benefits from SolarWinds NPM since it supports Akamai Guardicore, Akamai Synthetic Monitoring, and VMware-based device monitoring. In general, SolarWinds NPM integrates smoothly with every solution. The integration part of the solution might not be as easy as it seems since one may have to enter some commands in JSON format in the integer part. The templates are already set in the solution, but there is a need to change the parameters, values, and IPs. After the aforementioned steps are followed, integrating the solution with tools like Tableau, Power BI, ServiceNow, and Microsoft Teams for notifications and alerting an incident becomes easy.

Though in SolarWinds NPM, there is no need to go into other interfaces and set up some settings with other parameters, SolarWinds NCM allows you to do so more easily. We just put the configuration and execute the particular IP, or you can just put the Excel sheet, where once the import is done, it shows all the IPs there, and so you just need to do the configuration and execute the IPs. The solution provides you with real-time data, including details like how many devices are completed, how many are left, and how many are getting errors.

The dashboard of the solution is an area with certain shortcomings that need improvement. Having all the features and parameters under a single tab in the solution would be good. For knowledge-related purposes, SolarWinds needs to consider adding documentation to its portal to provide users with the upgrade command if they want to upgrade the solution and how to carry out the onboarding procedure.

I would like to see real-time visualization and monitoring, especially when attempting to connect globally where one router is in the USA and the other is in the UK. With real-time visualization, all the interfaces can be made visible properly, while the users also get more visibility and their network. If an interface goes down, then one can monitor the interface directly with the help of the dashboard provided in the solution.

I have been using SolarWinds NPM for nine to ten months. I operate as a system integrator for SolarWinds. I use the open-source version of the tool.

It is a stable and good solution.

SolarWinds NPM is a scalable solution since it can handle a huge number of users. When I joined my current organization, I saw SolarWinds NPM handling 10,000 devices, including the backup, storage, and everything else. SolarWinds NPM never had any performance problems, like hanging or lagging issues, and this may be because the solution only has a few features in it.

For SolarWinds, my company needs to send an email to the customer support of SolarWinds, after which they will reply back to us with their incident number, and then work on it. If required, the customer support of SolarWinds will set up a call with our company to understand the real-time situation at our end.

I rate the support team an eight out of ten.

Positive

Though I wasn't involved in the deployment process of SolarWinds NPM, I was involved in Fortinet FortiCloud's deployment. With the deployment part, my customers have deployed SolarWinds NPM and Fortinet FortiCloud on the same server.

My company's current customers plan to replace SolarWinds NPM with Fortinet FortiCloud.

In comparison to other tools in the market, SolarWinds NPM hasn't been upgraded yet. I believe SolarWinds NPM plans to upgrade itself in the future and have more features, like the ability to support other devices or vendors, like Arista, Juniper, Guardicore, or Akamai. In terms of the advantages provided by SolarWinds NPM, I would say that the solution is easy to use, easy to onboard, easy to set up, easy to delete, easy to configure, easy to get the report on a single interface, and one can also apply a filter to get what is required.

In the last four years, I have deployed three tools in Avaya and another four in my current organization.

The maintenance of SolarWinds NPM is not difficult.

SolarWinds NPM is one of the easiest and most flexible tools, but I would say that SolarWinds NCM is a better tool. I rate SolarWinds NCM a nine out of ten.

I don't know if there have been any upgrades in SolarWinds NPM. Considering the performance graph, one will see a clear visualization in SolarWinds and not in Fortinet FortiCloud.

I rate SolarWinds NPM an eight out of ten.

We use SolarWinds as a monitoring platform.

It monitors all of our network gears for up-down status, for the most part. We can also see utilization being high at a given location.

The alerting has been the biggest aspect we appreciate. In regards to utilization, it can be proactive in regards to addressing situations before some cases arise before the users even see them.

The initial setup is simple.

It integrates really well with the Cisco platform. We are a Cisco shop. I don't know how well it's going to integrate with us moving to Aruba or going with other vendor hardware, how well it's going to integrate, I guess we'll find out.

It is scalable.

Technical support is helpful.

The stability is good. 

The only real caveat that we have or that I have an issue with is when I go on vacation, it's a little hard for me to go and modify alerts so that I don't get alerted about things when I'm on vacation. There's not a way to turn me off from alerts easily.

There really hasn't been anything that we've needed that it hasn't been able to provide. 

I've used the solution for at least 17 years. 

The solution is stable. there are no bugs or glitches and it doesn't crash or freeze. It's reliable.

We've got about nine different Sys admins that use it on a day-to-day basis, at different locations, to check on different things.

Contact support was great. They're very knowledgeable. They knew what we needed, once we explained our problem. In some cases, they helped us figure out a different solution than what we were looking at. They knew the product pretty well for everybody that we've dealt with.

Positive

We didn't use a different solution. That's what was here when I started 17 years ago and that's what we've stayed with.

The setup was pretty straightforward. We just went through a complete redeployment part of upgrading to the latest and greatest as we upgraded servers and databases and the whole nine yards. We just simply did a fresh install. It was pretty easy.

It probably took us about a couple of days. We had to go back in and once we re-added the location, we had to go back and tweak what we wanted to monitor, and that kind of stuff. We didn't simply just do a migration. It was a little bit of doing the network re-discovery and then going in and tweaking the individual locations. 

The one thing we did migrate over was the alerts. We didn't have to recreate alerts from scratch, however, it took us a while. We've got 400-plus devices that we monitor. It took a little while to get all of the devices back in the way they originally were.

We did everything in-house. We did not use consultants or integrators. 

I don't know anything about pricing. It's not an aspect I deal with.

We deal directly with Solarwinds. 

We have been keeping the solution updated. 

I would recommend the solution. A lot of our colleagues use it and we like the way it works. I'd rate it ten out of ten. 

I'd advise potential new users to give it a good rundown and see if it really fits what they need. Don't just try it with one or two things. Do the 30-day evaluation. I have folks that have used it and try to find some way to break it really. Load it up the way that you want to run it and actually take time to dig down into it. So far, there hasn't been anything that it hasn't been able to do for us. However, it's designed for that Cisco environment and that's what we've always been. I can't really talk about it outside of the box.

The most valuable feature is the way it monitors the environment, and how user-friendly the console is for the end-user. The interface is also very easy and it captures all the information very well.

This product could improve by adding cloud monitoring. I want SolarWinds NPM to do much more integration, and have more involvement in cloud monitoring, like AWS or Google, or Azure. I feel like it requires lots of improvement for cloud monitoring in NPM.

I've been working with this product for almost ten years.

The support could be improved. Within the last two, three years, I would say the support has declined. It has degraded, but not that bad. We are still getting solutions, but sometimes, calls stay on hold. When we try to call the support team, it continues to ring on their side. About half of the time it gets connected very quickly, but the other half takes some time to connect. Sometimes I wait more than 10 minutes. It's not totally bad, as we are still getting support. Nowadays, we prefer to send emails to them, so whenever they have someone available, they can revert back to us and we can schedule a call with them.

The pricing is reasonable. In the last year we tried to look for different applications and those other applications are even more expensive. 

If someone wants to install this application, they need to be very specific what environment they want to monitor, whether they want to monitor in a hybrid environment or just cloud, or just on prem, because the setup is going to be quite different in all aspects. When it comes to installation, someone has to have a better understanding of what they're actually going to monitor, how many nodes they are going to monitor, how many network device they are going to monitor, etc. With respect to that, the licensing changes.

I would rate SolarWinds NPM an eight out of ten.

If a customer is looking for a monitoring box solution, a medium-scale customer, and he's looking for something that can manage servers, routers, storage, applications, basic monitoring for applications, to cover everything, then SolarWinds is the right choice. However, he has to be a mid-tier customer. He cannot be an enterprise customer. If they are an enterprise customer, then SolarWinds is not the right choice as it will start to slow down.

It's a very good tool and a very stable tool. 

For a medium-sized customer, it has everything that you're looking for.

It has all kinds of functionality that any network team or monitoring team is looking for. It's easy to integrate with any other tool, as it has an open database. It's easy to implement and has a very nice user experience.

One of the problems that SolarWinds has is when the data becomes too big, it will start getting slower. 

It's not at all for enterprise customers. I don't recommend enterprises to go for SolarWinds. They should go for a bigger tool.

They have had a rather large security breach in the past. It's cost some companies customers. 

I've been dealing with the solution for ten years as a partner at least. It's been a long time. I've used it for about a decade at this point in that capacity. I've been dealing with SolarWinds for almost more than 17 or 18 years, personally.

The solution is stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

We have three to four customers on the solution.

It's best for a mid-tier company, and not a large enterprise. 

Technical support is okay.

The only problem that they have is that last year they had a security hack issue. That is something that was a big problem SolarWinds in the market, as everybody is scared to use SolarWinds. They still have managed customers. Still, I have to say, there are very few customers that they don't have SolarWinds.

Whenever I go for meetings for security or monitoring or anything, I find some engineers still using SolarWinds. They may not be using it a lot, however, they are still using it for more than monitoring. Still, people did lose customers over it. 

The initial setup is very easy and quite straightforward. It's not overly difficult or complex. 

The implementation is fast and doesn't take more than a month or a month and a half. 

We only need one consultant to handle implementation. 

We are able to handle the setup for our clients. 

The licensing process is pretty simple. it's not too complex. 

We've done a couple of implementations at this point. We're actually a partner. 

For a mid-tier customer, I would rate the solution at about an eight.

I'd recommend the solution t a mid-tier customer. I wouldn't if the company was quite sizable. 

One of my clients is a bank. SolarWinds is primarily used in banking to limit network downtime to less than one or two minutes. All the ATMs are connected with SolarWinds, so the bank can respond quickly when the network is down. You only need about three or four people monitoring this software at a time. SolarWinds is deployed on-premises for security reasons. Banks do not allow cloud solutions for this purpose. 

Network performance is the main issue clients are facing. SolarWinds checks if a node is down, and we can set thresholds for performance metrics. For example, we set it up to get an alert automatically if a value is over 80 percent. It has a full dashboard that covers CP, hard disk, and node monitoring.

Each model has different features, so clients need to purchase a separate model for SQL monitoring, database monitoring, network traffic analyzer, HTTP traffic, etc. So each feature they need is in a different model, but customers would prefer an all-in-one solution.

I have been working with SolarWinds NPM for two years.

SolarWinds is stable. We sometimes have crashes here and there because we are monitoring so many features and routers.

SolarWinds is easy to scale.

We don't use technical support because we handle everything in-house. We already make customized dashboards, reports, notes, etc. ourselves.

I used PRTG, but it's not used in any banks. About 80 percent of banks I know use SolarWinds. PRTG is mostly popular in manufacturing companies. It's cheaper, so manufacturers can easily afford it. 

Setting up SolarWinds is somewhat complex because the data is encrypted and banks require so many policies. The reporting and dashboards are also complex. 

SolarWinds is expensive. That's why it's primarily banks using the solution. Small businesses can't afford it. Due to its pricing, most smaller enterprises like manufacturing companies are not interested. For example, we have a client who is also interested in traffic monitoring, but they are not purchasing SolarWinds because of the cost. 

I rate SolarWinds NPM seven out of 10. 

SolarWinds NPM is generally used for network monitoring for all of the switches, networking equipment, as well as physical and virtual servers in the environment.

We use the top 10 dashboards on a frequent basis, as well as the ability to put systems in maintenance mode when we need to perform patching or other maintenance.

Being able to easily, and quickly obtain disk space statistics from servers and volumes.

The interface can be a bit cumbersome at times. There is a steep learning curve if you wanted to get into it in any depth. 

I would say that both the installation and use of it can be complicated initially. It isn't for someone who doesn't have a lot of expertise or knowledge.  It does have a significant learning curve.

After the initial installation, the configuration is where more knowledge is required.

The reporting could be improved. 

I would like to see some enhancement on the reporting side, such as making it easier to create reports or have a larger assortment of canned reports.

I have been working with SolarWinds NPM for eight years. Most recently version 2020.

SolarWinds NPM seems to be stable.

In our environment, scalability wasn't really a factor. The environment we had, and the method we used for the initial install were sufficient.

In our organization, we had about 20 users consistingn of IT server and network engineers as well as business analysts.

This is a tool that we utilize on a regular basis.

Although technical support is adequate, it could be better, but that appears to be the situation in the majority of businesses nowadays.

I would rate them seven out of ten.

The initial setup was somewhere in middle.

This solution is maintained, deployed, and updated by a team of six people, and it is also automated for operating system upgrades. We have one or two server admins that are responsible for actual application upgrades.

I would recommend having a review with a SolarWinds tech first to make sure you understand the system requirements. It would be helpful to work with them also in regards to unique configurations. 

I would rate SolarWinds NPM an eight out of ten.

My team uses SolarWinds to do some of the network monitoring. I look at the reports.

One of the challenges with SolarWinds is that in order to pull the data, we have to have a lot of false positives.

False positives or positive falses are a concern because you want to be as accurate as possible and get them down to zero, which is what you want on your network. Once a week with the reports there, is always a false positive or vice versa where it's showing that it's up and really it's down.

We are looking at how we can overcome that issue. Is it a work issue, or does it come from the tool itself? It will show that something is down when it's up and every once in a while if something is down it shows that it is still up.

We would like to be able to pull information from the vendor's OEM. It would be helpful to have crosswalks or if it could have a running list that goes out of models, software, and it can pull out the end of life, or end of service life dates. Also to suggest the recommend current version to use, that way you can do the comparisons without having to do a manual search. That would be beneficial.

Similar to other tools, I would also like to see a graphical map of your network that highlight in green, red, or yellow, and if you see a specific device you can click on it and it will help you drill down on the details of that device.

There are other things that it should be able to do, such as when it comes to monitoring the infrastructure and my server, and there are issues developing like the circuits degrading or latency is increasing it should give you a notification to know what is going on, rather waiting for the device to go down which at that point it would be too late. You want to be able to do proactive monitoring and reaction.

We want to get to a monitoring level where if it is monitoring the server, the CPU, or the storage level you could have presets where it will identify and give you warnings to say that you are at 70% or 80% storage capacity. This would allow you to get ahead of it before you run out. 

It would be the same for the CPU utilization and knowing if it is running 20 or 30% premiums normally or is it running at 90 or 100% and you have to add CPUs.

It could let you know if you have other tools or applications that are running too hot or if they need to be changing out that tool or is it something else.

To have something in place where it can help us to do some analysis and be proactive would be helpful.

I don't use this solution, I oversee a team who uses it.

We don't have any issues with the stability of SolarWinds NPM. 

We had one problem, but it wasn't a stability issue, it was a hack that occurred earlier this year that affected everyone using SolarWinds. After that, it took a bit to get it stabilized to where it is now. 

Our team that has worked with technical support hasn't had any complaints. It goes pretty well. 

I am familiar with several tools.

They will be putting NetScout on their network to look at some of the differences and to look at the pluses and minuses of each of the two tools.

I would rate SolarWinds an eight out of ten.