RetroSearch Browse

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://cloud.google.com/sql/docs/mysql/monitor-active-queries below:

Monitor active queries | Cloud SQL for MySQL

Monitor active queries

Stay organized with collections Save and categorize content based on your preferences.

This page describes how to monitor and troubleshoot the queries that are active in your database. Monitoring these queries can help identify causes of system latency and high CPU usage.

On the Query insights dashboard, you can view a summary of active transactions and a list of transactions with associated query and statistics. The transactions are displayed by the transaction start time. If there is a large number of queries running, then the results might be limited to a subset of total queries.

Before you begin

To monitor active queries, you can use either Cloud SQL Enterprise edition or Cloud SQL Enterprise Plus edition.

To terminate a session or a long-running transaction in active queries, you must use Cloud SQL Enterprise Plus edition for your Cloud SQL for MySQL instance.

For more information about Cloud SQL editions, see Introduction to Cloud SQL editions.

Required roles and permissions

To get the permissions that you need to view active queries, ask your administrator to grant you the following IAM roles on the project that hosts the Cloud SQL instance:

View instance activity summary: Cloud SQL Viewer (roles/cloudsql.viewer)
View database activity summary and long-running transactions: Database Insights Viewer (roles/databaseinsights.viewer)
Terminate a session or long running transaction:
- Cloud SQL Editor (roles/cloudsql.editor)
- Database Insights Operations Admin (roles/databaseinsights.operationsAdmin)

For more information about granting roles, see Manage access to projects, folders, and organizations.

These predefined roles contain the permissions required to view active queries. To see the exact permissions that are required, expand the Required permissions section:

Required permissions

The following permissions are required to view active queries:

View database activity summary and long-running transactions:
- databaseinsights.activeQueries.fetch
- databaseinsights.activitySummary.fetch

You might also be able to get these permissions with custom roles or other predefined roles.

Enable active queries

When you enable query insights, you enable active queries automatically. To be able to terminate a session or long-running transaction in active queries, you must use query insights for Cloud SQL Enterprise Plus edition.

Disable active queries

You can't disable active queries without disabling query insights. To disable active queries and query insights, see Disable query insights.

View active queries

To view your active queries, complete the following steps:

In the Google Cloud console, go to the Cloud SQL Instances page.

Go to Cloud SQL Instances
To open the Overview page of an instance, click the instance name.
Do one of the following to display the Query insights dashboard:
- Select the Query insights tab.
- Click Go to Query insights for more in-depth info on queries and performance. The Query insights dashboard opens. It shows details about the instance at the top.
Click the Active queries tab.

From here, you can modify the query information that appears in the Longest running transactions table:
- Database: filters query load on a specific database or all databases.
- User: filters query load from a specific user account.
- Summary scorecard of all active queries: provides an overview of all the active queries by displaying the total connections based on the following parameters:
  1. Distribution of active connections categorized by connection state.
  2. Distribution of active transactions based on transaction state.
  3. Distribution of query durations.
- Longest running transactions: provides an overview of the top 50 running queries (in the active state) based on descending execution time. You can filter and sort active queries in the table.

View normalized active queries

You can view a list of top long-running transactions with normalized active queries on the Query insights dashboard. A normalized active query removes sensitive data and returns a digest. The digest is the same for different values used in the following example:

Regular queries
- select * from test_table where id=1;
- select * from test_table_where id=2;
Digest or normalized query
- select * from test_table where id=?;

A query that runs in different sessions is displayed as different entries on the dashboard.

View top longest running transactions

The Longest running transactions table on the Query insights dashboard contains the following columns:

Column name Description Process ID Unique identifier of the connection. Query SQL query text. Transaction state The current execution state of the transaction. Permitted values include: RUNNING, LOCK WAIT, ROLLING BACK, and COMMITTING. Thread state Thread state (or query state) indicates the current state of the active thread. Transaction start time The timestamp when the transaction started its execution. Transaction duration The duration of current active transaction in seconds. Transaction wait duration The duration of wait in seconds on current active transaction. Thread state duration Time elapsed in the query. Transaction rows locked Number of rows locked by the current active transaction. Transaction rows modified Number of rows modified by the current active transaction. Database Database name on which this connection is running. User name Name of the user connected to the database. Client address The IP address of client from where a user connects to the database. Action Contains a link for terminating a transaction.

The display is refreshed every 60 seconds automatically.

Note: Data comes from the innodb_trx and processlist tables. Because both tables collect data separately, the transaction state and thread state might be captured at different point in time. Terminate a connection

To terminate a connection or long-running transaction in active queries, you must use Cloud SQL Enterprise Plus edition and enable query insights for Cloud SQL Enterprise Plus edition.

Long running operations can take longer to terminate.

To terminate a query or transaction, complete the following steps:

In the Longest running transaction table, select a query.
In the Action column, click Terminate connection.
In the Terminate connection window, click Confirm.

A database request returns immediately while the termination happens in the background.

The page refreshes after initiating termination. If termination fails, then an error message or notification isn't returned. The query continues showing up in the Active Query list. If termination is successful, then the query no longer displays in the list. If the termination requires a rollback, then the Txn state column shows the ROLLING BACK state, which means that termination is still in progress.

Note: If Terminate isn't available, then you might have insufficient IAM permissions. For more information, see Before you begin. What's next

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-08-14 UTC.

[[["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-14 UTC."],[],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4