Using Offline Trace

You're viewing Apigee X documentation.
View Apigee Edge documentation.

The Offline Trace tool lets you view and analyze "offline" trace sessions that were previously downloaded. A saved trace session is essentially a "recording" of a trace session, and can be useful for cases where troubleshooting and further analysis is required. The UI for the Offline Trace tool is similar to the "live" Trace tool.

To learn about the Trace Tool UI and on downloading trace sessions, see Using Trace.

To view downloaded trace data using Offline Trace:

  1. Sign in to the Apigee UI.
  2. Select API Proxies from the main view.
  3. Select Develop > Offline Trace.

    The Offline Trace view displays:

    Trace view

  4. To load data into the Offline Trace view, click either of the Choose File buttons.

    The Apigee UI loads the trace file's data and displays it:

    A view of actual offline trace data in the Apigee UI.

    Note the following regions of the Offline Trace view:

    • Top Left: Displays the request type. Use this area to navigate among the requests.
    • Bottom Left: Displays configuration options, as described in Using Trace.
    • Top right: Displays details about the trace session.
    • Middle right: Shows the path of the request through the API proxy; this path is known as the transaction map; it shows which policies were encountered and indicates if any errors occurred during the execution of those policies.
    • Bottom right: Shows the request headers for the currently selected request.

    When viewing trace data in the Apigee UI, you can toggle various options such as whether to view policies that are disabled or variables and properties. For more information, see Debugging with trace.