Analysis Reports

Analysis reports in Stackdriver Trace show you an overall view of the latency for requests to your application, or for a subset of the requests. You can create an analysis report using a single set of parameters, or generate a report over two sets of parameters, which allows you to compare two different sets of latency data. Stackdriver Trace also automatically creates a daily report comparing the previous day's performance to the same day the week before.

Create an analysis report

To create an analysis report, you can:

Create a new analysis report

To create an analysis report:

  1. Open the trace overview for your project.

  2. Click the Analysis Reports tab.

  3. Click New Report.

    Enter or select the following properties in the form that appears:

    Property Description
    Request URI Full URI for the request or partial stem URI. Use the forward slash character (/) to view all requests. Optional. Default is all requests.
    HTTP Method HTTP method for the request. Default is All.
    HTTP Status HTTP status returned by the request. Default is All.
    Report Name Human-readable name for the report. Optional. If no name is specified, Stackdriver Trace creates a name based on the specified request URI and the time at which the report was created.
    Module App Engine module (Java, Python, Go or PHP) that handled the request. Default is All.
    Version Version of the App Engine application that handled the request. Default is All.
    Time Range Time range during which the requests occurred. You can select Last Hour, Last 24 Hours, Last Week or Custom Range. If you select Custom, you must specify the start and end times for the range. Default is Custom.

  4. To create a report that compares two sets of data, select Create Comparison and specify the module, application version and time range for the second data set.

  5. Click Submit.

Note: Stackdriver Trace must have at least 100 stored traces that match the parameters you specify to create a report. If there are less than 100 traces, a warning message is displayed and no report will be created.

Create a similar (duplicate) report

Stackdriver Trace also provides the option to Create a similar report, which duplicates the chosen report and allows you to edit one or more parameters. To create a report this way:

  1. View an existing analysis report.

  2. Click Create similar report. The New report request screen appears.

  3. Edit one or more report parameters and click Submit.

Note: Stackdriver Trace must have at least 100 stored traces that match the parameters you specify to create a report. If there are less than 100 traces, a warning message is displayed and no report will be created.

View an analysis report

To view an analysis report:

  1. Click the Analysis Reports tab in Stackdriver Trace.

    The analysis reports list appears and shows both the system-generated daily report and any custom reports you have created.

  2. Click the name of a report.

    The analysis report appears.

View the overall request latency

The Latency Density Distribution tab in the analysis report shows a graphical distribution of requests in the report along a logarithmic axis of average latency times.

Stackdriver Trace overall request latency

If you created a comparison report, Stackdriver Trace overlays the data from the two data sets so that you can compare them and analyze any changes.

Stackdriver Trace overall request latency

The Latency panel below the graph view shows average latency times by percentage with links to traces for representative sample requests. You can click on a trace number to view its details in the trace details view.

Stackdriver Trace overall request latency

Stackdriver Trace will attempt to identify performance bottlenecks and report them, if found, in a Bottleneck panel in the view. This panel highlights RPC calls that are significant contributors to latency in the requests and displays them by percentile with representative sample requests. You can then click on a trace number to view its details.

In a report that compares two sets of latency data, the bottlenecks highlights the RPC calls that caused latency distribution changes between the two sets.

Stackdriver Trace overall request latency

View the cumulative request latency

The Cumulative Distribution tab in the analysis report shows what percentage of requests have completed along an logarithmic axis of average latency times.

Stackdriver Trace overall request latency

If you created a comparison report, Stackdriver Trace overlays the data from the two data sets so that you can compare them and analyze any changes.

Stackdriver Trace overall request latency

Send feedback about...

Stackdriver Trace Documentation