View Data Boost eligibility metrics

Bigtable Data Boost is a serverless compute service designed for high-throughput read jobs and queries. A workload must meet certain compatibility criteria to be able to use Data Boost.

This document describes how to check eligibility metrics to determine whether your workload is compatible with Data Boost. Review these metrics if you are are considering converting a standard app profile that is already in use to a Data Boost app profile.

Before you view eligibility metrics, review the details on ideal workloads and feature limitations at Bigtable Data Boost overview.

Eligibility metrics overview

To help you determine whether the workload for a given app profile is suitable for Data Boost, Bigtable provides two metrics:

  • Data Boost traffic eligibility count (data_boost/eligibility_count)
  • Data Boost traffic ineligible reasons (data_boost/ineligible_reasons)

For more information, see Metrics.

Check eligible and ineligible request counts

To determine whether traffic that is sent by a given app profile is suitable for Data Boost, look at the metric Data Boost traffic eligibility count. This metric shows the number of requests that are eligible or ineligible for Data Boost for a given app profile for the last seven days.

To view this metric for a specific app profile, follow these steps:

  1. In the Google Cloud console, go to the  Metrics explorer page:

    Go to Metrics explorer

    If you use the search bar to find this page, then select the result whose subheading is Monitoring.

    It opens in the last project you viewed.

  2. In the Metric drop-down, choose Cloud Bigtable Table > Server > Data Boost traffic eligibility count.

  3. Click Apply.

  4. Add filters.

    1. In the Filter field, select app_profile, and then in the Value field, choose the ID of the app profile to check.
    2. In the Filter field, select instance, and then in the Value field, choose the instance ID the app profile is for.

  5. In the Aggregation drop-down, choose Sum.

  6. In the by drop-down, check the boxes for app_profile, eligibility, project_id, and cluster.

View an app profile's ineligibility reasons

The Data Boost traffic ineligible reasons metric tells you why requests sent with a given app profile are considered ineligible for Data Boost. A single request can have multiple reasons for being ineligible. Reasons for ineligibility include the following:

  • The app profile was used for requests that called API methods other than ReadRows, PingAndWarm, or SampleRowKeys.
  • The app profile was used for reverse scans.
  • Traffic was sent using an incompatible client library.
  • Requests using the app profile exceeded 1,000 read requests per second.

To view this metric for a specific app profile, follow these steps:

  1. In the Google Cloud console, go to the  Metrics explorer page:

    Go to Metrics explorer

    If you use the search bar to find this page, then select the result whose subheading is Monitoring.

    It opens in the last project you viewed.

  2. In the Metric drop-down, choose Cloud Bigtable Table > Server > Data Boost traffic ineligibility reasons.

  3. Click Apply.

  4. Add filters.

    1. In the Filter field, select app_profile, and then in the Value field, choose the ID of the app profile to check.
    2. In the Filter field, select instance, and then in the Value field, choose the instance ID the app profile is for.

  5. In the Aggregation drop-down, choose Sum.

  6. In the by drop-down, check the boxes for app_profile, eligibility, project_id, and cluster.

Conversion-blocking configurations

If you attempt to convert a standard app profile to use Data Boost, the conversion fails if any of the following conditions are true for the app profile.

  • The instance uses CMEK encryption.
  • It's configured for multi-cluster routing.
  • Single-row transactions are enabled.
  • It routes to a cluster in an instance that uses HDD storage.

What's next