Percepio Tracealyzer vs. Sensu, by Sumo Logic

This is a perfect tool to debug complex bugs in your system, especially in regards to inter-task communication. It is also a great tool for beginners, as the documentation is accessible and the support given by the company is excellent

• 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

• Great visualization
• Sometimes awkward views (vertical vs horizontal)

• 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 not always easy to include/integrate Tracealyzer in the OS build. It would be nice to have a simple install/plug n play method for our target.
• Sometimes, the .bin files from Tracealyzer don't always work and we don't know why

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

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 we started using uCOSIII for our simpler microcontroller products, we also use QNX on more complex targets (full microprocessors) and it is a much more complex platform offering event tracing, memory tracing, and performance measures that are extremely good and integrated. More importantly these tools are fully integrated without any code changes. Tracealyzer is not integrated as much into uCOSIII like QNX's tools, debugger, etc. But, going thru the manual work of adding Tracealyzer to the build, it did help us get to a shippable product.

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

• Positive: We were able to find some thread priority issues with Tracealyzer.
• Positive: we were able to see timing of events in the sw/hw that we couldn't otherwise see.

• 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