PingPlotter vs. Splunk Infrastructure Monitoring

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

Splunk Infrastructure Monitoring is well suited for any complicated environment where you have apps and servers across multiple clouds and platforms and products. If you have a data centre where all your apps and servers are in one single network, you could probably get away with older solutions. But for any modern, complex, hybrid-cloud microservices environment, Splunk Infrastructure Monitoring is a must-have.

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

• SignalFX handles historical metric aggregation exceptionally well, providing a multifaceted approach to event detection based on anomalies.
• SignalFX's cost is incredibly flexible with their pricing model of DPM (data-point per minute) vs the traditional "per host" model that most monitoring SaaS use.
• SignalFX support is responsive and knowledgeable, very eager to help solve your immediate problems.
• SignalFX integrations is vast and constantly growing, making adoption easy even when multiple different open-source technologies are used in your stack.

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

• Better integration with our clients (native mobile clients SDKs will be great).
• A way to easily tag filters and move them across metrics/formula.
• Alert system to easy false [alarm] and hard to configure.
• Be able to have group more dimensions (and have more values on each).

Incentivized

Good: Stable system with low error rate Easy to use for simple use cases Bad: UI is not very clear for complex usage Mobile view (when logged in from phone) is bad No library for .net

Incentivized

I find that learning the interface can take some time. We need a better show-and-tell on how the Teams pages, Dashboard Groups, Dashboards and charts delay. Advance SignalFlow is sometimes hard to build. Some better samples of advanced SignalFlow would be helpful. For example, Splunk SPL has a vast resource of examples.

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

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

They’re not for the same purpose but we’re using NewRelic and Honeycomb for monitoring purposes. NewRelic is used for HTTP client monitoring for system related throughput, error, database and external client monitoring. Honeycomb is used to monitor actual HTTP request/response values. Splunk [Infrastructure Monitoring] is used for real-time application related throughout and error monitoring.

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

• Reduced downtime.
• Caused us to get a lot of spam when we redeployed apps and old instances stopped sending metrics. Muting alerts solves this, but people often forget to do it or do it incorrectly.
• Helped us find historical info about instances/apps.

Incentivized