Splunk Log Observer vs. Sensu, by Sumo Logic

Great for organizations that need to centralize different types of logging across integration, qa, sandbox and production environments. Would be less impactful for organizations that don't have complex logging needs.

• 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

• Providing in-depth insights
• A related content feature which really helps us to figure out which service is breaking the infrastructure.
• The Log explorer which helps us to explore the entire log and pin point the errors/issues.
• Fast and powerful log investigation

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

• Integrating the system with Slack channels
• Saving the logs in different cloud provider
• Viewing the logs at more fine grained level based on user roles and permissions

Incentivized

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

Incentivized

I'm a Splunk specialist, and I'm involved in its use and improvement.

Incentivized

It gives access to data features for every level of users: from managers and executives to Analysts, each one with the correct level of observation and analysis.

Incentivized

Splunk support is very quick and efficient. Pre-sale specialists are very skilled and available.

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

Follow a training before starting.

Incentivized

I had not considered other products because Splunk Log Observer was in use in my company before I started working there.

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

• Significantly reduced the MTTR (Mean Time To Recovery), which in turn has improved the end-user experience tremendously.
• Meets compliance requirements of security policies, audit, regulation, and forensics.
• Helps us to track/manage the resource usage on our cloud instances which has a direct implication on the recurring cost.

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