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.
At least during our investigation thus far, all of these companies have a more responsive support organization and are more actively maintaininbg and supporting their products. They are also all significantly more expensive.
Verified User
Manager
Chose SolarWinds Pingdom
I have used Datadog's testing, and it is far more in-depth but more expensive. Pingdom was simple and easy to set up and very reliable, but Datadog had more advanced features but also cost a lot more and wasn't as simple to set up.
We have been with Pingdom since before it was SolarWinds Pingdom. It remains stable and solutions driven and has done so for many years. While it has many features we do not utilize, we are always looking to see which ones we can start to use when we have time. Some of the more …
We have only used Pingdom for these needs, so I can't speak directly to competitors. That being said, for the reasons we used Pingdom it was fantastic value and the fact we never bothered to look for a competitor speaks volumes about our satisfaction with the product.
We use a mixture of atlassian products and chose to use this at the beginning of 2020 when our org switched to full remote work posture. While it was nice having integration with opsgenie and our jira ticketing system it did not provide quite the mixture of flexibility and …
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
It is very suitable for our organization as metrics that it provides like disk space, CPU usage and availability of application, etc. And the main thing is it has good integration with OpsGenie and Jira Software so when our application is down or has any issue then we get a …
Some of the products mentioned here are much more "holistic solutions" for monitoring, analyzing, logging, alerting, etc., but for the use case, we use SolarWinds Pingdom. I think that SolorWinds Pingdom is much simpler and friendlier for configuring and maintaining. We …
we migrated from site 24x7 to pingdom because we have been facing issues with the monitoring and alerting. Our customers would reach out to us first rather than our monitoring tool notifying us that there is a problem. Its administration is also very complicated and compared to …
We have looked into using New Relic Synthetics to achieve the same results we are achieving with Pingdom, ultimately Pingdom is significantly cheaper for essentially the same functionality.
We selected SolarWinds Pingdom based on the feature set we desired, which was simply a monitoring solution for our websites and other critical network services. The decision to use SolarWinds Pingdom was based on the simplicity of their mobile app and website.
Newrelic has some simple uptime monitoring but it has very unclear pricing, which depends on how often you ping. And for our needs the next pricing bracket was way too much, maybe 10x. This could make sense if we were going to use the other monitoring capabilities of NewRelic …
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
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.
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.
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.
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.
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.