SolarWinds NPM Reviews

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.

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.  

There are modules in SolarWinds NPM which are better than other competitive tools. However, some areas require new releases or updates. For example, there have not been many updates to cloud monitoring, containerization or serverless environments. In that regard, SolarWinds NPM is not as good as other solutions in the market.

It is a stable solution, and rate the stability a nine out of ten.

The scalability can be better.

The technical support has been a good experience.

The ROI has been good.

It is considerably cheaper compared to other tools and available technologies in terms of LMS or EMS.

I rate this solution a seven out of ten. Regarding advice, I would recommend concentrating on gaining some expertise. A foundational or intermediate understanding of different network protocols and technologies would be helpful when using SolarWinds. In addition, understanding the underlying technology that will eventually be monitored or managed will be good.

We use this solution for checking databases and new devices that are added to the network. We test the L state of routers and firewalls.

The benefit of this solution is the reporting. We're able to report on and see our network in a graphical form. We are able to detect when a device is added to a network.

Being able to detect devices that are trying to connect wirelessly would make using this solution much easier.

I have been using this solution for two years.

This is a stable solution. 

We have not experienced any challenges with scalability. 

The support for this solution is satisfactory.

Neutral

The initial setup is not that straightforward and could be made easier. We have approximately 500 devices using this solution. We require only two team members for maintenance. 

I would recommend this solution to other users. I would rate it an eight out of ten.

Our clients are using Solar Winds NPM to monitor their network product. Solar Winds NPM is straightforward and you can monitor it very easily.

I think Solar Winds NPM needs to create a profile with documentation responsibility.

I have been using Solar Winds NPM for about three years.

The product is very stable and we have been using the product for around ten years.

Technical support is very helpful with our upgrades. I would rate them about an eight or a nine.

Positive

The setup is straightforward and takes about a week.

I would rate this Solar Winds NPM an eight out of ten.

We use SolarWinds NPM for monitoring. We don't change anything, and we just look at it.

I like the tracking feature to track devices and see where they are connected. This is very practical.

The console could be more user-friendly. It would be better if SolarWinds updated the user interface.

I have worked with SolarWinds NPM for two or three years. 

SolarWinds NPM is a stable solution.

SolarWinds NPM is a scalable solution, but it costs a lot. As long as you pay, you can scale it as much as you like.

Technical support is quite efficient, but they have to be a little more responsive.

On a scale from one to five, I'll give them at least four.

Positive

The initial setup was quite complex and took a while. You need an engineer to install the solution and the database and configure everything. We have only two people accessing and maintaining SolarWinds.

We had a contractor implement this solution.

I did a proof of concept with ManageEngine. The functionalities are similar, but the ManageEngine interface is way more user-friendly.

On a scale from one to ten, I would give SolarWinds NPM a seven.

We use SolarWinds for monitoring internet bandwidth, both outbound and inbound. We also use it to check out network tools like switches, routers, and other things including user monitoring for RAM and CPU. We typically get a report on the internet interface about, for example, HTTP traffic and other software traffic. 

The solution is easy to use. It's easy to understand, even if you are not too technical.

It's quite stable and reliable. 

The reports are excellent. They give good graphical information. It gives a lot of great details about everything that's going on in my network and it's easy to read and understand due to its visual nature.

The scaling is quite good.

It's a very easy solution to set up.

If SolarWinds integrated with other solutions, for example, something like in a SIEM, security operations system, it would be more useful for customers. It would be ideal if they could integrate more with security solutions down the line. 

There isn't support available to us as they don't offer support in our country.

I've been using the solution for more than five years at this point.

The stability and reliability of the solution are very good. It's got more stability than other software options. There are no bugs or glitches. It doesn't crash or freeze. The performance is good.

The solution can scale well. It's not a problem if a company wants to expand it.

Currently, we have more than 50 users on the solution. 

Unfortunately, in our country, we do not have access to official support channels. We need to find answers online. It would be ideal if they could establish agents in the country that can help with setup and questions. It would be good for customers like us and good for SolarWinds. 

We did not use a different solution previous to SolarWinds. 

The implementation process is quite simple and straightforward. In fact, it's easier than a lot of other solutions. I wouldn't describe the process as difficult. 

The deployment is fast. It likely didn't take more than ten minutes or so. 

We have a technical team of about five or six people that are able to handle deployment and maintenance tasks. Two of those team embers are managers. 

We didn't need any assistance with the implementation process. We did not use any integrators or consultants. We did it ourselves. 

You do need to pay for a license in order to use it. We have a license paid for two years. 

I would rate the solution at an eight out of ten. We're pretty happy with it overall. The downside is that there is no official support available in my country. 

Our primary use case for SolarWinds NPM is for network monitoring and SNMP traps.

SolarWinds NPM features that I have found most valuable are the reporting tools and the ability to create customized reports.

With regards to suggested areas of improvement for the product, I would like to see the price come down, and in addition I think the network element mapping tool is not as robust as it should be. 

I have been using SolarWinds NPM for 5-6 years.

SolarWinds NPM to date has been stable for me. 

The SolarWinds NPM product is easy to scale.

I have utilized SolarWinds technical support to help with issues, the experience is adequate for the the level of support we pay for. 

The initial setup of SolarWinds NPM is complex in my view. There are many knobs, dials and buttons to push, and it can take several days to get familiar with the product and it's functionality. 

Approximately 50 users utilize SolarWinds NPM within my company. 

The most valuable features are language support and technical support.

An area for improvement would be the use of modular licenses, which are not practical for big clients.

I have been using this solution for seven years.

The initial setup varies but can be quite complex.

This product is priced quite highly. Its licenses are available yearly, and the calculation of costs is quite complex.

I would rate this solution as nine out of ten.

We use SolarWinds NPM to monitor and manage network devices and infrastructure in our environment.

SolarWinds NPM has helped our organization by providing a proactive approach to understanding the current trends in the environment, utilization of the resources, and providing inventory reports of the environment. This has helped us stay ahead of the cost for new infrastructure requirements as well as licenses.

The solution could improve in many areas, such as the marketing and description of the products, providing areas of improvement, cloud capabilities, and being able to be more streamlined with the current integration points with other applications.

I have been using SolarWinds NPM for approximately two years.

I have found the stability of SolarWinds NPM to be good.

The scalability has been adequate.

We have multiple users using the solution with various roles, such as network administration, server administration, and reporting users.

We have plans to increase usage. We are currently leveraging the internal infrastructure aspects of the environment. We're going to expand it and we purchased additional infrastructure to expand the visibility across multiple areas.

The technical support offered by SolarWinds NPM is pretty good.

The initial setup was straightforward. We deployed the solution from new and completed the upgrades. 

We coordinate with the vendor to help support the implementation. It can take many days depending on the modules that need to be installed. It took us approximately two days.

We need at least one staff member in each focus area for the implementation of the solution, totaling approximately six, depending on the modules you have.

We have a multi-year license for the use of this solution. There are additional costs for recourses in the environment.

Before choosing SolarWinds NPM we evaluated other solutions such as Splunk and ScienceLogic. The flexibility and the overall breadth of different modules that SolarWinds has to offer were superior to the other solutions evaluated.

I rate SolarWinds NPM an eight out of ten.

It is a good solution, it provides multiple module options, easy to use, and predominantly easy to find people to support it in the industry.