Back Trace

Usually when we analyse traces and find an Anchor (Volume 5, page 293) or Error Message (Volume 7, page 299) we do backtracking using a combination of Data Flow (Volume 7, page 296) and Message Sets (Volume 7, page 349) and selecting appropriate log messages to form a Back Trace leading to a possible root cause message:

This pattern is different from Error Thread (Volume 7, page 351) pattern which just backtracks messages having the same TID (or in general, ATID, Volume 5, page 279). It is also different from Exception Stack Trace (Volume 4, page 337) pattern which is just a serialized stack trace from memory snapshot.