Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Managed Service for MySQL®
  • Getting started
    • All guides
      • Viewing cluster logs
      • Performance diagnostics
      • Monitoring the state of clusters and hosts
      • Connecting from DataLens
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes

In this article:

  • Enabling statistics collection
  • Getting session statistics
  • Getting query statistics
  • Available metrics
  1. Step-by-step guides
  2. Logs and monitoring
  3. Performance diagnostics

Performance diagnostics in Managed Service for MySQL®

Written by
Yandex Cloud
Updated at December 10, 2025
  • Enabling statistics collection
  • Getting session statistics
  • Getting query statistics
    • Available metrics

Managed Service for MySQL® has a built-in tool for collecting session and query statistics. These metrics can be useful when analyzing the cluster’s performance and optimizing its settings.

Enabling statistics collectionEnabling statistics collection

Management console
CLI
Terraform
REST API
gRPC API

When creating a cluster or updating its settings:

  1. Enable Statistics sampling (disabled by default).
  2. Set the Sessions sampling interval and Statements sampling interval. The possible values range from 1 to 86400 seconds.

If you do not have the Yandex Cloud CLI installed yet, install and initialize it.

By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.

To enable and configure statistics collection, provide the --performance-diagnostics parameter in the cluster update command:

yc managed-mysql cluster update <cluster_name_or_ID> \
   ...
   --performance-diagnostics enabled=true,`
                            `sessions-sampling-interval=<session_sampling_interval>,`
                            `statements-sampling-interval=<statement_sampling_interval> \
    ...

For sessions-sampling-interval and statements-sampling-interval, the valid values range from 1 to 86400 seconds.

  1. Open the current Terraform configuration file describing your infrastructure.

    For more information on how to create this file, see this guide.

  2. To enable and configure statistics collection, add the performance_diagnostics section to the cluster configuration:

    resource "yandex_mdb_mysql_cluster" "<cluster_name>" {
      ...
      performance_diagnostics {
        enabled = true
        sessions_sampling_interval = <session_sampling_interval>
        statements_sampling_interval = <statement_sampling_interval>
      }
      ...
    }
    

    For sessions_sampling_interval and statements_sampling_interval, the valid values range from 1 to 86400 seconds.

  3. Make sure the settings are correct.

    1. In the command line, navigate to the directory that contains the current Terraform configuration files defining the infrastructure.

    2. Run this command:

      terraform validate
      

      Terraform will show any errors found in your configuration files.

  4. Confirm updating the resources.

    1. Run this command to view the planned changes:

      terraform plan
      

      If you described the configuration correctly, the terminal will display a list of the resources to update and their parameters. This is a verification step that does not apply changes to your resources.

    2. If everything looks correct, apply the changes:

      1. Run this command:

        terraform apply
        
      2. Confirm updating the resources.

      3. Wait for the operation to complete.

Timeouts

The Terraform provider sets the following timeouts for Managed Service for MySQL® cluster operations:

  • Creating a cluster, including by restoring it from a backup: 15 minutes.
  • Updating a cluster, including the MySQL® version update: 60 minutes.
  • Deleting a cluster: 15 minutes.

Operations exceeding the timeout are aborted.

How do I change these limits?

Add the timeouts section to the cluster description, such as the following:

