SolarWinds NPM Reviews

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. 

SolarWinds NPM was used for everything. For interface monitoring, load balancing checking interface uptime and device status. 

We had the full suite of products, not just NPM.

It is simple to use.

It can be agentless.

The nice thing about SolarWinds is that it's kind of all-in-one. I can manage the status of my networking devices, whether they are up or down, I can see how much traffic is going across an interface, and I can run a report that tells me exactly what that traffic is.

Their IPAM component is severely lacking. The process is extremely manual. It just doesn't get in there if you don't manually enter it. 

It is not particularly DNS-aware. When it comes to DNS names, you pretty much have to configure everything manually. It will not grab anything on its own. 

They need to work on their automation and automatically discover devices. They are not very good at automatically discovering devices.

I am been using SolarWinds NPM for 15 years.

I believe that we are working with version nine.

SolarWinds NPM is a stable solution, aside from the fact that they had a major hack a couple of years ago and effectively allowed the Russian government to completely hack their code, making everyone vulnerable.

SolarWinds NPM is not very scalable.

We had 10 users.

There was only an IT engineer that was responsible for upgrading.

There was only one administrator. The rest were read-only.

Technical support is very good. You always got a live person.

The initial setup is straightforward. It is easy to set up.

The initial configuration is simple. Because, they did not use a backend SQL database, their initial setup was extremely simple. 

As they grew, they began to use SQL, which made things a little more complicated. 

It was extremely simple at first.

It probably took me a week to get it all set up and running, and another month to get everything in it. 

The initial configuration to the point where it was up and running took me about a week.

We installed it in a central data center and then began implementing it. We had to manually discover devices, pull them in, and manually add them one at a time.

It was implemented in-house.

We have seen a return on investment.

It was inexpensive when we installed it and gradually became more expensive, but it was a very inexpensive product at first.

It is significantly less expensive than Infoblox.

I don't recall the exact amount, It was approximately 20 years ago, but I recall it being relatively inexpensive to install. The initial part was really cheap, but the licensing cost became really expensive over time.

I would advise people to only use it for monitoring or viewing traffic flows. Don't use the IPAM section, the DHCP section, or the DNS section.

I would rate SolarWinds NPM a seven out of ten.

We've been using SolarWinds for our network monitoring. It's basic advanced network monitoring, up-down of Rogers switches, as well as metrics, latency, wireless metrics, where users are, errors on interfaces, route cables, and things of that nature. We're just pulling as much data from our network devices as possible to present that in an easy pane of glass.

I find the NetPath to be very valuable. It visualizes that traceroute that you can share with anyone in the business. For example, when they say, "Hey, what's going on? The network's slow because my application or my server's having issues" you can show them this nice graph that visualizes where there may be congestion or if there isn't any congestion at all.

Its initial setup is simple. 

So far, it's been pretty good, however, due to the whole solar flare thing that happened two years ago, a lot of cybersecurity and leadership's kind of looking to replace it with something else. We're currently just trying to find other info or anybody else who's comparable in terms of other network monitoring solutions.

Wireless monitoring needs improvement. We need to get a little bit more information from the thin clients or wireless LAN controllers than we already do. It's very minimal at this point and getting more information would be pretty vital.

There should be a little bit more integration in some of the other tooling and utilizing the APIs of devices or tools could be a little bit better. It would help to present information - rather than trying to get the highest level of administrative access to present minimal information. There are a lot of aspects where they give you base information, however, for other necessary gleams of information, you may need to have high-low. For instance, for Linux servers, you need to have pseudo access to get the necessary information to monitor and that's kind of a hassle.

We've been using the solution for about three years. 

The stability is fantastic. We haven't personally had any issues other than a few gripes about the lack of information. However, as far as it being stable, for me, it's been pretty solid.

It's possible to scale, however, it comes at a cost. You have to go through them and there's a whole nother license piece that costs a large lump sum to grow your polers to start importing more if your initial server is getting towards a limit. It's scalable, with the caveat of it's going to cost you.

