This document provides an overview of the metrics generated by Database Center. It also describes how you can use filters to restrict data that is charted or monitored by alerting policies. To help you identify and troubleshoot performance issues for database products such as Cloud SQL, AlloyDB for PostgreSQL, and Spanner, create custom dashboards that display useful metrics and information about your alerting policies.
Database Center metric types
This section lists the metric types that are generated by Database Center.
The "metric type" strings in this table must be prefixed
with databasecenter.googleapis.com/
. That prefix has been
omitted from the entries in the table.
When querying a label, use the metric.labels.
prefix; for
example, metric.labels.LABEL="VALUE"
.
Metric type Launch stage (Resource hierarchy levels) Display name |
|
---|---|
Kind, Type, Unit Monitored resources |
Description Labels |
Resource/new_resource_count
BETA
(project)
New database resources |
|
CUMULATIVE , INT64 , 1
databasecenter.googleapis.com/Resource |
Number of new database resources.
product :
Type of product.
engine :
Type of engine.
version :
Version of the product.
|
Resource/new_signal_count
BETA
(project)
New database signals |
|
CUMULATIVE , INT64 , 1
databasecenter.googleapis.com/Resource |
Number of signals generated for resources.
issue_type :
Type of signal.
|
resource/new_resource_count
BETA
(project)
New database resources |
|
CUMULATIVE , INT64 , 1
databasecenter.googleapis.com/Resource |
Number of new database resources.
product :
Type of product.
engine :
Type of engine.
version :
Version of the product.
|
resource/new_signal_count
BETA
(project)
New database signals |
|
CUMULATIVE , INT64 , 1
databasecenter.googleapis.com/Resource |
Number of signals generated for resources.
issue_type :
Type of signal.
|
Table generated at 2025-08-28 21:10:54 UTC.
About metric filters
When you create charts or alerting policies, you can add filters to restrict the metric data that's charted or monitored. For example, you might add a filter so a chart displays data only for a specific resource. Your charts and notifications from alerting policies can help you troubleshoot issues. They can also help you gain deeper insights into the health of your database fleet.
A filter is composed of a label key and a label value. For example, a label
key might be resource_container
and the label value is a specific resource
container. You can filter metric data by metric labels and by resource labels:
Metric labels let you filter alerts based on a characteristic of the metric type, such as the database product type or signal type.
Resource labels let you filter alerts based on a property of the monitored resource, such as its location or name.
Filter values are case-sensitive and must be entered exactly as they appear in the tables in this document.
You can add multiple filters to a chart or alerting policy. If you add multiple filters, then only metric data that match all labels is shown.
The remainder of this document lists metric labels and resource labels that you can use to filter the metric data that Database Center generates. We recommend that when you create a filter, you copy and paste the filter values listed in this document into into the filter element.
Filter by resource type
The following label keys let you filter your
New database resources (resource/new_resource_count)
and
New database signals (Resource/new_signal_count)
metric data by
the resource type:
resource_container
monitored_resource_container
location
resource_type
full_resource_name
For all label keys except resource_type
, when you create the filter in
the Google Cloud console, the value menu lists all valid values.
For the label key resource_type
, the list of label values from which you can
choose in the Google Cloud console might be incomplete.
Use the following table to choose a supported resource type:
resource_type |
Definition |
---|---|
|
An AlloyDB for PostgreSQL cluster. |
|
An AlloyDB for PostgreSQL instance. |
|
A Bigtable cluster. |
|
A Bigtable instance. |
|
A Compute Engine instance. |
|
A Firestore database. |
|
An Oracle autonomous database resource. |
|
An Oracle cloud Exadata infrastructure resource |
|
An Oracle cloud VM Cluster resource |
|
A Redis cluster |
|
A Redis instance |
|
A Spanner instance. |
|
A Cloud SQL instance. |
Filter by product, engine, or version
The New database resources (resource/new_resource_count)
metric type
defines the following label keys:
product
—Type of productengine
—Type of engineversion
—Version of the product
Each row in the following table lists valid combinations of label values. For
example, if you add the filters product=CLOUD_SQL
and
version=SQLSERVER_2022_WEB
to a chart, then the chart might display data.
However, if you add the filters product=CLOUD_SQL
and version=2
to a chart,
then the chart won't display data.
product |
engine |
version |
---|---|---|
ALLOYDB |
POSTGRES |
14 , 15 , 16 , 17 |
BIGTABLE |
NATIVE |
N/A |
CLOUD_SQL |
MYSQL |
5.6 , 5.7 , 8.0 ,
8.4 |
CLOUD_SQL |
POSTGRES |
9.6 , 10 , 11 , 12 ,
13 , 14 , 15 , 16 ,
17 |
CLOUD_SQL |
SQL_SERVER |
SQLSERVER_2017_EXPRESS , SQLSERVER_2017_STANDARD ,
SQLSERVER_2017_ENTERPRISE , SQLSERVER_2017_WEB ,
SQLSERVER_2019_EXPRESS , SQLSERVER_2019_STANDARD ,
SQLSERVER_2019_ENTERPRISE , SQLSERVER_2019_WEB ,
SQLSERVER_2022_EXPRESS , SQLSERVER_2022_STANDARD ,
SQLSERVER_2022_ENTERPRISE , SQLSERVER_2022_WEB |
COMPUTE_ENGINE |
MYSQL , POSTGRES , SQL_SERVER |
N/A |
FIRESTORE |
FIRESTORE_WITH_NATIVE_MODE ,
FIRESTORE_WITH_DATASTORE_MODE ,
FIRESTORE_WITH_MONGODB_COMPATIBILITY_MODE |
N/A |
MEMORYSTORE |
MEMORYSTORE_FOR_REDIS |
3.2 , 4.0 , 5.0 , 6.X , 7.0 , 7.2 |
MEMORYSTORE |
MEMORYSTORE_FOR_REDIS_CLUSTER |
7 |
SPANNER |
NATIVE |
N/A |
Filter by signal type
The New database signals (resource/new_signal_count)
metric type
defines the one label key, issue_type
. The value of this label is set to
a signal type.
For the label key issue_type
, the list of resource types from which you can
choose in the Google Cloud console might not include all the supported values.
Use the following table to choose a supported signal type:
issue_type |
Definition |
---|---|
|
The resource is failover protected. |
|
The resource is part of a multi-regional group. |
|
The resource is part of a replica pool. |
|
The resource has no automated backup policy. |
|
The resource has a short backup retention period. |
|
The last backup for the resource failed. |
|
The last backup for the resource is older than 24 hours. |
|
The resource violates the CIS Google Cloud Foundation 2.0 benchmark. |
|
The resource violates the CIS Google Cloud Foundation 1.3 benchmark. |
|
The resource violates the CIS Google Cloud Foundation 1.2 benchmark. |
|
The resource violates the CIS Google Cloud Foundation 1.1 benchmark. |
|
The resource violates the CIS Google Cloud Foundation 1.0 benchmark. |
|
The resource violates CIS Controls 8.0. |
|
The resource violates NIST 800-53. |
|
The resource violates NIST 800-53 R5. |
|
The resource violates NIST Cybersecurity Framework 1.0. |
|
The resource violates ISO-27001. |
|
The resource violates ISO-27001 v2022. |
|
The resource violates PCI-DSS v3.2.1. |
|
The resource violates PCI-DSS v4.0. |
|
The resource violates Cloud Controls Matrix 4. |
|
The resource violates HIPAA. |
|
The resource violates SOC2 v2017. |
|
Logs aren't optimized for troubleshooting. |
|
Query durations aren't logged. |
|
Error logging is configured to be verbose. |
|
Query lock waits aren't logged. |
|
Error logging for statements is misconfigured. |
|
Error logging for statement severity is misconfigured. |
|
Error logging for message severity is misconfigured. |
|
Query statistics are being logged. |
|
There is excessive logging of the client hostname. |
|
There is excessive logging of parser statistics. |
|
There is excessive logging of planner statistics. |
|
The configuration isn't set to log only DDL statements. |
|
Query statistics are being logged. |
|
Temporary files aren't being logged. |
|
The maximum number of concurrent connections isn't configured. |
|
User options are configured. |
|
The resource is exposed to public access. |
|
The resource allows unencrypted direct connections. |
|
The root user has no password. |
|
The root user has a weak password. |
|
The encryption key isn't managed by the customer. |
|
Server authentication isn't required because contained database authentication is enabled. |
|
The resource is exposed by ownership chaining. |
|
The resource is exposed to external scripts. |
|
The resource is exposed to local data loads. |
|
Connection attempts aren't logged. |
|
Disconnections aren't logged. |
|
Excessive statement information is being logged. |
|
The resource is exposed to remote access. |
|
Database names are exposed. |
|
Sensitive trace information isn't masked. |
|
The resource has a public IP enabled. |
|
The resource is idle. |
|
The resource is overprovisioned. |
|
The resource has a high number of open tables. |
|
The resource has a high number of tables. |
|
The resource has high transaction ID utilization. |
|
The resource is underprovisioned (high resource utilization). |
|
The resource is nearing or at its storage capacity. |
|
The server certificate is nearing its expiration date. |
|
Database auditing is disabled. |
|
The resource violates the policy restricting authorized networks. |
|
The resource violates the policy restricting public IP. |
|
The resource is nearing its cluster quota limit. |
|
There is no password policy configured. |
|
A high number of connections is impacting disk performance. |
|
The use of temporary tables is impacting performance. |
|
Transaction log activity is impacting disk performance. |
|
A high number of joins without indexes is impacting performance. |
|
A superuser is writing to user tables. |
|
A user has been granted all permissions. |
|
Data has been exported to an external Cloud Storage bucket. |
|
Data has been exported to a public Cloud Storage bucket. |
|
A weak password hash algorithm is being used. |
|
There is no password policy for users. |
|
A node in the cluster has high utilization. |
|
Deletion protection isn't enabled. |
|
Point-in-time recovery isn't enabled. |
|
The resource is suspended. |
|
Expensive commands are being run. |
|
A maintenance policy isn't configured. |
|
Inefficient queries are being run. |
|
The workload is read-intensive. |
|
The resource is nearing its memory tier limit. |
|
The maximum server memory is misconfigured. |
|
Large rows have been detected. |
|
The resource is experiencing high write pressure. |
|
The resource is experiencing high read pressure. |
|
The organization's encryption policy isn't satisfied. |
|
The organization's location policy isn't satisfied. |
|
The resource is running an outdated minor version and requires a patch. |
|
The database schema isn't optimized. |
|
There are many idle connections. |
|
There is high replication lag. |
|
The resource is running an outdated major version. |
Example: Create a chart
To visualize the number of new database resources on a chart, follow these instructions. You can follow the same procedure for the other Database Center metric types.
-
In the Google Cloud console, go to the leaderboard Metrics explorer page:
If you use the search bar to find this page, then select the result whose subheading is Monitoring.
- In the toolbar of the Google Cloud console, select your Google Cloud project. For App Hub configurations, select the App Hub host project or the app-enabled folder's management project.
- In the Metric element, expand the Select a metric menu,
enter
New database signals
in the filter bar, and then use the submenus to select a specific resource type and metric:- In the Active resources menu, select Database Resource.
- In the Active metric categories menu, select Resource.
- In the Active metrics menu, select New database signals.
- Click Apply.
databasecenter.googleapis.com/resource/new_signal_count
. Filter your data by the signal type and resource type:
- To filter by the signal type, in the Filter element, click Add filter, and then select issue_type. For the label value, select or enter a value.
- To filter by the resource type, in the Filter element, click Add filter, and then select resource_type. For the label value, select or enter a value.
What's next
- Learn more about Google Cloud Observability.
- Learn more about alerting policies.
- Learn more about metric-based incidents.