We primarily use the solution for network health.
Vice President Of Global Operations at a computer software company with 51-200 employees
Easy to deploy and good alarm tuning but cost prohibitive for smaller companies
Pros and Cons
- "The initial setup is easy."
- "Technical support can be slow to respond."
What is our primary use case?
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I've used the solution for several years.
Buyer's Guide
SolarWinds NPM
October 2024
Learn what your peers think about SolarWinds NPM. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
815,854 professionals have used our research since 2012.
What do I think about the stability of the solution?
The stability is good. Aside from the very public hack, from a user's standpoint, it's good.
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
How was the initial setup?
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.
What's my experience with pricing, setup cost, and licensing?
The solution is expensive and may not be very affordable for startups or smaller companies.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior Vice President and CIO at a financial services firm with 201-500 employees
Lets us track down brownouts in a multi-host, multi-guest virtual environment
Pros and Cons
- "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."
- "The solution's network discovery and node addition processes need more work."
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
We have been using some version of SolarWinds for 20 years.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
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.
How are customer service and technical support?
As I have been using the solution for so long, I have not had any need for technical support.
Which solution did I use previously and why did I switch?
I have used other products prior to SolarWinds NPM. I switched because the solution provides a consolidated view of everything.
How was the initial setup?
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.
What about the implementation team?
I did the integration myself.
What's my experience with pricing, setup cost, and licensing?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
SolarWinds NPM
October 2024
Learn what your peers think about SolarWinds NPM. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
815,854 professionals have used our research since 2012.
Data Center Engineer at a retailer with 5,001-10,000 employees
A robust solution with good connectivity and a straightforward setup
Pros and Cons
- "The connectivity of the solution is very good."
- "My team has had a lot of issues with support."
What is our primary use case?
We primarily use the solution for detecting weaknesses and portal connectivity with our client's machines. We also use it to analyze the stacks of data to figure out where downtimes are and for how long.
How has it helped my organization?
It helps us figure out how to fix problems faster than we were able to before.
What is most valuable?
The connectivity of the solution is very good.
The solution is quite robust.
What needs improvement?
My team has had a lot of issues with support.
The solution should offering monitoring for the database and for the TC (traffic controller).
For how long have I used the solution?
I've been using the solution for three years.
What do I think about the stability of the solution?
The stability of the solution is very good. We haven't faced any bugs or glitches.
What do I think about the scalability of the solution?
The scalability of the solution is okay.
Currently, we have ten people in our organization using the solution. They are mostly admins.
How are customer service and technical support?
Technical support hasn't been the most reliable. Sometimes it takes them a long time to respond or resolve the issues. Occasionally they aren't able to resolve issues at all. The solution is great, but they're really missing the support piece.
Out of ten, I'd rate support at three or four.
Which solution did I use previously and why did I switch?
We didn't previously use a different solution.
How was the initial setup?
The initial setup was straightforward. We didn't have any issues at all. I don't recall how long deployment took. It does depend on what the company needs though. It can vary from company to company. Most installations don't take longer than six hours at a maximum.
Three people handled the implementation.
What about the implementation team?
We handled the implementation process ourselves. We used our own team.
Which other solutions did I evaluate?
We did try out some other software before we decided on SolarWinds, but I don't recall the names of the other companies.
What other advice do I have?
We use the solution on a daily basis.
I'd advise others that if they just implement the software with an engineer that knows how to handle the installation they should be okay.
We've generally had a good experience using the product.
I'd rate the solution overall eight out of ten. I'd rate it higher if the support was better.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Systems Engineer at a healthcare company with 1,001-5,000 employees
Strengths include steady development and strong focus on Windows but don't install it on a multi purpose server
Solar Winds Orion is a strong contender in network monitoring up to (at
least) mid size enterprises. It’s particular strengths are steady
development and a strong focus on Windows. This focus gives it the
ability to drill deeper into application monitoring with less effort
than most of it’s competitors through WMI. SNMP is also supported for
non windows devices to round out the mix. The interface is primarily the
web console, which is highly configurable and can display completely
different options for different users/groups. However, building maps and
setting most alerts require a separate installed application for the
former and console access to the Orion server for the latter. Orion uses
MS SQL on the back end, and with more than a small network requires a
separate DB server from the web server and agent server(s). Yes, you can
use multiple monitoring servers for large networks. Pricing is tiered,
both for the type of monitoring (straight network, application, and
specialty items like VMWare are separate SKUs) and # of monitored
objects.
Competitors - quite a few. Whatsup Gold was purchased by Solar Winds a
couple years ago but is still a separate product. Others include Nagios,
MRTG, Cacti, on the open source side, and a host of ‘monitoring’
systems on the paid product side. Keep in mind that some of these are
less monitoring than ‘is it up’ ICMP pings, but there is a good range of
monitoring. I’ll let you inspect the field - this review is pretty
good: http://www. . Orion was selected as winner by the site, but keep in mind your needs and resources may vary.
Resist the urge to install monitoring on a multi purpose server, and
think very hard before using a ‘spare workstation’ or old server. It
benefits from lots of memory, and the DB needs adequate disk
performance. Database activity is greater than you’d think from the size
(especially when opening a graph or running a report). Also keep in mind
the aphorism that when problems occur it’s impossible to always
self-monitor; the very tool used may be the problem.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Network Engineer at a healthcare company with 501-1,000 employees
If you REALLY want to get the information we crave, you need to buy some of the plug-ins.
Out of the box, Solarwinds Network Performance Monitor does an adequate job of monitoring the basics of your network. Things like Bandwidth Utilization, syslog capture and reporting, circuit outages, etc. However, If you REALLY want to get the information we crave, you need to buy some of the plug-ins.
You start out with NTA, Netflow Traffic Analyzer. Now you don't just know that your bandwidth is being consumed. You know WHAT is taking a big bite out of that ALWAYS important bandwidth. Is it legitimate traffic and you need to add bandwidth or is it frivolous and you need to block it?
Next, if you operate call centers you might want to add on the VoiP and Network Quality Manager. I'm unfamiliar with this but it must have evolved from IP SLA Manager, a product I loved for it's ability to tell me how well my voice traffic was moving across the network. It looks like they've added integration with Call Manager so now you can really dig down into those voice related issues.
There's another piece you may consider indispensable if you have a lot of apps running across your network; Server and Application Monitor. Now we're cooking with gas!
Nowadays, it's just not enough to know that you still have bandwidth available. What you REALLY need to know is, do you have bandwidth available to ALL your key applications? QOS might be dropping packets while you are blithely examining your bandwidth utilization, thinking everything is running smoothly.
While Voice and one or 2 other apps may be blissfully travelling down the carpool lane of your network, what about the rest of your traffic? Is it stuck in a traffic jam, staring hungrily at those empty lanes? You NEED to know these things. And that's where the plugins will make your monitoring get up and DANCE! And once you KNOW what's going on on your network, YOU'LL be dancing too!
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior Security Consultant at a tech services company with 11-50 employees
An network monitoring solution that offers insights into servers and virtual machines
Pros and Cons
- "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."
- "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."
What is our primary use case?
We use the product for network monitoring.
What is most valuable?
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.
What needs improvement?
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.
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
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.
What other advice do I have?
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.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Technical Specialist, consultant at a tech vendor with 10,001+ employees
Great connection with management systems for networking devices, applications and servers
Pros and Cons
- "Can easily be interconnected with other management systems."
- "GUI needs improvement with a more graphical dashboard."
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
What do I think about the stability of the solution?
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.
How are customer service and technical support?
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.
How was the initial setup?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Integrator
Works at a energy/utilities company with 10,001+ employees
An extensible and scalable solution that suits our expanding network
Pros and Cons
- "It is very extensible with 'SWQL' and APIs to where we are beginning to integrate it with network automation."
- "This solution would benefit from expanding on the capabilities within the API."
What is our primary use case?
We use this solution for network node monitoring and alerting.
How has it helped my organization?
This solution has scaled as we have grown.
What is most valuable?
It is very extensible with 'SWQL' and APIs to where we are beginning to integrate it with network automation.
This solution has a very large and active user community.
What needs improvement?
This solution would benefit from expanding on the capabilities within the API.
Network automation is a hot topic now, and SolarWinds needs to be focused on developing the product with that in mind.
For how long have I used the solution?
I have been using this solution for two years, but it has been in my company for much longer.
What do I think about the scalability of the solution?
We are a larger and dispersed company so there are many, many network nodes monitored by NPM. It has been able to expand and scale to manage that well.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free SolarWinds NPM Report and get advice and tips from experienced pros
sharing their opinions.
Updated: October 2024
Product Categories
Network Monitoring Software IT Infrastructure Monitoring Cloud Monitoring SoftwarePopular Comparisons
Splunk Enterprise Security
Dynatrace
Datadog
Zabbix
New Relic
PRTG Network Monitor
Cisco DNA Center
Cisco Secure Network Analytics
ThousandEyes
Nagios XI
Mist AI and Cloud
Fortinet FortiSIEM
LogicMonitor
Centreon
Buyer's Guide
Download our free SolarWinds NPM Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- PRTG vs. SolarWinds: Which is a better Network Monitoring Tool?
- Which is the best network monitoring tool: Zabbix or Solarwinds? Pros and Cons?
- Can SolarWinds NPM be used by network solution providers? What needs to be taken into consideration?
- What Is The Biggest Difference Between NETSCOUT and SolarWinds?
- What SolarWinds NPM alternatives do you recommend?
- SolarWinds Network Performance Monitor compared to alternative solutions
- Is Zabbix or SolarWinds NPM better for infrastructure monitoring?
- How does Solarwinds NPM compare with Dynatrace?
- What is the main difference between SolarWinds NPM and Riverbed NetIM?
- When evaluating Network Performance Monitoring, what aspect do you think is the most important to look for?
First, I hope you've updated - the current release (10.6) of NPM has some really neat features, like instant access to server error logs and process monitors. Second, if you're just using the Network Performance Module (NPM) you're missing a lot. Application monitoring gives a much better picture of what's going on with your servers; the two together are pretty impressive.
As for sizing, we found that the newer capabilities a couple years ago added so much load we had to move the database to a separate server. Even then we were dropping data (empty space on the graphs) and replaced the monitor server last fall with a virtual system. We were on an older 32 bit server with 4 GB of RAM, moving to a 64 bit system gave us plenty of power and we no longer drop data. However our database server should be replaced; some reports and screens run slow when a lot of data is requested. It's a user experience issue, not a failure, so your milage may vary. Again, older hardware and 32 bit processors. Approach this in a stepwise fashion (separate the database first, etc) and you'll be fine.
Last point - be careful when adding monitors. It's easy to monitor too much; separate what is 'must have' from 'nice to have', add the 'must have' first and check system performance. That includes slow or saturated WAN links; it is possible to overload these with the extra traffic.
Let us know how the project goes!