Splunk Application Performance Monitoring (APM) vs. Sensu, by Sumo Logic

Good for below cases 1. There is a front end and need to correlate data with front end data 2. multiple microservices and need to check the health of each system 3. correlate data from various sources 4. Application performance is a key to be captured 5. application performance is a key metric.

Incentivized

• Well suited for raising pagers when you have count-based metrics.
• Well suited for threshold-based metrics.
• Not well suited for tracking events over the day, since graphs and other visualizations are missing.

Incentivized

• Detect and Troubleshoot, which allows team to eliminate errors.
• Dashboard creates a one stop location for environment health
• Provides visibility, access to logs and user data real time.

Incentivized

• Unique concept as a "monitoring router" that can tie services together.
• Backward-compatible with Nagios environments.
• More of a DevOps focus than Nagios.

Incentivized

• I wish Splunk Application Performance Monitoring could integrate with packet capture and analysis tools and provide the integrated analysis results on each tier of the application

Incentivized

• Cannot be solely used for tracking metrics over time.
• Not a very good UI.

Incentivized

Splunk is a great tool for log mining. It is less time-consuming and easy to use. It provides high security, it has customisable dashboards. Furthermore, it acts as a search head, and it gives real-time status. It has the ability to collect data from any source and multiple sources, and it can correlate them.

Incentivized

Sensu's customer support was always willing to work with us but never really seemed to learn much from our experiences. I think they get a lot of customers with DevOps IT teams that are willing to put in a lot of elbow grease to get the most of Sensu's architecture. However, despite explaining my continued disappointment with their documentation and the overall flow of the product, I never got much more than a "sorry" and a notice that their documentation was open source if I wanted to contribute to it. The problem, of course, is that you can't document what you don't understand. I'm a former technical writer, so I know that better than most.

Incentivized

It is good that the correlation analysis and the cause of the failure can be analyzed more extensively through the collection of many data. It is good because it provides a user interface (usability) well and can be used conveniently.
It is good because it can utilize anomaly detection through various AI-based ML models.

Incentivized

Have used New Relic and Sematext Cloud for APM and for tracking over days and visualizing the issues. But those are very expensive as compared to Sensu.

Incentivized

• It gave us more quicker alerts in a organize way to distribute to specific audience.
• Helped us to improve our uptime by getting pro-active alerts via emails
• More collaboration in a DevOps culture

Incentivized

• Standing up the Sensu Go server took very little effort.
• Setting up and maintaining the build processes and deployment logic for Sensu assets and checks was somewhat exhausting and resulted in lower adoption among non-DevOps IT.
• The limited web interface resulted in lower adoption among non-DevOps IT.

Incentivized