You can enable the logging settings (System >> Operations >> Logs >> Logging Level Settings) for the Decision Table to Debug.  For example, you would select  Rule_Declare_DecisionTree.PYCHECKRESOLVEDSTATUS.Work_Cover_.Action to enable Debug for PyCheckResolvedStatus .    You will then get a logging statement for each "step" processed in the Decision Tree.  If you filter on the operator or Requestor ID in the log file, you will be able to see the exact sequence as one DT calls another.  Of course, you'll have to set the logging to DEBUG for ever DecisionTree you want to monitor, and do this on every node.  And then you'll have to parse the log to extract the information.  You can set the logging level by changing the log4j.xml (forget the exact name) on each node so it's more permanent and easier to propagate for each node.  It's not the cleanest way to do it, but it will generate the info you want.