dynaTrace Diagnostics is an application performance management solution fulfilling the measurement and diagnosis requirements that have been identified earlier. Specifically designed to support the whole application life-cycle, dynaTrace’s PurePath technology captures essential information for all transactions during their execution across multiple servers in heterogeneous distributed environments at very low overhead (Figure 6). This enables IT personnel to:

• Understand the dynamic behavior of the software so that, where possible, performance problems can be prevented, and
• Detect and diagnose performance problems so they can be quickly resolved whenever they occur.

A transaction’s PurePath identifies the code executed by the transaction, the execution context and the server on which it was executed.

In addition to high-level performance indicators, dynaTrace Diagnostics maps out the precise execution path - the PurePath - of each individual transaction from its entry at the first monitored server, through all other servers where it is processed, across system and technology boundaries. PurePath uses KnowledgeSensors™ to capture all performance and relevant context information with minimum performance overhead.









































KnowledgeSensors mark a transaction’s progress along its execution path and identify all transaction method calls or servlet invocations, their sequence and nesting. For each transaction, the KnowledgeSensors record performance information like method call sequence, arguments, return values, exceptions, log messages, elapsed time and resource usages statistics such as CPU usage, IO usage, network traffic, objects created, SQL calls, remote calls, and synchronization delays; see Figure 7 below.

PurePath allows one to reconstruct problem scenario without trial and error.

dynaTrace Diagnostics records the PurePath for all transactions at very low overhead and sends it to the Diagnostics server for analysis. This ensures that IT personnel:

• Have a complete record of execution for all transactions,
• Have a record of each transaction’s execution across application tiers, servers and machines,
• Can actually see the transaction’s execution path, and avoid guessing by trying to follow its execution from one server to the next,
• Can understand the dynamic behavior of the software,
• Can determine the root cause of the problem experienced by a specific transaction the first time – without having to pre-specify what transactions to monitor and then wait for the problem to recur,
• Can replay problem scenarios, including problem transactions, fromrecorded data and pinpoint the exact cause of performance problems quickly, avoiding traditional, expensive trial and error approach,
• Can diagnose problems in near real time or afterwards, and
• Can do diagnosis off-line without loading the production systems.