SolarWinds NPM Reviews

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 solution for our network. It's for P2P networks or our servers to our network.

It can be a monitoring tool that just monitors for us at the moment, checking what the issue is or where the issue is. It is managed by a third party. Basically, it just gives us a view of what the site is. We can see our server connection and whether it's up or not. It's just checking if the servers are up or not and if the network is up or not. It's not doing too much else.

The solution is very user-friendly. 

When it pinpoints something, I will get an email alert. I'll immediately know what the problem is and be able to do something. 

The pricing is great. 

We were looking for some sort of endpoint monitoring as well. it would be nice if that was covered. We'd like to have more security when it comes to ADR. 

We'd like to see a bit more automation in the future. 

Sometimes, if the problem isn't on our side, it doesn't provide a very clear problem in terms of what the issue is. 

I've been using the solution for about two years. 

It's been very stable and reliable. I'd rate the stability ten out of ten. It doesn't crash or freeze. There aren't bugs. 

We just have one user on the solution who monitors it. Three of us can cover it at any given time. It's web-based. 

A third party helped with the initial setup, and they handled everything. I'm not sure how the deployment worked. 

The initial setup was done by a third party. 

The pricing is decent. We chose to use it based on the price. I can't speak to the exact cost, however, I can say it is very reasonable. 

I'm a customer and end-user.

I'm not sure which version of the solution we're using. 

As a user, I would recommend the solution as it is user-friendly and easily understandable. It will tell you exactly what the issue is and where. It's quite useful. 

I'd rate the solution eight out of ten. 

We are customers of SolarWinds and I'm the corporate IT infrastructure manager.

SolarWinds provides a good enterprise level of tools and covers the essential components. I like the new GUI. 

The solution could be enhanced. It currently lacks integration with SMS services which is something we need. A cloud-based option would also be helpful so we can monitor at any time and from anywhere; for now, we need to VPN to our environment. 

I've been using this solution for six years. 

The solution is generally stable although there are occasional bugs when updating to the latest version. 

The scalability is good, we currently have around 2,000 users. 

The initial setup is simple.

Compared to other products, SolarWinds is not expensive. 

We evaluated Zabbix and Nagios but SolarWinds is better for enterprise organizations. Other solutions are on a smaller scale and only provide basic monitoring; SolarWinds has a better engine.

I rate this solution eight out of 10. 

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.

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. 

I believe the ease of setup and use, including everything, from the initial installation to the discovery of devices is the most valuable. The advanced alerting and notifications capabilities are helpful as well. Devices can be discovered automatically on a schedule, and grouped by vendor automatically, which makes it very easy to track down devices. The customizable dashboards and reporting are flexible and tend to come in handy as well.

SolarWinds NPM allowed the IT department to take a more proactive approach to troubleshooting, and gaining insights on device availability. We were able to use the integration with Storage Manager and Virtualization Manager to gain valuable insight into our storage and virtualization environments. We were able to readily pull reports on device availability, and other metrics, to provide to our senior management staff and external security auditors.

The SolarWinds notification and alerting configuration could be simplified as it would be easier to find if it was within the NPM web application instead of in a separate client application. The SolarWinds Orion/NPM installation comes with a few Windows client application “add-ons” that would be better served if they were built into the SolarWinds NPM web application. Another area for improvement would be better integration between Solarwinds NPM and Solarwinds NCM as it seems that Solarwinds NCM installs a separate version of NPM/Orion console.

I used this product for a little over two years in two different companies. I implemented the product for the first organization I was with to gain visibility and performance monitoring for the network and servers within our data center.

Yes, there can be issues with deployment if you try to install/uninstall or re-install under different account types (i.e. Local Administrator vs. Domain Administrator). I would recommend sticking to one or the other and you won’t run into any problems.

I have never had an issue with stability or performance. I recommend following the SolarWinds documentation (which is very detailed) and you can be assured not to encounter a single issue in regards to stability.

