MSPs
and IT professionals use N-able™ N-central® to monitor and manage devices and complex
networks remotely. N-central provides
visibility and efficiency as the user's needs scale. N-central can help users:
1. Proactively monitor everything on a customer network—not just servers
and workstations—and troubleshoot.
2. Stay on top of threats with features like MFA, antivirus, integrated endpoint
detection and response, data backup, disk encryption, email protection,…
N/A
SolarWinds Pingdom
Score 9.2 out of 10
N/A
SolarWinds Pingdom is a website uptime monitoring and alert tool, with additional reporting and Real User Monitoring capabilities. Pingdom is part of SolarWinds’s DevOps package, enabling full-stack monitoring as a service.
$14.95
per month
Pricing
N-able N-central
SolarWinds Pingdom
Editions & Modules
No answers on this topic
Synthetic Monitoring
$10
per month
Real User Monitoring
$10
per month
Enterprise
Custom Pricing
Offerings
Pricing Offerings
N-able N-central
SolarWinds Pingdom
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
N-able N-central
SolarWinds Pingdom
Features
N-able N-central
SolarWinds Pingdom
Monitoring Tasks
Comparison of Monitoring Tasks features of Product A and Product B
N-able N-central
7.3
6 Ratings
1% below category average
SolarWinds Pingdom
-
Ratings
Remote monitoring
9.56 Ratings
00 Ratings
Network device monitoring
8.26 Ratings
00 Ratings
Management Tasks
Comparison of Management Tasks features of Product A and Product B
N-Able is perfect for an MSP environment. It gives all the standard functionality an IT professional needs out of the box and can be configured to show almost anything required. For example, we have configured a dashboard to show when our backups need attention for each customer. This is achieved by running a small script on repeat via N-Central everyday/evening, and the result gives us information on the dashboard to help us identify exactly what is working and what needs looking into.
I believe the scenarios we used it for were quite well covered, from the executive perspective. The downtime alarms worked very well and were easy to setup, uptime monitoring tools were clear and easy to use, even for non-technical people (C-level) and the SLA management tools allowed us to spend less time, and have less friction, with our clients
Remote tasks - entry-level techs can run basic tasks without physically touching a piece of equipment.
Remote support - remote controlling user devices is easy and saves a lot of time with having to initiate a remote session.
Management of devices, particularly patch management and anti-virus management - you can automatically approve and deploy patches and schedule automatic AV scans.
Customer support just points to online guides and I feel they aren't helpful.
During the trial they turn on a lot of features. In my experience, if you play around with the features, they charge you for them. Keep this in mind if you move forward with N-Able - they will charge for "trialed" services.
In my experience, some services that you're being charged for can't be disabled or monitored by you or your team. You only see them on the monthly invoice.
In my opinion, the "Scripting Automation" doesn't provide value. You're either going to be writing your own batch or Powershell to make scripting work.
In my opinion, monitoring software deployments is painful.
The default monitoring template can't be duplicated, edited, or referenced. You'll find that the default monitors in an unusual way and will throw needless recurring alerts into your ticketing system. To avoid this, you need to create a template from scratch which takes many hours to set up.
In my opinion, they're more concerned about a quick buck than customer service. "Buyer beware" company.
The PagerDuty integration could be a lot better. When you use the PagerDuty integration, it doesn't send any information about which check failed! It just sends a message like "Timeout (> 30s)" -- this isn't very helpful when we have hundreds of checks. We've worked around this by using both the PagerDuty and Slack integrations and having them both post to the same Slack channel. But this means that when an engineer is paged from PagerDuty, they have to go to Slack (or Pingdom) to find the details about the page; it's not available on the page itself.
Overall we have liked our solar winds experience, however, as our company has grown to support larger enterprises, this product does not have the functionality that our teams need in order to fully support them. The lack of granularity with backups and lack of ability to support nutanix environments is slowly drawing us into the use of other tools.
Recently added features have made Pingdom less intuitive for our requirements. While Pingdom has a broad offering and remains a good value, it is becoming more than we need. Our customer base is becoming more and more global and Pingdom still lacks Asia-Pacific monitoring, which we will need within a year.
The user interface is fairly straight forward, with logic groupings for objects. I did not deploy this software, but am one of the daily administrators. Once you get the correct agent package (Which can be a challenge) the integration into AD is not bad. The UI could be more customized, but that may have been a design choice.
Pingdom is easy to use, very intuitive and has a very short learning curve. From the onset, we've been able to jump in and leverage the tool to accomplish our goals for page speed performance and discover the insights we need to make improvements. Its a well-designed tool and makes for a good user experience.
Every time we have reached out to SolarWinds they are quick to respond, even offering support chat 24/7. Their support team is great and works with you to find solutions to issues. They have taken items we had issues with before and used those to create updates so that the issue is handled better in the future.
Support responded the same day to my query, as I was setting the product up but couldn't find the setting I needed. This was successfully resolved in a short time frame, so I was pleased with how quickly we were able to get this resolved. I haven't needed to contact support since.
Our version of SolarWinds was old and running on old hardware, but it was way easier to setup and do things with. It did not do everything N-able does such as patch management, or at least we didn't have a module to do so if one existed. However it definitely seemed easier to use and possibly more stable.
PRTG Network Monitor was a far more complicated tool to use and set up albeit it does both Internal and External monitoring. The setup wasn't intuitive and there are too many configuration options to complete to form an alert
Amazon CloudWatch is specific to AWS resources and cannot be easily use outside of the AWS Ecosystem
Honestly, we have 4 other products that overlap this functionality whose organizations provide far superior support. At this point it is an unnecessary expense.
In my opinion, their lack of support responsiveness and commitment has impacted our IT agility.