ITRS Geneos vs. Sensu, by Sumo Logic

ITRS Geneos is well suited in any situation where uptime is mission critical.

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

• ITRS Geneos has many built-in plugins to integrate with other widely used tools like Control-M.
• Apart from being the monitoring tool, it provides different features like capacity planning and log analytics.
• ITRS Geneos' new UI is quick, responsive and user-friendly.

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

• The only problem I really had was the adjustment abilities of the GUI, otherwise it was a great product.

Incentivized

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

Incentivized

ITRS Geneos support is well managed by its wide variety of options like live chat, query submissions, 24/7 on-call support, self help and of course well-documented details about its features and troubleshooting methods. ITRS Geneos is being used by many big size organizations because it is a stable product with a good pool of knowledge available about it.

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

Every tool that competes in the market with ITRS Geneos has its own capabilities and shortcomings. For our project, ITRS Geneos stands out since it is a stable product with a long history of serving large organizations with huge number of components to monitor. ITRS Geneos has upgraded itself to a new and better GUI interface and has offered integration with different tools.

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

• Prevented losses in trades
• Efficient server maintenance
• Preventative server maintenance

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