Overall Satisfaction with SolarWinds Pingdom
We needed a service that would monitor our sites' uptime and alert us if any of our web services go down. We have a main web application that supports thousands of customers, and about 30 smaller applications that support single high-value customers. This means we need at least 30 checks (really more like 40 because there are a number of different endpoints to check within our main application) so we wanted something that could be configured programmatically so that we don't have to maintain all of these checks by hand.
- Alerting, particularly the integration with PagerDuty.
- Reporting: the ability to go back and view the history of each status check (including details about every failure) as well as graphs and reports over a longer time period.
- Weekly uptime report emails are very convenient.
- Programmatic configuration is possible with a third-party Terraform plugin.
- 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.
- Pingdom has ensured that we've been aware of customer outages before our customers are. It's helped us be proactively responsive to service incidents.
I've only interacted with SolarWinds support once but they were responsive and well-informed.
Do you think SolarWinds Pingdom delivers good value for the price?
Are you happy with SolarWinds Pingdom's feature set?
Did SolarWinds Pingdom live up to sales and marketing promises?
Did implementation of SolarWinds Pingdom go as expected?
Would you buy SolarWinds Pingdom again?