The page has been translated by Gen AI.

Monitoring metrics

Cloud Monitoring Service Termination Notice

According to Samsung Cloud Platform’s policy, the Cloud Monitoring service is scheduled to be discontinued.

Accordingly, services whose monitoring metrics are linked in Cloud Monitoring will no longer be able to monitor resources through Cloud Monitoring after the service improvement work in November 2026.
After that, resource monitoring can be continuously performed through the ServiceWatch service, which was released in October 2025.

To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.

  1. Guide to Applying Monitoring Services by Resource

    • New Resources: Resources created after the service improvement work in March 2026 are monitored by default using the ServiceWatch service.
    • Existing resources: After the service improvement work in September 2026 We provide monitoring in parallel using the Cloud Monitoring service and the ServiceWatch service.
    • During the parallel operation period, we must prepare for the Servicewatch transition. *
      Performance and log data backup, user-configured settings integrated with existing Cloud Monitoring (e. You need to verify the event policies, etc., perform tasks such as resetting the ServiceWatch service, and complete the process.
  2. Cloud Monitoring Service Phased Termination Schedule Notice

    • Console menu termination (September 2026 service improvement work)
      • You cannot access the Cloud Monitoring Console through the Console menu; you can only connect via the separate URLs for each region listed below.
  • Service termination (service improvement work in November 2026)
    • All services of Cloud Monitoring, including the API, will be permanently discontinued.
      • After the service ends in November, you will not be able to view Cloud Monitoring data. * Be sure to complete the ServiceWatch migration within the parallel operation period**.

Detailed information about ServiceWatch: see the ServiceWatch 개요.

MySQL(DBaaS) Monitoring Metrics

The table below shows the performance monitoring metrics for MySQL (DBaaS) that can be viewed through Cloud Monitoring. For detailed Cloud Monitoring usage, refer to the Cloud Monitoring guide.

For MySQL (DBaaS) server monitoring metrics, please refer to the Virtual Server Monitoring Metrics guide.

Performance itemsDetailed descriptionunit
Active LocksNumber of Active Lockscnt
Active SessionsNumber of Active Sessionscnt
Binary Log Used [MB]binary log usageMB
Connection Usage [Total]DB connection session usage%
ConnectionsNumber of connectionscnt
Connections [MAX]Connection countcnt
Connectionsmax connected threads countcnt
Data Directory Used [MB]data directory usageMB
Instance Status [PID]mysqld process pidpid
Open FilesNumber of open DB filescnt
Open Files [MAX]Number of DB files that can be openedcnt
Open Files UsageDB file maximum count usage rate%
Relay Log Used [MB]relay log usage (MB)MB
Running Threadsrunning thread countcnt
Safe PIDsafe program pidpid
Slave Behind Master secondsTime difference with the master nodesec
SlowqueriesNumber of SQL queries running for a long time (over 5 minutes) (by DB)cnt
Slowqueries [Total]Number of long-running (over 5 minutes) SQL queries (total)cnt
Tablespace UsedTablespace usageMB
Tablespace Used [Total]Total tablespace usageMB
Transaction Time [Long]Maximum transaction execution timesec
Wait LocksNumber of sessions blocked for more than 60 seconds by lockcnt
Table. MySQL(DBaaS) Monitoring Metrics
Server Types
ServiceWatch Metrics