Apica vs. Sensu, by Sumo Logic

As I use this for only my area, it is very well suited to what I need it to do. Apica Synthetic monitors two different web applications in a time interval that is easily customizable for uptime and latency. These are critical indicators for a cloud-based point-of-sale system. We need solid uptime and limited latency across the enterprise.

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

• Auto alerts trigger if any issue is identified
• Graphical representation of the health of applications
• Good product support from the team

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

• It's very clunky. Infrastructure is large and very difficult to upgrade.
• SaaS and On-premise versions are different. There is an LDAP integration but users can only be assigned to one group (i.e. department). If you are in 2 departments, you need 2 separate logins.
• Update: they now offer federated logins
• It filled a gap in monitoring for us, but we're looking to move on.

Incentivized

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

Incentivized

We trust the results that Apica Synthetic has achieved. Real-time alerting is critical to our clients and with limited resources, we can't handle many false positives; Apica Synthetic is the only solution that provides both of those features.

Incentivized

As per my experience while using it. Thanks!

Apica Synthetic is very effective while configuring the account setup for any of the database/UserID.

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

Easy for implementation in our Infrastructure, Easy for troubleshooting the issue and Easy to use as well.

We were using different monitoring tools for different requirements (e.g.,Nagios and Checkmk for infrastructure issues) and we were in need of a tool for service and API monitoring for which we were using ThousandEye. But alerts were 60-70% valid irrespective of conditions like network issues. But Apica Synthetic's alert mechanism is a perfect fit for our department. It helped us to reduce unnecessary/false alerts and a number of wrong tickets.

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

• My department is not charged for Apica Synthetic so no ROI, but from a customer service perspective, we can react to an outage and repair it faster than our customers can report the outage.
• Our vendor's own monitoring tools are not as accurate nor as timely as ours. They rely on us telling them, from Apica Synthetic, that they have an issue.

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