By stack trace exception I mean the automatic correlation between the exception stack trace with the request. For example, you can ignore specific know issue and In transaction snapshots, an ignored exception does not appear as an error in the Summary and Error Details sections of any transaction snapshot that was in progress when the exception occurred.
Concerning the ability to see the history of executionsI mean the ability to list of transaction snapshots, using Transaction Snapshot Flow Map displays.
You can see the history of the execution time, and timestamp of the transaction. The flow map also provides details of the overall time that is spent in a particular tier and in database and remote service calls.
The Applications dashboard and tabs, is a major point of the intuitiveness of the product, in fact It allows in a single view to have an overall impression of each application performance (for example Application Flow Map which depicts communications between different nodes and backends…).
The call Graph which is a powerful feature which allow to list the methods in a call stack and provides detailed informations about each call is another intuitiveness feature of the tool belong many other but the the better is to experiment the tool in a normal diagnostic case, my company and I can explain and assist your team more further with those features (we are based in France but also based at Montreal).