We have about ten to 20 users. It's a mix of network analysts, CIS admins, storage administrators, and application administrators.

We do not plan to increase usage at the moment, mainly as we're pretty much utilizing it as much as we need to, however, it is pretty much monitoring our entire environment or maybe couple hundred switches, some routers, couple hundred servers, and applications and things like that. We pretty much monitor our whole environment and our environment's not really growing anymore. We're pretty good right now.

Technical support is pretty good. In the few cases we have reached out for any support, they've been pretty responsive. Also, their online resources and knowledge bases are very extensive as well.

Positive

We actually didn't use anything before this product.

The implementation process is pretty straightforward. They give you an MSI and once you have your servers and databases set up, it's just a couple of clicks and it's set up.

For overall importing of everything may have taken a couple of weeks to have things up and running due to how our organization is structured and how we can gather information to pull into SolarWinds and our implementation strategy. For example,  who set up servers and applications. We start getting with the appropriate aims to get whatever monitor or whatever polling method we need, whether it was S and NP strings or accounts for any server monitoring with administrative access or whatnot. Then we look at the network and do those automatic scans from there. Once we start pulling in that information, we start actually organizing all the nodes in there to properly alert and monitor. It takes maybe a month or so to get it to a baseline.

For deployment and maintenance, honestly, it's just me by myself doing it. It would be easier with a few more people.

The setup was done in-house. We did not use any third party, like an integrator, reseller, or consultant.

As far as assisting in being proactive in our network, it's been a great help in helping us maintain a healthy environment and being proactive and making sure things are up to date and upgraded.

The standard licensing fees are what we're paying. It's about $20,000 a year for all our licensing.

There weren't any other options were evaluated. We saw SolarWinds and noted our other sister companies use that. We just went with it to be standardized within our entire conglomerate.

We are a customer and end-user.

I would definitely advise others to do their homework. There are a lot of different modules you can buy with different licensing. You need to understand what you're looking to monitor, and what you're trying to present to your business, and then do the homework on the solution itself and see how that fits your needs before just going and buying it or even talking to a sales representative.

I'd rate the solution eight out of ten. It's pretty good at its job. I haven't really delved into too many other things. I've tried to look at other tools recently and in my opinion, solutions like Nagios or Zabbix aren't the best. I haven't really looked into other things like Datadog or LogicMonitor yet, however, I'd say this solution is kind of a leader in the pack for what it's doing. Still, there's definitely room for improvement.

SolarWinds NPM is a good tool. It's a strong monitoring tool that we use to monitor our network devices, routers, and switches.

I like that SolarWinds NPM is a strong tool for monitoring network devices, switches, and routers. It's also a user-friendly tool. My team also likes how scalable it is.

There are some areas for improvement in SolarWinds NPM. One is that their dashboard needs to be friendlier. We want them to take their dashboard to another level. For example: with our databases, we develop services and we want to put those on the dashboard, while making them more visual. This would be good to improve in the tool.

The integration of SolarWinds NPM with other tools is also another area for improvement. For example, we'd like to have the ability to manage the unit with other tools, because we need to have better control to manage the alerts. How can you load that capacity with only that kind of information?

We also had to be attentive to vulnerabilities, because SolarWinds NPM have some issues in that area. We had to work with our security team, so that they could help us check and backup the data, and check what they needed to secure. You have to do a test, find what needs to be improved, then make the corrections on SolarWinds NPM. You have to be very attentive when using the tool, but it's an area to improve not just in SolarWinds NPM, but for any tool.

I've been using SolarWinds NPM for a year and a half.

SolarWinds NPM is a stable tool.

SolarWinds NPM is a scalable tool. My team likes working with it because they really like its scalability.

The technical support for SolarWinds NPM is very good. I'm rating their support five out of five.

The initial setup for SolarWinds NPM was easy. I didn't do the configuration, but I watched our installer very closely, and he installed the tool quickly. For example: if you have a new module or a new product, you can do the installation very quickly.

The deployment of SolarWinds NPM was done in-house.

