Grafana vs. PingPlotter

Grafana is a one stop solution for all application monitoring needs. In our organisation, we use nodeJs. We run it using pm2. Since we didn't use Grafana it was hard for us to know if an app has stopped working unless we find it ourselves because our other app components were failing, or someone called us up and told about the situation. We were already using Grafana for monitoring our Ubuntu servers, but we hadn't had set it up for our app monitoring. Somehow we decided to monitor our nodeJs app with Grafana. It's a really good decision we made. We used Grafana nodeJs module "prom-client" for our node app which brought us relief from app failing situations. Since we have implemented Grafana for our Node app, it has helped us to monitor every health aspect of our node app. Now we have set up alerts based on heap-memory, so when heap memory goes beyond a set threshold we get notified and take the right steps ultimately saving our app from crashing and of course from losing business and reputation.

Incentivized

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

• It visualizes metrics very well coming from any well known data source.
• It sends alerts to collaboration channels when a threshold is breeched.
• Graphs and dashboards are portable (Graph-as-a-Code).

• 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

• Functions to customize values
• Improved user experience

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

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

Grafana has a direct plugin to Icinga monitoring solution and allowed for easy configuration for us. At the time of implementation, other services did not have such an integration. As we already had a very customized and heavily introduced monitoring solution in place, we needed settings that could plug into the system quickly and efficiently. This was the case with Grafana and allowed us to have all the integrations we needed with services such as Icinga

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

• Helps us to keep our application and server up all time
• Dashboards are easy to share with others

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