Percepio Tracealyzer vs. Progress Telerik Fiddler

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

I am a senior software engineer and I have actively made fiddler a requirement for all of our engineers to have on their laptops by default. I have recommended it to all web developers that I have worked with and contractors that I have worked with as it has saved my mental stability on numerous occasions when trying to show people details of various web requests when working on integrations between different systems This is an absolutely fantastic product that I have used in a technical capacity many, many times and I will always suggest it as a tool when someone is debugging specifically but also for initial development to see how the requests are formed and for sharing responses and requests details so that others can recreate the request that you have sent through right down to the smallest detail

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

• 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

• The display could potentially become a bit more user-friendly over time, it's pretty easy to follow but for example, I always view the raw request/response information by default and this is not the default selection, being able to choose the default selection would be nice
• Clearer information and options to reduce 'noise' when viewing the requests, there are often a lot of background requests being sent on a computer, you can filter to roughly see what you want and filter out things that you don't want but there are different types of requests and I can't see how to filter between those - possibly a feature but could be made easier to use potentially
• Nothing else to put, this is a fantastic product so there isn't much else to suggest at this stage of using it and I have been using fiddler for years now in my role as a software engineer

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.

• 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.

• Overall this tool has sped up the process of integrating with new systems infinitely
• The cost of fiddler everywhere which is what we use specifically is nothing in comparison to the cost of dev time saved when debugging processes
• Being able to send information around so simply to other support teams to show them what responses we are getting along with the request detail have made communications much quicker and saves a lot of time going back and forth discussing what is being done and what the request is being sent