Datadog vs. Sensu, by Sumo Logic

Datadog works really well with complex microservices architecture like any E-commerce platform which will be having multiple services but they all are interdependent to others so in this scenario Datadog will be best to monitor these as it will show the transactions also between those microservices. If you are using multiple services in your architecture whether it will be cloud services or on prem services Datadog will be the best choice to monitor all those service with in Datadog so that you can see everything in a single place. But if you are having small architecture and few services in that then in that scenario you can use Datadog but it will be little costly as compared to other but obviously the features are very well.

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

• Create Dashboards as per application, environments, and Custom metrics in one panel.
• Log aggregation, one-stop Application monitoring tools for the whole infrastructure.
• Playbooks, SLA definition, success and error quotas, request visualizations.
• DB monitoring, Serverless stack monitoring.
• Alerting of Production incidents so we can quickly resolve the issues on 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

• Alert windows cause lag in notifications (e.g. if the alert window is X errors in 1 hour, we won't get alerted until the end of the 1 hour range)
• I would appreciate more supportive examples for how to filter and view metrics in the explorer
• I would like a more clear interface for metrics that are missing in a time frame, rather than only showing tags/etc. for metrics that were collected within the currently viewed time frame

Incentivized

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

Incentivized

There is some room for improvement, but the Datadog team sends out updates frequently, and the UI is user-friendly for engineers, with no significant loading issues or region-specific problems. That was one of the key reasons we preferred Datadog; our company has employees worldwide, and it wasn't difficult to transition to the tool.

Incentivized

The support team usually gets it right. We did have a rather complicate issue setting up monitoring on a domain controller. However, they are usually responsive and helpful over chat. The downside would be I don’t think they have any phone support. If that is important to you this might not be a good fit.

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

We are still trying other products, but people still like Datadog. After setting up a dashboard, it's great for monitoring instances on Datadog. Also, the DevOps team had a good time setting up Datadog. It means Datadog was way easier to set up compared to those others.

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

• Saved us (time & money) from developing our own monitoring utilities that would pale in comparison
• Alerts allow us to remedy issues before our customers even know about them
• Tracking resource usage over time allows us to better plan for future needs, before it becomes a pain-point.

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