Skip to main content
The XBOX services Trace Analyzer reviews the service calls made by a title. The XBOX services Trace Analyzer is an offline analysis tool, to find any violations in calling patterns. The Trace Analyzer (XblTraceAnalyzer.exe) can be found as part of the GDK and XboxLiveTools.zip; see Development tools for XBOX services. This is a command-line tool. There is a readme file about this tool in the .zip file.

​
Gather logs and analyze the service calls

The following steps are required to gather the logs that contain the record of your service calls and analyze them using XBOX services Trace Analyzer.
  1. Build your title.
  2. Modify your title to enable tracing as described below.
  3. Deploy your title.
  4. Launch the title and make at least one call to XBOX services in order to initialize the XBOX services API.
  5. Start tracing at the point in your title you’d like to analyze.
  6. Stop tracing.
  7. Run the XBOX services Trace Analyzer tool on your development PC and view the output.

​
Starting and stopping tracing

On GDK titles, it is currently recommended to use Fiddler to capture the trace file of the target device. Then save the Fiddler results as a Fiddler Session file (.saz) which the XBOX services Trace Analyzer tool can read. See Using Fiddler to inspect web service calls.

​
Analyze the trace file

To analyze your title’s use of XBOX services, after the trace file has been copied back to your PC, you can use the XBOX services Trace Analyzer tool on GDN. For a description of how to invoke the tool and interpret its output, see the documentation included with the XBOX services Trace Analyzer tool on Game Developer Network. To view command line help, you can also run XblTraceAnalyzer.exe with the command line option of -? or -h.
Last modified on August 20, 2026

Related topics

Best practices for calling XBOX servicesStats and achievementsLeaderboardsDevelopment tools for XBOX servicesTools for XBOX services