Stay organized with collections
Save and categorize content based on your preferences.
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)
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:
Open the list of Bigtable instances in the Google Cloud console.
Click the instance whose metrics you want to view.
In the navigation pane, under Insights, click Monitoring.
Click the Application profiles tab.
View the Data Boost eligibility chart.
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.
Click the instance whose metrics you want to view.
In the navigation pane, under Insights, click System insights.
Click the Application profiles tab.
View the Data Boost eligibility chart.
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[[["\u003cp\u003eBigtable Data Boost is a serverless compute service for high-throughput read jobs, but workloads must meet certain compatibility criteria to use it.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eData Boost traffic eligibility count\u003c/code\u003e metric shows the number of requests eligible or ineligible for Data Boost for a given app profile over the last seven days.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eData Boost traffic ineligible reasons\u003c/code\u003e metric explains why requests are ineligible, such as using incompatible API methods, reverse scans, or exceeding 1,000 read requests per second.\u003c/p\u003e\n"],["\u003cp\u003eConverting a standard app profile to Data Boost fails if the instance uses CMEK encryption, multi-cluster routing, single-row transactions, or routes to a cluster with HDD storage.\u003c/p\u003e\n"]]],[],null,["# View Data Boost eligibility metrics\n===================================\n\nBigtable Data Boost is a serverless compute service designed for\nhigh-throughput read jobs and queries. A workload must meet certain\ncompatibility criteria to be able to use Data Boost.\n\nThis document describes how to check eligibility metrics to determine whether your\nworkload is compatible with Data Boost. Review these metrics if you are are\nconsidering converting a **standard app profile that is already in use** to a\nData Boost app profile.\n\nBefore you view eligibility metrics, review the details on\nideal workloads and feature limitations at [Bigtable\nData Boost overview](/bigtable/docs/data-boost-overview).\n\nEligibility metrics overview\n----------------------------\n\nTo help you determine whether the workload for a given app profile is suitable\nfor Data Boost, Bigtable provides two metrics:\n\n- Data Boost traffic eligibility count (`data_boost/eligibility_count`)\n- Data Boost traffic ineligible reasons (`data_boost/ineligible_reasons`)\n\nFor more information, see [Metrics](/bigtable/docs/metrics).\n\nCheck eligible and ineligible request counts\n--------------------------------------------\n\nTo determine whether traffic that is sent by a given app profile is suitable for\nData Boost, look at the metric `Data Boost traffic eligibility count`.\nThis metric shows the number of requests that are eligible or ineligible for\nData Boost for a given app profile for the last seven days.\n\nTo view this metric for a specific app profile, follow these steps:\n\n1.\n Open the list of Bigtable instances in the Google Cloud console.\n\n\n [Open the instance list](https://console.cloud.google.com/bigtable/instances)\n2.\n Click the instance whose metrics you want to view.\n\n3. In the navigation pane, under **Insights** , click **Monitoring**.\n\n4. Click the **Application profiles** tab.\n\n5. View the **Data Boost eligibility** chart.\n\nView an app profile's ineligibility reasons\n-------------------------------------------\n\nThe `Data Boost traffic ineligible reasons` metric tells you *why*\nrequests sent with a given app profile are considered ineligible for\nData Boost. A single request can have multiple reasons for being ineligible.\nReasons for ineligibility include the following.\n\n- The app profile was used for requests that called API methods other than `ReadRows`, `PingAndWarm`, or `SampleRowKeys`.\n- The app profile was used for [reverse scans](/bigtable/docs/reads#reverse-scan).\n- Traffic was sent using an incompatible client library.\n- Requests using the app profile exceeded 1,000 [read requests per second](/bigtable/docs/monitoring-instance#console-monitoring-resources). For more information, see [What it's not good\n for](/bigtable/docs/data-boost-overview#not-good-for).\n\nTo view this metric for a specific app profile, follow these steps:\n\n1.\n Open the list of Bigtable instances in the Google Cloud console.\n\n\n [Open the instance list](https://console.cloud.google.com/bigtable/instances)\n2.\n Click the instance whose metrics you want to view.\n\n3. In the navigation pane, under **Insights** , click **System insights**.\n\n4. Click the **Application profiles** tab.\n\n5. View the **Data Boost eligibility** chart.\n\nConversion-blocking configurations\n----------------------------------\n\nIf you attempt to convert a standard app profile to use\nData Boost, the conversion fails if any of the following conditions are true\nfor the app profile.\n\n- The instance uses CMEK encryption.\n- It's configured for multi-cluster routing.\n- Single-row transactions are enabled.\n- It routes to a cluster in an instance that uses HDD storage.\n\nWhat's next\n-----------\n\n- [Read the Bigtable Data Boost overview.](/bigtable/docs/data-boost-overview)\n- [Create or configure an app profile.](/bigtable/docs/configuring-app-profiles)\n- [Learn more about Bigtable monitoring.](/bigtable/docs/monitoring-instance)"]]
