Client-side metrics descriptions

Client-side metrics are available when you use the Bigtable client library for Java or the Bigtable HBase client for Java. This page provides a detailed description of each client-side metric.

To learn how to set up and configure client-side metrics, see Set up client-side metrics. For an overview, see the Client-side metrics overview.

Metrics are published to the region of the Bigtable cluster that they are for. If Bigtable can't resolve the cluster for a metric, like when an operation fails, then the metric is published to the global region and the cluster tag has the value unspecified.

Use client-side metrics in conjunction with server-side metrics for performance debugging. For a comprehensive list of Bigtable server-side and client-side metrics, see Metrics.

Operation latencies

Attempt latencies

Retry count

Application blocking latencies

Application blocking latencies timer examples

ReadRows requests are typically sent in one of three ways: iteratively, asynchronously, or as a future call. The following examples demonstrate the start and stop times for the application blocking latencies for each type of ReadRows operation.

Iterative

long totaLatency=0;
ServerStream<Row> stream = bigtableDataClient.readRows(query);

for (Row row : stream) {
   timer.start();
   // Do something with row
   timer.stop();
   totalLatency += timer.elapsed();
}

Asynchronous

client.readRowsAsync(query, new ResponseObserver<Row>() {
    @Override
    public void onStart(StreamController streamController) {

    }

    @Override
    public void onResponse(Row row) {
        timer.start();
        // Do something with the row
        timer.stop();
        totalLatency += timer.elapsed();
    }

    @Override
    public void onError(Throwable throwable) {
        // Do something with the error
    }

    @Override
    public void onComplete() {
    }
});

Future call

The application blocking latencies should be approximately 0 (no timer) for this type of ReadRows request.

List<Row> rows = bigtableDataClient.readRowsCallable().all().call(query);

First-response latencies

Server latencies

Connectivity error count

Client blocking latencies

What's next

• See all Google Cloud metrics.
• Install and configure client-side metrics.