PingPlotter vs. SolarWinds Pingdom

It is well suited for performing monitoring and testing from a single device. It is less appropriate if you have to monitor from multiple different endpoints. That type of deployment would be more of an enterprise application. If you are looking for an end user monitoring solution then PingPlotter is the one for you.

Incentivized

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

Incentivized

• Monitor traffic in network
• Measure stops when contacting network locations such as websites
• Measures the lag and latency it takes to contact network locations
• Gives you both induvidual measurements as well as good oversight
• identifies when network lag or disconnect occurs

• 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

Incentivized

• Its a little confusing to see which targets are currently running pings and which ones are displayed in the plots.
• Starting and stopping pings requires a right click and that would be better with a play/pause button I think.
• Ability to drag and drop the graphs to reorder them.
• more columns to show which targets are running and which are displayed. Currently this is done with symbols so you cant sort by just the running targets for example I've found.

Incentivized

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

Incentivized

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.

Incentivized

Interface is unnecessarily complicated and frequently responds slowly.

I have not had much contact with the PingPlotter support, only one time have I went to them and it was a positive experience. The questions I had were answered quickly and professionally. I have no issue with the experience I had with the Support team. This was from before and after the purchase of the product.

Incentivized

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.

Incentivized

A balance of a generic tool vs a network equipment product is necessary when investigating network incidents or disruptions. Need to train the engineer to use both tools to perform their analysis and to dive down to the issues as fast as they can. Experience with the tools will continue to play a part if we were to adopt PingPlotter

Incentivized

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

Incentivized

• Great ROI, troubleshooting time has been reduced by 90%
• Network Discoveries used to take 2 to 3 hours and were inconsistent - now it is a matter of minutes
• lacks integration into our MSP toolkit, and we now use it as a stand alone product

Incentivized

• 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.
• Its time to explore other alternatives.