resource "yandex_mdb_mysql_cluster" "<cluster_name>" {
  ...
  timeouts {
    create = "1h30m" # 1 hour 30 minutes
    update = "2h"    # 2 hours
    delete = "30m"   # 30 minutes
  }
}
  1. Get an IAM token for API authentication and set it as an environment variable:

    export IAM_TOKEN="<IAM_token>"
    
  2. To enable statistics collection when creating a cluster:

    1. Use the Cluster.create method and add the configSpec.performanceDiagnostics parameter to the cURL cluster creation command:

      curl \
          --request POST \
          --header "Authorization: Bearer $IAM_TOKEN" \
          --header "Content-Type: application/json" \
          --url 'https://mdb.api.cloud.yandex.net/managed-mysql/v1/clusters' \
          --data '{
                    "configSpec": {
                      "performanceDiagnostics": {
                        "enabled": <enable_statistics_collection>,
                        "sessionsSamplingInterval": "<session_sampling_interval>",
                        "statementsSamplingInterval": "<statement_sampling_interval>"
                      },
                      ...
                    },
                    ...
                  }'
      

      Where configSpec.performanceDiagnostics is the statistics collection settings:

      • enabled: Enables statistics collection, true or false.
      • sessionsSamplingInterval: Session sampling interval, from 1 to 86400 seconds.
      • statementsSamplingInterval: Statement sampling interval, from 60 to 86400 seconds.
    2. Check the server response to make sure your request was successful.

  3. To enable statistics collection when updating an existing cluster:

    1. Call the Cluster.update method, e.g., via the following cURL request:

      Warning

      The API method will assign default values to all the parameters of the object you are modifying unless you explicitly provide them in your request. To avoid this, list the settings you want to change in the updateMask parameter as a single comma-separated string.

      curl \
          --request PATCH \
          --header "Authorization: Bearer $IAM_TOKEN" \
          --header "Content-Type: application/json" \
          --url 'https://mdb.api.cloud.yandex.net/managed-mysql/v1/clusters/<cluster_ID>' \
          --data '{
                    "updateMask": "configSpec.performanceDiagnostics",
                    "configSpec": {
                      "performanceDiagnostics": {
                        "enabled": <enable_statistics_collection>,
                        "sessionsSamplingInterval": "<session_sampling_interval>",
                        "statementsSamplingInterval": "<statement_sampling_interval>"
                      }
                    }
                  }'
      

      Where configSpec.performanceDiagnostics is the statistics collection settings:

      • enabled: Enables statistics collection, true or false.
      • sessionsSamplingInterval: Session sampling interval, from 1 to 86400 seconds.
      • statementsSamplingInterval: Statement sampling interval, from 60 to 86400 seconds.
    2. Check the server response to make sure your request was successful.

  1. Get an IAM token for API authentication and set it as an environment variable:

    export IAM_TOKEN="<IAM_token>"
    
  2. Clone the cloudapi repository:

    cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi
    

    Below, we assume the repository contents are stored in the ~/cloudapi/ directory.

  3. To enable statistics collection when creating a cluster:

    1. Use the ClusterService/Create method and add the config_spec.performance_diagnostics parameter to the gRPCurl cluster creation command:

      grpcurl \
          -format json \
          -import-path ~/cloudapi/ \
          -import-path ~/cloudapi/third_party/googleapis/ \
          -proto ~/cloudapi/yandex/cloud/mdb/mysql/v1/cluster_service.proto \
          -rpc-header "Authorization: Bearer $IAM_TOKEN" \
          -d '{
                "config_spec": {
                  "performance_diagnostics": {
                    "enabled": <enable_statistics_collection>,
                    "sessions_sampling_interval": "<session_sampling_interval>",
                    "statements_sampling_interval": "<statement_sampling_interval>"
                  },
                  ...
                },
                ...
              }' \
          mdb.api.cloud.yandex.net:443 \
          yandex.cloud.mdb.mysql.v1.ClusterService.Create
      

      Where config_spec.performance_diagnostics is the statistics collection settings:

      • enabled: Enables statistics collection, true or false.
      • sessions_sampling_interval: Session sampling interval, from 1 to 86400 seconds.
      • statements_sampling_interval: Statement sampling interval, from 60 to 86400 seconds.
    2. Check the server response to make sure your request was successful.

  4. To enable statistics collection when updating an existing cluster:

    1. Call the ClusterService/Update method, e.g., via the following gRPCurl request:

      Warning

      The API method will assign default values to all the parameters of the object you are modifying unless you explicitly provide them in your request. To avoid this, list the settings you want to change in the update_mask parameter as an array of paths[] strings.

      Format for listing settings
      "update_mask": {
          "paths": [
              "<setting_1>",
              "<setting_2>",
              ...
              "<setting_N>"
          ]
      }
      
      grpcurl \
          -format json \
          -import-path ~/cloudapi/ \
          -import-path ~/cloudapi/third_party/googleapis/ \
          -proto ~/cloudapi/yandex/cloud/mdb/mysql/v1/cluster_service.proto \
          -rpc-header "Authorization: Bearer $IAM_TOKEN" \
          -d '{
                "cluster_id": "<cluster_ID>",
                "update_mask": {
                  "paths": [
                    "config_spec.performance_diagnostics"
                  ]
                },
                "config_spec": {
                  "performance_diagnostics": {
                    "enabled": <enable_statistics_collection>,
                    "sessions_sampling_interval": "<session_sampling_interval>",
                    "statements_sampling_interval": "<statement_sampling_interval>"
                  }
                }
              }' \
          mdb.api.cloud.yandex.net:443 \
          yandex.cloud.mdb.mysql.v1.ClusterService.Update
      

      Where config_spec.performance_diagnostics is the statistics collection settings:

      • enabled: Enables statistics collection, true or false.
      • sessions_sampling_interval: Session sampling interval, from 1 to 86400 seconds.
      • statements_sampling_interval: Statement sampling interval, from 60 to 86400 seconds.
    2. Check the server response to make sure your request was successful.

