TrustRadius Insights for SolarWinds Pingdom are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Business Problems Solved
Pingdom is a versatile tool that users rely on to monitor the uptime of their websites and ensure they are up and operational. With Pingdom's notifications via Mobile, Email, and Slack Integration, users can quickly resolve any downtime issues and avoid potential revenue loss. The tool is widely used by multiple departments within organizations for front-line monitoring of core public-facing services, allowing them to be proactive and react as soon as they receive a notification of downtime, preventing further issues. Additionally, Pingdom is used for uptime monitoring and verification of responses from specific endpoints, which assists in diagnosing issues. Its ability to support different monitoring types makes it a preferred choice for many users.
Furthermore, Pingdom serves as an uptime monitor for cloud applications, providing direct notifications and general uptime statistics. Users rely on Pingdom to monitor URL/endpoints and website uptime, ensuring optimal performance. It also helps in managing preventive failures and troubleshooting during scheduled maintenances. Additionally, Pingdom allows for the addition of notification-only users, facilitating collaboration with other teams. As a service provider, Pingdom is a primary tool for monitoring uptime for clients. Users appreciate its simplicity and ease of setup and maintenance. Integration with OpsGenie allows for quick resolution of alerts and efficient management of downtime. Overall, Pingdom is a helpful tool for monitoring and testing websites, analyzing page speed, overall performance, compliance with SLAs, and providing reliable customer service.
Loading Reviews List....
SolarWinds Pingdom Reviews
11 Reviews
Engineering
Search is temporarily unavailable. Filters are still applied.
Its our last frontier of monitoring. When things go bad we depend on using it for monitoring our public endpoints and to understand if something bad really happened. We have internal monitoring, but Pingdom has proven itself to be our fallback, and main public endpoint monitoring. We have integrated it with our Status pages, our on-call and it is one stop solution for our needs on the edge of our platform.
Pros
Multi endpoint monitoring
Latency monitoring
Tagging of alerts
Cons
Customized payload alerts for statuses different than 200
Grouping of alerts
Organisation support
Likelihood to Recommend
Pingdom has been one of our critical components for the past 5 years.When things go bad I depend on Pingdom to be our last frontier of our monitoring solution.Having in mind the time we have used the product I am amazed that we had only 1 false-positive alert for that period.Its strong, well positioned production that I will continue to recommend to every company I work for.
I would love to see more functionalities added to the external monitoring toolset of Pingdom, like direct integrations with the known softwares out there.
We at Hevo use Pingdom primarily for URL/endpoints and website uptime monitoring and alert tool. Also, each product team can set up monitoring of their internet-facing product on Pingdom.
Pros
URL/endpoints and website monitoring from different parts of the world
Uptime reporting
DNS uptime and alerting
Website speed test
Cons
Dashboard is a bit slow
The test reports download for a specific date range should be allowed
Likelihood to Recommend
Awesome and reliable tool for website uptime monitoring and alert tool with great reporting insight
We were using Pingdom to check the availability of our client's sites. Also we had a monitoring site in each of our web fleets, and we were using checks with each of those monitoring sites to detect when a fleet was down. We set alerts to be notified when sites were not accessible. It also helped us to provide our clients a visibility of theirs sites response using public status pages. It also helped to determine if we were under our SLA because Pingdom provided us how long a site was down. That way we could build the reports we sent to clients.
Pros
providing uptime stats
notifying us when sites were down
public status page (clients did love that)
Cons
Nothing at the top of my head right now. Our usage was very basic I guess, and we didn't have any issues using the available features.
Likelihood to Recommend
Basically with Pingdom we were able to provide a better service to our clients. I want to emphasise on public status pages. It is hard to provide clients access to our monitoring tools, and sometimes to make them public and secure it requires a bit of effort. With Pingdom, and a few clicks, clients were able to have a visibility of their sites behaviour.
It's well suited for scenarios where you need to set up some simple monitoring of uptime for your website, measure uptime trends over a longer period of time, the ability to set up SMS notifications for when the website is down and when it goes back up.
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.
Pros
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.
Cons
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.
Likelihood to Recommend
I've found Pingdom to be the best solution for relatively simple uptime checks when you need a reliable way to run those checks and alert on failures. I haven't used their transaction monitoring or Real User Monitoring features but it may be great at those too.
The product [SolarWinds Pingdom] is used to monitor different aspects of our product from different views, being as latency, or some special characteristics that we need to have available and measurable. [SolarWinds] Pingdom makes this easy and customizable, you can create custom monitoring scenarios and measure more than just the response time of the server.
Pros
Easy setup
Dashboards
Customizability
Cons
User interface
Filters
Comparison between locations
Likelihood to Recommend
The tool is well suited to create custom monitoring from the user's perspective. When you need a detailed overview on how your tool performs remotely from multiple locations, this tool is for you. Since it also supports custom ways to gather this view, it's easy to adapt to your needs, and monitor your custom applications and services as well.
As a services provider, [SolarWinds] Pingdom is our primary tool to monitor uptime for our clients.
Pros
Uptime monitoring, easy to setup, geographic redundancy and checking, easy to integrate
Transaction monitoring, easy to setup, geographic redundancy and checking, easy to integrate
Cons
Pricing on transaction checks and users is a bit old in style and not flexible enough.
Likelihood to Recommend
[SolarWinds Pingdom] is the central tool in our services support program. It allows me to easily track sites that are up and down and automatically create tickets in our helpdesk system.
I've deployed SolarWinds Pingdom in a few customer deployments to help facilitate site checking of the network post migration. This tool helps to check interconnectivity between data centers by checking the recovery and response of remote applications during a migration exercise. Demonstrating to the customer the ability of the tool to check their end hosts/applications and the length of outage builds up their confidence during a maintenance activity.
Pros
End host response.
End site recovery times.
API recovery.
Cons
Based on limited use I haven't seen any shortcomings as of yet.
Likelihood to Recommend
Corporate data center migrations are highly sensitive to any type of outage. During live system cutovers, network migrations and integration between data centers, Pingdom was used to check system communications and response times prior to, during and after the network activities. By monitoring the systems along with reports generated I was able to see the issues and address them quickly.
It is our internal alert system for server uptime/downtime alerts within our IT and Engineering departments. Primarily it acts as a notification system to alert our IT that something is amiss and also the sales and support staff so that they can update customers accordingly. Secondarily, there are situational integrations that we have set up to act as alerts for the network connection for certain servers to alert a specific use-case
group of users for testing purposes as well.
Pros
Customizable alerting: Allows text and email alerts that can be set up to run as many times as you wish and as frequently as you wish so that you can scale down or up accordingly to your use-case.
Integrations: We have integrated third-party applications such as Tibco products and Slack to bring alerting into our messaging system (Slack) and do alerting off of specific report run-times (Tibco products)
Communication: It offers groups of users that can be selected to alert based on a time interval so that we can alert teams based on the severity of the issue.
Cons
An easy way to update a mass group of alerts instead of one-by-one edits
Our less IT-oriented teams sometimes have a hard time understanding what the alerts mean, but that is a user education issue we should probably address ourselves to better explain purposes of alerts.
Likelihood to Recommend
Easy set up to alerts to servers/reports on servers based on certain criteria exception cases. Great options for testing purposes and for production use-cases to use as a mass alerting system to teams of users on the health of network connectivity. The price point is good and flexible depending on the number of alerts you have set up/ Insights for speed.
I used Pingdom at Qwiki where we added checks for various endpoints to ensure uptime and reasonable response times.
It is by far the most simple monitoring tool. It doesn't provide you all the details an internal monitoring tool can provide but for most part, it's a good must have due to ease of setup and maintenance (or lack of!).
Pros
simple endpoint checks
no maintenance on your end
it works
Cons
keep it simple and don't add new things
Likelihood to Recommend
It's the first line of defense for knowing when your endpoints aren't accessible.
