Offline debugging by using Pega-TracerViewer
The Pega-TracerViewer tool presents and summarizes Tracer output data, that is saved in an .xml file, in an interactive table or tree format. By using TracerViewer, you can analyze the Tracer data offline to understand what happens on your system, determine where performance bottlenecks occur, and diagnose additional issues.
After you run the Tracer tool on Pega Platform, save the output as an .xml file to your local system, and then open it in the viewer.
Key features of Pega-TracerViewer 3.3
By using the TracerViewer 3.3, you can perform the following actions:
- View the Tracer data offline after the test is complete.
- Organize the data in a table or in tree views.
- Sort the data, for example, by the slowest call.
- Search the Tracer tool output data.
- View Performance tool statistics for each interaction.
- View alerts and SQL statements in the context of where and when they occur.
- Group traced events by a key, such as a unique SQL statement, stream, activity, or method.
The TracerViewer 3.3 supports standard Pega Platform applications that rely on Cosmos React. The output depends on the type of application that you trace. For Cosmos React, the output additionally includes DX API interaction IDs and DX API paths.
- Debugging applications by using Pega-TracerViewer
Provide bug-free applications by diagnosing and fixing issues, preventing bottlenecks, and analyzing events in your application by using the Pega-TracerViewer tool. You can generate Tracer output in an .xml format so that you can continue debugging offline or share the results with other developers.