Getting session statisticsGetting session statistics

  1. In the management console, navigate to the folder dashboard and select Managed Service for MySQL.

  2. Click the name of your cluster and select Performance diagnostics → Sessions.

    To view session statistics or the history of queries run within a session, select the relevant tab.

    Statistics
    History

    To view session statistics:

    1. Specify the time interval.
    2. Optionally, set filters.
    3. Select the data slice.

    To show or hide individual categories, click the category name in the chart legend.

    To view the history of queries run within a session:

    1. Specify the time interval.
    2. Optionally, set filters.

Getting query statisticsGetting query statistics

  1. In the management console, navigate to the folder dashboard and select Managed Service for MySQL.

  2. Click the name of your cluster and select Performance diagnostics → Queries.

    To view query statistics or compare them across two time intervals, select the relevant tab.

    Interval
    Two intervals

    To view query statistics:

    1. Select the time interval.
    2. Optionally, set filters.

    To get information about the relative changes in query statistics:

    1. In the Interval 1 field, select the time interval whose statistics will serve as the basis for calculations.
    2. In the Interval 2 field, select the time interval whose statistics will be compared with those of the first interval.
    3. Optionally, set filters.

    Let’s assume, 10 SELECT * FROM cities queries were made in the first interval and 20, in the second one. When comparing statistics, the difference in the number of queries (the Calls column in the table) will be +100%.

Available metricsAvailable metrics

This section lists metrics used to collect query statistics and the associated Managed Service for MySQL® metrics in Monitoring.

Statistic metric Monitoring metric Description
Total query latency - Total query execution time
Total lock latency - Total lock wait time
Avg query latency mysql_latency_query_avg
DGAUGE, milliseconds
Average query execution time
Avg lock latency - Average lock wait time
Rows examined - Number of rows read
Calls - Number of database calls
Rows sent - Number of rows returned
Rows affected - Number of rows changed, deleted, added, or returned
Tmp tables mysql_Created_tmp_tables_rate
DGAUGE, tables per second
Rate of temporary tables created during query processing
Tmp disk tables mysql_Created_tmp_disk_tables_rate
DGAUGE, tables per second
Rate of temporary tables created on the disk during query processing
Select full join mysql_Select_full_join_rate
DGAUGE, queries per second
Rate of joins using table scans rather than indexes
Select full range join mysql_Select_full_range_join_rate
DGAUGE, queries per second
Rate of joins searching by range in the reference table
Select range - Number of range selects
Select scan - Number of selects using table scans
Sort merge passes - Number of merge sorts on tables
Sort range mysql_Sort_range_rate
DGAUGE, queries per second
Number of range sorts per unit of time
Sort rows mysql_Sort_rows_rate
DGAUGE, queries per second
Number of rows sorted per unit of time
Sort scan mysql_Sort_scan_rate
DGAUGE, queries per second
Number of sorts using table scans per unit of time
No index used - 1 if no index was used for the table scan, 0 otherwise
No good index used - 1 if no suitable index was found for the query, 0 otherwise
Errors - Number of query execution errors
Warnings - Number of query execution warnings

For more information about the statistics you can get, see this MySQL® article.

Was the article helpful?

Previous
Viewing cluster logs
Next
Monitoring the state of clusters and hosts
© 2025 Direct Cursus Technology L.L.C.