Metrics and alerting policy filters

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
CUMULATIVEINT641
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
CUMULATIVEINT641
databasecenter.googleapis.com/Resource
Number of signals generated for resources.
issue_type: Type of signal.
resource/new_resource_count BETA(project)
New database resources
CUMULATIVEINT641
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
CUMULATIVEINT641
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
alloydb.googleapis.com/Cluster
An AlloyDB for PostgreSQL cluster.
alloydb.googleapis.com/Instance
An AlloyDB for PostgreSQL instance.
bigtableadmin.googleapis.com/Cluster
A Bigtable cluster.
bigtableadmin.googleapis.com/Instance
A Bigtable instance.
compute.googleapis.com/Instance
A Compute Engine instance.
firestore.googleapis.com/Database
A Firestore database.
oracledatabase.googleapis.com/AutonomousDatabase
An Oracle autonomous database resource.
oracledatabase.googleapis.com/CloudExadataInfrastructure
An Oracle cloud Exadata infrastructure resource
oracledatabase.googleapis.com/CloudVmCluster
An Oracle cloud VM Cluster resource
redis.googleapis.com/Cluster
A Redis cluster
redis.googleapis.com/Instance
A Redis instance
spanner.googleapis.com/Instance
A Spanner instance.
sqladmin.googleapis.com/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 product
  • engine—Type of engine
  • version—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
