Skip to main content
Monitoring of cluster, nodes and MySQL sync databases
Last update:

Monitoring of cluster, nodes and MySQL sync databases

In cloud databases MySQL sync you can monitor the status of the cluster in the control panel:

Cluster and database node metrics can also be export in Prometheus format.

View the status of the node cluster⁠

  1. В control panels go to Cloud platform → Databases.
  2. Open the cluster page → tab Monitoring.
  3. Click Monitoring of cluster servers.
  4. See what's available node cluster metrics.

Cluster node metrics in the control panel⁠

vCPUHow many percent of the node cluster cores are utilized
Load Average

The average system load over a period of time. Shows how many processes are processed by the cluster cores. The indicator is presented in the form of three values — for one minute, five minutes and 15 minutes. These values should not be greater than the number of cores on the node.

MemoryMemory utilization excluding cache and operating system buffers in percent or gigabytes
DiskUsed disk space in percent or gigabytes. The file system reserves 4% of the disk space for service needs, so the space occupied is greater than the actual space used by this 4%

View the status of the databases⁠

  1. В control panels go to Cloud platform → Databases.
  2. Open the cluster page → tab Monitoring.
  3. Click Database monitoring.
  4. See what's available database metrics.

Database metrics in the dashboard⁠

Threads

The number of threads (tracks) inside MySQL:

  • Cached — number of tracks in the cache;
  • Connected — number of open connections;
  • Running — the number of running tracks.
Inquiries

The number of requests of a particular type per second:

  • DELETE;
  • INSERT;
  • SELECT;
  • UPDATE.
Slow queries

The number of slow requests per second. Slow requests are defined by the parameter long_query_time. You can change the value parameter long_query_time

Cache hit

Percentage of requests entering the cache

View cluster status⁠

  1. В control panels go to Cloud platform → Databases.
  2. Look at the status in the cluster row → column Status.
ACTIVEThe cluster is available
CREATINGA cluster is created
UPDATINGChanges are applied to the cluster
RESIZINGThe cluster is scalable
ERRORThere's been a mistake, file a ticket
DISK FULLThe disk is full and the cluster is read-only. To make the cluster read and write, scale the cluster and select a configuration with a larger disk size
DEGRADEDSome nodes in the cluster are unavailable
DELETINGThe cluster is being deleted

Disk fullness notifications⁠

If the cluster disk is 80% full, a notification will automatically be sent to the email address the account is registered to.

If the cluster disk is 95% or more full, the cluster will go into status DISK_FULL and will be read-only. For the cluster to work both read and write, scale the cluster and select a configuration with a larger disk size.

Export metrics in Prometheus format⁠

You can export metrics in the format Prometheus and then independently configure monitoring and alerts for database clusters. Historical information for clusters is not available — metrics are requested only in real time.

To export metrics, you need to get a monitoring token. The token gives access to metrics of all clusters in one project pool.

  1. В control panels go to Cloud platform → Databases.

  2. Open the cluster page → tab Monitoring.

  3. In the block Metrics in Prometheus format click Manage tokens.

  4. Click Create.

  5. Enter the name of the token.

  6. Click Create. The token will be generated automatically.

  7. Add to the Prometheus configuration file:

    scrape_configs:
      - job_name: get-metrics-from-dbaas
        scrape_interval: 1m
        static_configs:
          - targets:
            - '<pool>.dbaas.selcloud.ru'
        scheme: https
        authorization:
          type: Bearer
          credentials: <monitoring_token>

    Specify:

    • <pool> — the pool in which the token operates, e.g. ru-3. The address (URL) depends on the region and pool, you can look in the URL list;
    • <monitoring_token> — monitoring token value.

  8. The source of the metrics will appear at http://<localhost>:9090/targets.

    Specify <localhost> — IP address where Prometheus is installed.

  9. See what's available Prometheus metrics.

Metrics in Prometheus format⁠

Metrics in Prometheus format are provided for all clusters. A specific cluster can be found by the database cluster identifier in the label ds_id.

dbaas_memory_percentMemory utilization excluding cache and operating system buffers (RAM) in percent
dbaas_memory_bytesOccupied memory excluding cache and operating system buffers (RAM) in bytes
dbaas_oom_countNumber of processes that terminated with an Out of Memory error due to lack of RAM
dbaas_cpuPercent vCPU utilization on database cluster nodes
dbaas_cpu_iowaitI/O waiting time in percent
dbaas_disk_percentPercentage of disk space occupied. The file system reserves 4% of disk space for service needs, so the occupied space is larger than the actual space used by this 4%
dbaas_disk_bytesOccupied disk space in bytes. The file system reserves 4% of the disk space for service needs, so the occupied space is larger than the actual space used by this 4%
dbaas_disk_read_iopsNumber of read operations per second
dbaas_disk_write_iopsNumber of recording operations per second
dbaas_disk_read_bytesDisk read speed in bytes per second
dbaas_disk_write_bytesData write speed to disk in bytes per second
dbaas_node_load1The average value of system load in one minute. Shows how many processes are processed by the cluster cores
dbaas_node_load5The average system utilization over five minutes. Shows how many processes are processed by the cluster cores
dbaas_node_load15The average value of system utilization over 15 minutes. Shows how many processes are processed by the cluster cores
dbaas_network_receive_bytesNumber of bytes received through the network interface
dbaas_network_transmit_bytesNumber of bytes sent through the network interface
dbaas_network_receive_packetsNumber of packets received through the network interface per second
dbaas_network_transmit_packetsNumber of packets sent through the network interface per second
dbaas_role

Role of the node:

  • 0 — role unknown;
  • 1 — master;
  • 2 — replica