Google Cloud Operations Suite vs. Sensu, by Sumo Logic

Easy to set up in all environments. With this tool, the company is now able to measure both well-functioning data and data that needs immediate intervention. This early detection facilitates decisions about actions to correct the disorder and improve indexes. Stackdriver is now essential for the company's security and monitoring team and we plan to expand to other branches.

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

• All the application error reporting available at a single place.
• You will get the real-time application error and alerts.
• It's really easy to use and no need to worry for the setup.

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

• For searching and filtering the logs the system is slow sometimes.
• An agent needs to be installed in each VM to monitor specific metrics.
• The pricing model is confusing.

Incentivized

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

Incentivized

It is also a great problem detection tool, and this is extremely important for General Motors.

The user can count on the ease of flexible panels and advanced visualization tools that help to identify problems. Among the most common, we can mention:

- containment of hosts;

- cloud provider limitation;

- hardware wear.

And also Stackdriver Integration with other Google Cloud data tools such as BigQuery, Cloud Pub/Sub, Cloud Storage and Cloud Database.

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

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

• We completely depends on Stackdriver for error monitoring and reporting.
• Stackdriver is very simple to use and available at default.
• Stackdriver is the key part for our business to get the insight of our application behavior.

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