This page describes how you can use the Cloud SQL System insights dashboard.
The System insights dashboard displays metrics for the resources that your
instance uses and helps you detect and analyze system performance problems.
You can use Gemini in Databases assistance to help you observe and
troubleshoot your Cloud SQL for MySQL resources. For more information, see
Observe and troubleshoot with Gemini assistance.
View the System insights dashboard
To view the System insights dashboard, do the following:
In the Google Cloud console, go to the Cloud SQL Instances page.
Select the System insights tab from the SQL navigation panel on the left.
The System insights dashboard opens.
Dashboard image showing metrics and events timeline.
Figure 1. Dashboard image showing events timeline and summary cards.
The System insights dashboard shows the following information:
Your instance details
Events timeline:
shows the system events, in a chronological order.
This information helps you evaluate the impact of system events on the health
and performance of the instance.
Summary cards:
provide an overview of the instance health and performance by displaying the
latest and aggregated values for the CPU utilization, disk utilization, and
log errors metrics.
Metrics charts: show the
information about the operating system and database metrics that help you gain
insight into several issues, such as throughput, latency, and cost.
The dashboard offers the following high-level options:
To create a customized dashboard, click Customize dashboard.
To keep the dashboard up to date, enable the
Auto Refresh option. When you enable Auto Refresh, the dashboard data
updates every minute. This feature isn't compatible with customized time
periods.
The time selector shows 1 day selected by default. To change the period,
select one of the other predefined periods or click Custom and define a
start and end time. Data is available for the last 30 days.
To create an absolute link to the dashboard, click the Copy Link button.
You can share this link with other Cloud SQL users who have the same
permissions.
To create an alert for a specific event, click
notifications Notification.
To display specific alerts, click Annotations.
Summary cards
The following table describes the summary cards displayed at the top of the System
Insights dashboard. These cards provide a brief overview of the instance's health
and performance during the chosen time period.
Summary card
Description
CPU utilization - P50
The P50 CPU utilization values.
CPU utilization - P99
The P99 CPU utilization values.
Disk utilization
The latest disk utilization value.
Log errors
The number of errors that were logged.
Metrics charts
The toolbar on each chart card provides the following set of standard options:
To view metric values for a specific moment in the selected period, move the
cursor over the chart.
To zoom in on a chart, click the chart and drag horizontally along the x-axis
or vertically along the y-axis. To revert the zoom operation, click
Reset zoom. Or, click one of the predefined time periods at the top of the
dashboard. Zoom operations apply at the same time to all charts on a dashboard.
To view additional options, click more_vertMore chart options. Most charts offer these options:
To view a chart in full-screen mode, click View in full screen. To exit
full-screen mode, click Cancel.
Hide or collapse the legend.
Download a PNG or CSV file of the chart.
View in Metrics Explorer. View the metric in Metrics Explorer.
You can view other Cloud SQL metrics in the Metrics Explorer after
selecting the Cloud SQL Database resource type.
To create a custom dashboard, click editCustomize dashboard and give it a name. Or, expand the Predefined menu
and select an existing custom dashboard.
To view a metric chart's data in detail, click query_statsExplore data. Here, you can filter specific metrics and choose how the
chart displays:
Customizable view of Cloud SQL metric data.
To save this customized view as a metric chart, click Save to dashboard.
Default metrics
The following table describes the Cloud SQL metrics that appear by default
on the Cloud SQL System insights dashboard.
Database load per database/user/client address dbinsights.googleapis.com/ aggregate/execution_time
The accumulated query execution time per database, user, or client address.
This is the sum of CPU time, I/O wait time, lock wait time, process context switch,
and scheduling for all processes involved in query execution.
The memory components available to the database as usage, cache, and free memory.
The value for each memory component is calculated as the percentage of the total memory available to the database.
MySQL queries cloudsql.googleapis.com/ database/mysql/queries
The number of statements executed by the server. This includes statements executed within stored programs,
such as stored procedures and functions.
MySQL questions cloudsql.googleapis.com/ database/mysql/questions
The number of statements executed by the server. This includes only the statements sent
to the server by the clients and not the statements executed within stored programs.
MySQL network traffic cloudsql.googleapis.com/ database/mysql/received_bytes_count cloudsql.googleapis.com/ database/mysql/sent_bytes_count
The number of bytes received from and sent to the clients.
InnoDB total pages cloudsql.googleapis.com/ database/mysql/innodb_buffer_pool_pages_total
The number of dirty, free, and total pages in the InnoDB buffer pool.
A dirty page in the InnoDB buffer pool is a page that's modified
in the memory but isn't written back to the disk. A free page in InnoDB buffer
pool is a page that doesn't contain any data and is unused.
open_tables is the number of tables currently open. opened_table_count is the number of tables that the database has opened since the last sample.
If the value of opened_table_count is consistently high, we recommend that you
increase the value of table_open_cache.
open_table_definitions is the number of table definitions that are currently open.
opened_table_definitions_count is the number of times the database has opened
a table definition since the last sample. If the value of opened_table_definitions_count
is consistently high, we recommend that you increase the value of table_definition_cache.
Memory usage for the InnoDB data dictionary cache. InnoDB has its own cache for
storing information about database objects such as tables, columns, indexes, and foreign keys.
table_definition_cache sets a soft limit on the number of tables
in this cache. However, tables with foreign key relationships are kept in cache
until the database shuts down or restarts. This cache can consume a significant amount of memory
if your instance has many tables with foreign key relationships.
Disk storage by type cloudsql.googleapis.com/ database/disk/bytes_used_by_data_type
The breakdown of instance disk usage by data types, such as data, binlog, and tmp_data.
This metric helps you understand your storage costs. For more information about
storage usage charges, see
Storage and networking pricing.
Point-in-time recovery (PITR)
uses binary logs. Cloud SQL generates new logs regularly
and these logs use storage space. Cloud SQL automatically deletes the binary logs and
their associated automatic backups. This generally happens after
the retention value set for transactionLogRetentionDays is met.
transactionLogRetentionDays is the number of days for which
Cloud SQL retains the transaction logs. Its value ranges from 1 to 7.
To avoid unexpected storage
issues while using PITR, we recommend that you enable
automatic storage increases.
read_ops_count indicates the delta count of disk read I/O operations.
You can use this metric to
understand whether your instance is correctly sized for your environment.
If required, you can switch to a larger machine type to serve more
requests from cache and reduce latency.
write_ops_count indicates the
delta count of disk write I/O operations. Cloud SQL instances, barring replicas, write to a system
table, approximately, every second.
Cloud Logging
logging.googleapis.com/ log_entry_count
Shows the total number of log entries for errors and warnings.
[[["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年11月03日 UTC."],[],[]]