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 terminated.

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 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 Service 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 concurrent monitoring through Cloud Monitoring and ServiceWatch services.
    • During the parallel operation period, we must prepare for the Servicewatch transition. *
      Performance and log data backup, settings configured by users linked with existing Cloud Monitoring (ex. You need to review the event policies, etc., perform tasks such as resetting the ServiceWatch service, and complete them.
  2. Notice of the phased termination schedule for the Cloud Monitoring service

    • 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 (November 2026 service improvement work)
  * All services of Cloud Monitoring, including the API, will be permanently discontinued.
	  * **After the service ends in November, Cloud Monitoring data cannot be accessed.**     	  * Be sure to complete the ServiceWatch migration within the parallel operation period**.

Detailed information about ServiceWatch can be found in the ServiceWatch Overview.

MariaDB(DBaaS) Monitoring Metrics

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

The server monitoring metrics for MariaDB (DBaaS) can be found in the Virtual Server Monitoring Metrics guide.

Performance itemsDetailed descriptionunit
Active LocksNumber of Active Lockscnt
Active SessionsNumber of Active Sessionscnt
Connection Usage [Total]DB connection session usage rate%
ConnectionsNumber of connectionscnt
Connections [MAX]max connected threads countcnt
Binary Log Used [MB]binary log usageMB
Data Directory Used [MB]data directory usageMB
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 usageMB
Instance Status [PID]mariadbd processpid
Safe PIDmariadbd_safe processpid
Slave Behind Master secondsData time difference between Master and Slave (run only on slave)sec
Tablespace UsedTablespace usageMB
Tablespace Used [Total]Total tablespace usageMB
Running Threadsrunning thread countcnt
SlowqueriesNumber of SQL queries running for a long time (over 5 minutes) (by DB)cnt
Slowqueries [Total]Number of long-running (5 minutes or more) SQL queries (total)cnt
Transaction Time [Long]Maximum transaction execution timesec
Wait LocksNumber of sessions blocked for more than 60 seconds by lockcnt
Table. MariaDB(DBaaS) Monitoring Metrics
Server Types
ServiceWatch Metrics