SolarWinds NPM Reviews

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. 

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.

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.

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. 

We use this solution for one of our very big customers. We are consultants and I'm the technical specialist and consultant. The company is a customer of SolarWinds. 

SolarWinds core data is organized in a very good way. The solution can easily be interconnected with other management systems to get information not only from networking devices but also applications and servers.

I think the graphical environment, the GUI still has to be improved. Other tools like Power BI provide a more graphical dashboard for executives to show what's going on with operations. SolarWinds has the data but the representation needs to be enhanced for an executive view. It requires a large amount of customization to get to a point where you are able to have something concrete for the upper management team.

For additional features, I'd like to see something more in automations, the graphical interface, and some dynamic dashboards or at least the ability for integration with some dashboard tools. 

I think it's a pretty stable solution although we have identified some security gaps around it. I think it's more about managing it correctly and having the security hot fixes and patches up to date. It's generally stable and we haven't had many issues. 

Technical support is pretty good, they are very keen to help. There are some options which provide premier support and that enables access to direct SolarWinds support and upgrades. 

I think the initial setup is pretty simple, the challenge is more about trying to generate all the dependencies, setting the rules and actually setting up internals, ENBB. Our deployment was staggered and took five to six months. We started with a pilot in a region with the most number of users and complexity in order to test and configure the rules we needed. We then went global, starting with the big operations and then moving to the smaller ones which would be easier and take less time. Implementation required a couple of consultants who were familiar with the application and a team that managed the whole operation. The deployment probably involved around 10 people.

Any WAN or LAN environment will benefit from this sort of solution because it consolidates not only the monitoring but also the operation. You can actually trigger some actions based on the conditional threshold that you set in the tool.

I rate this solution a nine out of 10. 

Our installation is on-premises on a virtual machine. When we purchased NPM I was particularly interested in the features of Orion. We were going through a maturation process propagating the monitoring of applications throughout the server policy here at the university. It was more to monitor various applications that are primarily used for individual schools. For example, we have the school public health, and we have the school of nursing and they have different needs. You have all these applications like Banner and Canvas and other web-based applications that get used by particular areas. We are working with one application now for COVID-19. There is an application that has been spawned from that, but mostly our monitoring is for up/downtime, space, memory, availability, and those types of things critical for performance analysis. We are just now getting more into monitoring databases and a broader scope of applications as well.  

What I am mostly referring to is not the whole Network Performance Monitor suite. This is the actual operations monitoring piece of it. We have the network and we are responsible for set up and monitoring of those particular tools.  

We identified the five areas that we wanted to have be our key performers, like memory utilization, CPU utilization, and those core components. Just the basic care and feeding of servers, whether they were physical or virtual.  

We were looking at using DPA (Database Performance Analyzer) which is another component of the NPM and that looks like it takes care of an area we had not really dove into yet. But in talking to the DBA, they like another product that they want to use for the database monitoring. It is an Oracle product called OEM (Oracle Enterprise Manager).  

In talking to the DBA's, there was a lot of functionality that they were just used to and they had issues because they did not see some things that they thought were important but missing in the DPA product. That is the only thing I have run into so far with the product that seems to be a shortfall. Everything else is pretty good.  

I do not really have other suggestions for additional features beyond working on the development of DPA to make it a more complete tool. We are still learning the product.  

There may be some things that they could improve in the reporting aspect of the product. You can create custom reports and those types of things. But the product seems to be missing some depth in that area and it leaves a little bit to be desired. For example, the filtering system and formatting reports and things like that seem to have room for improvement. You are a little limited on the information available on that front and the utility could be improved.  

They do have some templates that you can use for report setup. It would be nice if you could maybe make your own. That might make it a little bit more easy to generate other reports that follow the way you like to do things.  

We purchased SolarWinds NPM (Network Performance Monitor) about three years ago.  

