N-able N-central vs SolarWinds Pingdom

N-able N-central is highly suitable for IT Admins within large organizations that need oversight of all it equipment. Ideal for managing organizations that need inventory and management of more than 10 IT devices. Highly inappropriate for smaller scale companies that mange less than 10 PCs

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.

• The alerts are very responsive offering quite detailed timing information
• The UI for reports is very clear and set up of reports is very intuitive
• Customer service was good when there were problems - e.g. lapsing billing causing reporting to go down

• Expensive software
• The support team are terrible
• Sales team will promise the world to get you over the line
• Subscription management is tedious
• Old software with very little development and the support team will not provide any further information on this - no roadmap
• Integrations galore - but none of them are effective

• 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.

Interface is unnecessarily complicated and frequently responds slowly.

For the most part, support has been good, but often we need to reach out to our account manager to ask that cases be escalated. First level support can often be frustrating to work with. There are particular support engineers that we know we won't get good service from when they are assigned to cases. The level of support offered did become worse when the company was sold to SolarWinds.

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.

Make sure if you your using a vm you follow the instructions for provisioning to the letter or it will be starting from square one

N-Central has automation manager, which allows you to automate multiple tasks, thereby saving time and effort through Automated patching. AV and Backups are built into the system, and can be deployed by checking a box. It's easy to update and keep secure. File transfer and remote controls are great and make easy work from off-site.

1. 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
2. Amazon CloudWatch is specific to AWS resources and cannot be easily use outside of the AWS Ecosystem

• Reduced time to manage and support servers and endpoints.
• Provides support dept with more accurate information to assess and resolve issues quicker and more efficiently.
• The subscription cost associated with N-central, to our clients has a good profit margin for us.

• Makes sure people trying out Quepid.com don't experience broken onboarding experiences.
• Confidence that when I bring up a demo for a customer, it is up and responding!
• Keeps my cloud-deployed services "warm" by hitting them every minute, so when I go to hit them, they are up and running.
• Confidence in your infrastructure.