We setup a standalone instance of SolarWinds NPM. However, SolarWinds NPM offers a couple of different HA architectures that will allow you to scale locally (within the same data center) or globally (across multiple data centers in different geographic locations).

The customer service experience was always top notch and I don’t recall ever having a bad experience. The customer support staff were friendly, courteous and always there to help you out. It was also very easy to get in touch with a technical support engineer, all who seemed very knowledgeable, within just a couple of minutes or less.

SolarWinds technical support was one of the best support departments I’ve ever dealt with. All of the technicians were very knowledgeable and technically capable. Also, when you call into their technical support number, you don’t have to jump through multiple departments to get to a technician, which is very nice and not the same with other vendors.

No, SolarWinds NPM was the first network/server monitoring product that was brought into the organization. Other network monitoring products were researched, but didn't have the feature set, didn't seem as easy to use or as robust as Solarwinds NPM.

It was very straightforward, as you basically just have to start up a Windows Server, and click through the SolarWinds NPM installation wizard before you are ready to configure. You can configure most of the basic settings using the installation wizard (i.e. the database storage location).

We implemented it using an in-house team. It should not be necessary to use a third-party team unless you are performing a massive roll (5000+ endpoints) out across multiple sites.

I believe the original setup cost was around $3500 with an annual cost of around $1200-$1500 to renew the support license. This would bring the average day-to-day cost of around $5-$6 over three years.

We also evaluated ManageEngine OpManager and AdRem NetCrunch before deciding to purchase SolarWinds NPM in conjunction with the SolarWinds NetFlow Traffic Analyzer (NTA) module.

If you’re looking to get a lot more insight and visibility into your network devices, servers, applications, and other devices, along with real-time alert notifications, SolarWinds NPM should be towards the top of your list. You will be able to view devices by type or by location and poll all sorts of different data using SNMP or WMI or other methods. Out of the box, you will also receive customizable dashboards, alerting, reporting, and Active Directory integration.

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.

The SolarWinds product is easy to deploy and the product features are quite granular. We can dig deep into the infrastructure and at the data level, or we can aggregate and come higher up and look at all the trends and analysis of what it provides.

The integration with the APIs and the web servers deployed can definitely be improved.

I've been using the solution for three years. 

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

It is a highly scalable product. Users can use something like F5 or load balancing. That gives you failover and similar infrastructure for disaster recovery as well. It's very, very scalable and stable product.

Usually, NPM users will be fewer as they're all network engineers. The solution doesn't require hundreds of users. We have about eight to nine. However, we deploy SolarWinds with a lot of clients. If you look at our clientele and our own user base in NPM, we must have had more than 100 users on this product between clients.

Technical support is excellent. 

SolarWinds wants its partners and resellers to succeed. They give you all the support, all the training for free. It's really, really, really good.

One of the competing products for this solution is Cisco SecureX. We have used it in the past.

The setup and deployment are quite simple. 

It's straightforward, however, you need to have networking knowledge. If you have knowledge of the network, then it's straightforward. It's a great product.

On a medium-sized enterprise, for one of our clients, we deployed it in three hours.

We've got our own engineers to handle the setup. However, whether we set IP up or not all depends on the client. If they define everything properly, the delays are not with the product. The product actually answers a lot of the client's questions and helps the client determine what they should be doing.

You've got the annual license, and then you've got a perpetual license as well. The pricing is very affordable.

There is no extra cost beyond the licensing. 

It is the latest version. The latest version comes with observability as part of the package. It's SolarWinds attempt to bring all its products under one platform. We've kind of become quite an expert in the area.

We are a provider of SolarWinds. We are an MSSP and also a reseller. It depends on what the client wants. 

We want to launch it as an MSSP for SMEs, and small companies who can't really afford a full install. We just doing a SaaS model so they can deploy it at cost to SMEs.

I'd advise potential users to use the one-month free trial and get a company like us to do a proof of concept and then do the NPM, application monitoring, log monitoring, et cetera. One by one, pick up all the products and integrate them.

I'd rate the solution nine out of ten.