RESOURCE_FAILOVER_PROTECTED
The resource is failover protected.
GROUP_MULTIREGIONAL
The resource is part of a multi-regional group.
GROUP_REPLICA_POOL
The resource is part of a replica pool.
NO_AUTOMATED_BACKUP_POLICY
The resource has no automated backup policy.
SHORT_BACKUP_RETENTION
The resource has a short backup retention period.
LAST_BACKUP_FAILED
The last backup for the resource failed.
LAST_BACKUP_OLD
The last backup for the resource is older than 24 hours.
VIOLATES_CIS_GCP_FOUNDATION_2_0
The resource violates the CIS Google Cloud Foundation 2.0 benchmark.
VIOLATES_CIS_GCP_FOUNDATION_1_3
The resource violates the CIS Google Cloud Foundation 1.3 benchmark.
VIOLATES_CIS_GCP_FOUNDATION_1_2
The resource violates the CIS Google Cloud Foundation 1.2 benchmark.
VIOLATES_CIS_GCP_FOUNDATION_1_1
The resource violates the CIS Google Cloud Foundation 1.1 benchmark.
VIOLATES_CIS_GCP_FOUNDATION_1_0
The resource violates the CIS Google Cloud Foundation 1.0 benchmark.
VIOLATES_CIS_CONTROLS_V8_0
The resource violates CIS Controls 8.0.
VIOLATES_NIST_800_53
The resource violates NIST 800-53.
VIOLATES_NIST_800_53_R5
The resource violates NIST 800-53 R5.
VIOLATES_NIST_CYBERSECURITY_FRAMEWORK_V1_0
The resource violates NIST Cybersecurity Framework 1.0.
VIOLATES_ISO_27001
The resource violates ISO-27001.
VIOLATES_ISO_27001_V2022
The resource violates ISO-27001 v2022.
VIOLATES_PCI_DSS_V3_2_1
The resource violates PCI-DSS v3.2.1.
VIOLATES_PCI_DSS_V4_0
The resource violates PCI-DSS v4.0.
VIOLATES_CLOUD_CONTROLS_MATRIX_V4
The resource violates Cloud Controls Matrix 4.
VIOLATES_HIPAA
The resource violates HIPAA.
VIOLATES_SOC2_V2017
The resource violates SOC2 v2017.
LOGS_NOT_OPTIMIZED_FOR_TROUBLESHOOTING
Logs aren't optimized for troubleshooting.
QUERY_DURATIONS_NOT_LOGGED
Query durations aren't logged.
VERBOSE_ERROR_LOGGING
Error logging is configured to be verbose.
QUERY_LOCK_WAITS_NOT_LOGGED
Query lock waits aren't logged.
LOGGING_MOST_ERRORS
Error logging for statements is misconfigured.
LOGGING_ONLY_CRITICAL_ERRORS
Error logging for statement severity is misconfigured.
MINIMAL_ERROR_LOGGING
Error logging for message severity is misconfigured.
QUERY_STATS_LOGGED
Query statistics are being logged.
EXCESSIVE_LOGGING_OF_CLIENT_HOSTNAME
There is excessive logging of the client hostname.
EXCESSIVE_LOGGING_OF_PARSER_STATS
There is excessive logging of parser statistics.
EXCESSIVE_LOGGING_OF_PLANNER_STATS
There is excessive logging of planner statistics.
NOT_LOGGING_ONLY_DDL_STATEMENTS
The configuration isn't set to log only DDL statements.
LOGGING_QUERY_STATS
Query statistics are being logged.
NOT_LOGGING_TEMPORARY_FILES
Temporary files aren't being logged.
CONNECTION_MAX_NOT_CONFIGURED
The maximum number of concurrent connections isn't configured.
USER_OPTIONS_CONFIGURED
User options are configured.
EXPOSED_TO_PUBLIC_ACCESS
The resource is exposed to public access.
UNENCRYPTED_CONNECTIONS
The resource allows unencrypted direct connections.
NO_ROOT_PASSWORD
The root user has no password.
WEAK_ROOT_PASSWORD
The root user has a weak password.
ENCRYPTION_KEY_NOT_CUSTOMER_MANAGED
The encryption key isn't managed by the customer.
SERVER_AUTHENTICATION_NOT_REQUIRED
Server authentication isn't required because contained database authentication is enabled.
EXPOSED_BY_OWNERSHIP_CHAINING
The resource is exposed by ownership chaining.
EXPOSED_TO_EXTERNAL_SCRIPTS
The resource is exposed to external scripts.
EXPOSED_TO_LOCAL_DATA_LOADS
The resource is exposed to local data loads.
CONNECTION_ATTEMPTS_NOT_LOGGED
Connection attempts aren't logged.
DISCONNECTIONS_NOT_LOGGED
Disconnections aren't logged.
LOGGING_EXCESSIVE_STATEMENT_INFO
Excessive statement information is being logged.
EXPOSED_TO_REMOTE_ACCESS
The resource is exposed to remote access.
DATABASE_NAMES_EXPOSED
Database names are exposed.
SENSITIVE_TRACE_INFO_NOT_MASKED
Sensitive trace information isn't masked.
PUBLIC_IP_ENABLED
The resource has a public IP enabled.
IDLE
The resource is idle.
OVERPROVISIONED
The resource is overprovisioned.
HIGH_NUMBER_OF_OPEN_TABLES
The resource has a high number of open tables.
HIGH_NUMBER_OF_TABLES
The resource has a high number of tables.
HIGH_TRANSACTION_ID_UTILIZATION
The resource has high transaction ID utilization.
UNDERPROVISIONED
The resource is underprovisioned (high resource utilization).
OUT_OF_DISK
The resource is nearing or at its storage capacity.
SERVER_CERTIFICATE_NEAR_EXPIRY
The server certificate is nearing its expiration date.
DATABASE_AUDITING_DISABLED
Database auditing is disabled.
RESTRICT_AUTHORIZED_NETWORKS
The resource violates the policy restricting authorized networks.
VIOLATE_POLICY_RESTRICT_PUBLIC_IP
The resource violates the policy restricting public IP.
QUOTA_LIMIT
The resource is nearing its cluster quota limit.
NO_PASSWORD_POLICY
There is no password policy configured.
CONNECTIONS_PERFORMANCE_IMPACT
A high number of connections is impacting disk performance.
TMP_TABLES_PERFORMANCE_IMPACT
The use of temporary tables is impacting performance.
TRANS_LOGS_PERFORMANCE_IMPACT
Transaction log activity is impacting disk performance.
HIGH_JOINS_WITHOUT_INDEXES
A high number of joins without indexes is impacting performance.
SUPERUSER_WRITING_TO_USER_TABLES
A superuser is writing to user tables.
USER_GRANTED_ALL_PERMISSIONS
A user has been granted all permissions.
DATA_EXPORT_TO_EXTERNAL_CLOUD_STORAGE_BUCKET
Data has been exported to an external Cloud Storage bucket.
DATA_EXPORT_TO_PUBLIC_CLOUD_STORAGE_BUCKET
Data has been exported to a public Cloud Storage bucket.
WEAK_PASSWORD_HASH_ALGORITHM
A weak password hash algorithm is being used.
NO_USER_PASSWORD_POLICY
There is no password policy for users.
HOT_NODE
A node in the cluster has high utilization.
NO_DELETION_PROTECTION
Deletion protection isn't enabled.
NO_POINT_IN_TIME_RECOVERY
Point-in-time recovery isn't enabled.
RESOURCE_SUSPENDED
The resource is suspended.
EXPENSIVE_COMMANDS
Expensive commands are being run.
NO_MAINTENANCE_POLICY_CONFIGURED
A maintenance policy isn't configured.
INEFFICIENT_QUERY
Inefficient queries are being run.
READ_INTENSIVE_WORKLOAD
The workload is read-intensive.
MEMORY_LIMIT
The resource is nearing its memory tier limit.
MAX_SERVER_MEMORY
The maximum server memory is misconfigured.
LARGE_ROWS
Large rows have been detected.
HIGH_WRITE_PRESSURE
The resource is experiencing high write pressure.
HIGH_READ_PRESSURE
The resource is experiencing high read pressure.
ENCRYPTION_ORG_POLICY_NOT_SATISFIED
The organization's encryption policy isn't satisfied.
LOCATION_ORG_POLICY_NOT_SATISFIED
The organization's location policy isn't satisfied.
OUTDATED_MINOR_VERSION
The resource is running an outdated minor version and requires a patch.
SCHEMA_NOT_OPTIMIZED
The database schema isn't optimized.
MANY_IDLE_CONNECTIONS
There are many idle connections.
REPLICATION_LAG
There is high replication lag.
OUTDATED_VERSION
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.

  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.

  2. 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.
  3. 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:
    1. In the Active resources menu, select Database Resource.
    2. In the Active metric categories menu, select Resource.
    3. In the Active metrics menu, select New database signals.
    4. Click Apply.
    The fully qualified name for this metric is databasecenter.googleapis.com/resource/new_signal_count.
  4. 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