SolarWinds is a pretty good, stable product, but we have had some issues with support. That is especially true of the last release we upgraded to. There were some SQL issues that we were looking for them to help us out with and, finally, it took so long that someone on our internal SQL team had figured out what the problem was. So, I would say that the upgrades to the product itself from what we went through can be somewhat of a pain point and maybe there needs to be more rigorous testing.  

Typically, I don't think scalability is an issue. If you are talking about individual users, we have anywhere from 20 to 25 people across the typology. Probably one of the biggest users is a resource/research support group where they have various servers on the Orion Monitoring System. They actually take on their own responsibility and monitoring role for their servers. So, there are some groups that adopted monitoring through Orion, and then there are some other groups that have quite a bit more of a blasé approach to it and do not really think it is important.  

We have not had a lot of opportunities to use technical support. When we did I was not particularly impressed with their response time or expertise.  

The initial setup with Orion was somewhat complex. They do have templates in there that you can utilize, but most of those you are going to have to customize anyways. We found that it was easier just to go ahead and do our own.  

The way that I found it to be complex was that we had to do a lot of our own scripting to collect the data that we needed. Once you have got a template set up, you can pretty much populate that information to the Orion database, but I mean there is some pain to get started off. Overall we got involved in a year-long project where we were meeting on a weekly basis discussing all the issues. I think it took us a little over a year-and-a-half to actually declare success on the project.  

Only after that declaration of success were we able to get on to monitoring and dissemination of information to various users and get started with the monitoring. But our monitoring is a lot better than what it used to be. We were using Homegrown, Nagios, and Check_MK. People were not paying attention to alerts. I think the way we handle it now has really helped users mature in that way. We have still got a lot more work to do though.  

We started out with an implementation strategy, but there were some challenges when our directions got changed on us by senior leadership. We would have a plan and a direction and head down a path to implement those particular types of solutions. We would set up the alerting and monitoring and then three months later somebody would come up from an executive level and say, "Hey, we need to monitor this as well." So, we would have to make some changes just like any project. We had to learn to be flexible with it to meet people's needs, but having clearer goals from the outset would have made it easier and quicker in the long run.  

We did just about all the work on the implementation on our own with an internal team. Right now, I have got one person that is in charge of the actual product itself. They take care of all the changes, releases, upgrades, deployments, the agents, and those types of things. I have another individual who is responsible for creating tickets and disseminating the information to the owners of the server monitoring in various groups to get their alerts fixed. It does require attention but it does not take a large group for maintenance requirements.  

I do not handle the negotiations on pricing, so that is outside my realm of influence. I know that our initial purchase was about $200,000.  

One of the things I would suggest to people considering this product and products like it is having a clear agreement upon targets of what you really want to monitor. If it is applications or servers or whatever it is, it just makes sense to come at your choices with a plan. Implement that on the front end by picking out what is important instead of coming back on the back end and trying to do things after-the-fact.  

On a scale from one to ten where one is the worst and ten is the best, I would rate this solution as about an eight-out-of-ten.  

We have a data center that is used by multiple clients and we need to see how applications are performing when clients are on our network. The NPM tool is used to analyze what different applications are consuming, in terms of bandwidth.

The most valuable feature is the graphical user interface.

SolarWinds needs to be improved such that it is on par with the leading products in the market. There are better products available, albeit more expensive.

We have been using SolarWinds NPM for three months.

This is a mature product and the stability is quite good.

We have eight users including an operations analyst, system analyst, and support engineers.

We have been in contact with technical support and they are good.

SolarWinds was the first product of this type that we used.

The initial setup is straightforward. The implementation took about two weeks in a controlled environment. We had no problems with the installation and connecting to our devices.

We did not require assistance for the deployment.

One person is suitable for deployment and maintenance.

It is not an expensive product.

We will probably continue looking for a better product.

This is a product that I recommend, although it requires technical skills in order to use it.

I would rate this solution a six out of ten.