SolarWinds NPM Reviews

We are using SolarWinds NPM to monitor our network. For example, we monitor Cisco Meraki for WAN, and other Cisco routers, and for LAN we monitor Cisco switches and firewalls.

There are a lot of valuable features with SolarWinds NPM. We can receive a lot of detailed data from the monitoring that can use useful for investigations, especially when you are troubleshooting. It is very helpful. Overall it was a very good experience.

SolarWinds NPM could improve the graphics of the interface and more customized reporting.

I have been using SolarWinds NPM for approximately one year.

SolarWinds NPM is stable. We haven't faced any major outages.

The scalability of SolarWinds NPM is good, and it is simple. We have approximately 5,000 nodes.

The support we have received from SolarWinds NPM has been very good. Initially, there were some issues with the solution but the support help us figure it out.

I rate the support of SolarWinds NPM a four out of five.

The knowledge base of the support could improve. However, every organization has its own use cases. Sometimes it's not a common use case and the support has not seen the particular problem. We might have something unique, which other clients never faced.

We have used Centreon previously. We have evaluated it for some time. It was very easy to use but the requirements we had, were not fulfilled. We have engaged with some Centreon providers, and the support was not great. We bought a license for one year for Centreon, and the support from France was not great. That's why we decided that we cannot go with it for a longer time and on a larger scale. Additionally, we have used Alaloop for quite some time, and it was good.

We switched to SolarWinds NPM mainly because we were expanding, and in Alaloop we were mainly using it for WAN only, not for the LAN. Additionally, Alaloop was much more expensive compared to SolarWinds NPM.

The initial setup of SolarWinds NPM was not straightforward. We had some difficulty configuring some of the new features for the devices properly. However, this was because we were new to the solution. We had the documentation which was helpful.

The full implementation took approximately one month.

I rate the initial setup of SolarWinds NPM a three out of five.

We used third-party support for the implementation. The solution requires maintenance but we have not had any issues.

SolarWinds NPM has different pricing models available. The cost of the solution is less than some competitors.

I would recommend SolarWinds NPM to others but it depends on how complex the network they have is and how large it is. Based on that information, you need to make a decision if the solution is the best fit. If their infrastructure is quite large, the good thing is they can expand it, even for the server infrastructure, not only for network infrastructure. 

I would recommend the solution for a larger organization.

I rate SolarWinds NPM an eight out of ten.

SolarWinds NPM is used to monitor our devices' to see uptime, availability, and performance.

SolarWinds NPM has helped our organization by proactively indicating if we are low on resources for a particular server.

The most valuable feature of SolarWinds NPM is the performance monitoring to see the memory, and CPU utilization.

SolarWinds NPM can be very slow at times. The database optimization can be done to improve the product performance.

I have been using SolarWinds NPM for approximately 10 years.

SolarWinds NPM is very unstable. We often have website loading issues. We have to call support, and they fix it. Then a month later, we're going to have the same problem.

SolarWinds NPM can be used at multiple locations, and increase the capacity as needed with additional licensing. It's very scalable. 

We have three people using this solution. It's used globally at all our sites and we plan to increase our usage in the future.

SolarWinds NPM technical support is very responsive. They're available by phone, which is a plus.

I did not use a solution previously.

SolarWinds NPM's initial setup was straightforward. It took about a year to complete the full process of the implementation. The strategy we used was we worked on the setup of vCore and Microsoft Azure, and then for each of our sites, we did afterward.

We did the deployment in-house.

I have not seen a substantial return on investment with SolarWinds NPM.

We pay approximately $4,000 annually for SolarWinds NPM. There are no additional fees required other than the standard fees.

I rate the price of SolarWinds NPM a three out of five.

I have evaluated other solutions, such as PRTG Network Monitor and WhatsUp Gold. We choose SolarWinds NPM because it had better licensing and architectural options.

My advice to others is to follow the best practices.

I rate SolarWinds NPM a seven out of ten.

The solution has good support they're constantly improving it.

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.

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.

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.

We were using it to monitor network devices and the monitoring of certain servers.

It did a good job of the collection and then an investigation of the net flow of information for understanding the applications that were being used at certain locations.

They were pretty good at keeping up with things.

We have replaced SolarWinds with LogicMonitor. 

I had been working with SolarWinds NPM for five years. We stopped using SolarWinds in December of last year when it was revealed that they had been hacked with the supply chain hack and we turned it off. We began a fast-track process of trying to find something else that we could use to replace SolarWinds. We decided that we were no longer going to trust that their products have not been compromised.

At the time, we were using the latest version.

We experienced the typical ones that happen when a parameter is not well understood and that it is implemented, you end up causing issues.

The scalability was complex. 

We had 99 facilities that were a hospital holding company, and we have some 90 other facilities that we are the corporate headquarters of. In monitoring each of those different hospitals, there would be challenges with getting to all of those devices because of firewall rules.

The faculty would use it on a regular basis. There were approximately 90 users.

We contacted technical support all of the time. They were fine.

At the time I had been with the company for just over six years. They had only been using SolarWinds.

I have also been using VMware for a long time, and we are implementing vROps for alerting and monitoring.

The initial setup was pretty straightforward.

It seemed that they nickeled and dimed you for everything that you were doing. There are a lot of sub-products and it just continued to increase the price.

I would not recommend implementing SolarWinds because of the hacks, it is just not trusted.

Before they had the hack, the intrusion process I would have rated them a six or a seven but after the compromise, I would rate SolarWinds NPM a zero or one out of ten.

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. 

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.