Azure Monitor vs. Sensu, by Sumo Logic

We were able to get a single pane of glass for all our monitoring needs on Azure Monitor. However, we would like to see it improve to auto scale out and scale in depending on the load without human intervention. This can help us get to the No Ops model and rely on automated processes rather than manual intervention.

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

• It supports all the Azure PAAS services.
• Can monitor both infrastructure and application

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

• Custom metrics
• Ease of use

Incentivized

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

Incentivized

I have not had to work with Azure Monitor support, so it is difficult to say how well the support team is. I assume that Azure has a well-versed team on the customer service side to assist with any issues customers may have. I may need them in the feature.

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

While other tools have their own unique capability, Azure Monitor helps us monitor essential PAAS services that are not supported by other tools. So even though we have one other APM tool, we still rely on Azure Monitor for some of the special PAAS services, this is a huge advantage.

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 are able to react quickly to the issues.
• Debugging sessions are yielding quicker results to generate RCA.

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