We pay for SolarWinds NPM yearly. We buy it and then we renew it, but it's not subscription-based. I don't remember the value exactly, because it's my manager who manages pricing, but we pay $60,000 per year for all the solutions. Pricing will also depend on the number of devices. We have a lot of devices.

We have the SolarWinds NTA (NetFlow Traffic Analyzer), and we also use another solution from SolarWinds: the SolarWinds SAM to monitor some on-premise servers. It also monitors the GPU, memory, the availability status and processes. We are now monitoring databases, particularly Oracle databases, to check their status and also check internal information. We detect all this information and equip our system so that it has the information, and we're doing it manually because that doesn't happen automatically with SolarWinds.

We have 30 people who use SolarWinds NPM and they're part of the operations, network, and infrastructure teams that do the diagnostics when something is wrong. We also have team leaders and some managers that watch the data in real time, plus the configuration and monitoring teams. We have 2 engineers responsible for the deployment and maintenance of the tool.

As for plans of increasing our usage of SolarWinds NPM, we've bought more modules recently, and we keep using the tool to monitor our network and infrastructure, together with other tools. For example: we have some very practical tools that our monitoring team uses to make diagnostic alerts such as McAfee. At the moment, our main tool is SolarWinds NPM, and we keep using it, especially for monitoring cloud devices. This is very important to our organization because we've migrated to the cloud. If you're doing cloud migration, you have to picture how you can monitor devices on the cloud.

I would recommend SolarWinds APM to others looking into using it. We're using a lot of it. We also have the SolarWinds SAM, and I would recommend it for monitoring databases and servers, and you have to do a little development, but it's manageable. I would also recommend SolarWinds NPM because from experience, it's able to do its job.

My rating for SolarWinds NPM is nine out of ten.

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. 

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. 

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're using SolarWinds NPM for server monitoring, report monitoring, and application monitoring.

I found a lot of valuable features in SolarWinds NPM, such as the customized application monitoring that allows you to customize any monitoring and script customization, and you also have the option to deploy and upgrade SolarWinds NPM online, which is very useful for my organization.

An area for improvement in SolarWinds NPM is the short retention period. Currently, it's just for seven days of data, which is very low, making it hard for my organization to keep that data.

SolarWinds recommended a seven-day retention period, but my organization needs a fourteen-day data retention period. Hence, I'd like an increase in the retention period or the database limit in SolarWinds NPM because you can't go back to the data for any investigation if seven days have passed.

Another area for improvement in SolarWinds NPM is the database, which needs to be a bit more mature.

I want a modified database in the next release of SolarWinds NPM. I'd also like more options added to groups because, currently, it's very limited.

I've been working with SolarWinds NPM for almost two years now.

SolarWinds NPM is a stable solution.

SolarWinds NPM is a scalable solution.

My team contacted technical support for SolarWinds NPM a lot of times. On a scale of one to ten, I'd rate support as seven because one of my cases remained open for a year without the perfect answer or resolution, though the SolarWinds development team has been working on it.

Neutral

I've previously worked with HPE and IBM, but that was for another organization. My current organization uses SolarWinds NPM.

The initial setup for SolarWinds NPM is relatively easy, and anyone can do it.

As I deployed SolarWinds NPM in a huge environment, the deployment took almost six to eight hours for fifteen servers.

We deployed SolarWinds NPM in-house.

Though I don't remember the price for SolarWinds NPM, its price is somewhat okay when you compare it with other tools in the market. The price isn't too high and isn't too low, so it's okay.

I'm an end-user of SolarWinds NPM.

In the organization, over a hundred people use SolarWinds NPM, with five to six administrators. The solution requires specific maintenance, mainly because it has a lot of DW issues.

My advice to people looking to start working with SolarWinds NPM is that it's the best solution for a medium-scale environment. For a large-scale environment with many requirements, such as a vast number of nodes, for example, more than twenty-five thousand, SolarWinds NPM may not be as scalable, DW-wise. If you have below fifteen thousand to fifteen thousand nodes, then it's okay to use SolarWinds NPM.

My rating for SolarWinds NPM is eight out of ten.