Skip to main content

Operations

The Operations tab breaks a database down into its operations - each a class of query, such as a SELECT against a given table - so you can find the slowest or busiest and drill into its query spans. It is the database analog of a service's Transactions tab.

Use the Top N selector (Top 5, Top 20 by default, or Top 100) to set how many operations to return; they are ranked by total time spent. The selection applies to both the charts and the table.

The Operations tab for a database: the Time consuming, Query time, Queries/s, and Failures/s charts above the per-operation table.

Charts​

Four charts summarize the selected operations:

  • Time consuming: cumulative time spent per operation. The tallest bands are the operations the database spends the most time on.
  • Query time: query duration per operation at a selected percentile (Avg, P50, P75, P90, P95, or P99).
  • Queries/s: query throughput per operation.
  • Failures/s: failed queries per second, per operation.

Operations table​

The table below the charts lists each operation with:

  • Operation: the database statement or command the row aggregates.
  • Table: the table or collection the operation reads or writes.
  • Calling services: how many services issued the operation.
  • Avg and P50-P99: query duration, on average and by percentile.
  • Total requests and Queries/s: query volume and throughput.
  • Total errors, Errors%, Failures/s, and Errors/min: failed-query counts and rates.
  • Time consuming: the operation's cumulative time and its share of the operations shown.

Use Search operations to find one by name, Manage columns to choose which columns show, and Export to download the table. Select an operation to open its drilldown, where you can inspect the individual query spans and open the traces they belong to.

Next steps​

Triage a database's failing queries in Errors.

Last updated on
Was this page helpful?