Monitoring metrics
According to the policy of Samsung Cloud Platform, 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 released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Guide to Applying Monitoring Service by Resource
- New Resources: Resources created after the service improvement work in March 2026 are provided with monitoring using the ServiceWatch service as the default.
- Existing resources: After the service improvement work in July 2026 We provide concurrent monitoring through Cloud Monitoring and ServiceWatch services
- During the parallel operation period, you must prepare for the Servicewatch transition. *
Performance and log data backup, the settings configured by users integrated with existing Cloud Monitoring (ex. You must verify the event policies, etc., perform tasks such as resetting the ServiceWatch service, and then complete them.
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.
- Console menu termination (September 2026 service improvement work)
| Region | Cloud Monitoring console URL |
|---|---|
| kr-west1 | https://console.kr-west1.e.samsungsdscloud.com/console/monitoring |
| kr-east1 | https://console.kr-east1.e.samsungsdscloud.com/console/monitoring |
- Service termination (service improvement work in November 2026)
- All Cloud Monitoring services, 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 transition work within the parallel operation period.
- All Cloud Monitoring services, including the API, will be permanently discontinued.
Detailed information about ServiceWatch can be found in 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 usage of Cloud Monitoring, refer to the Cloud Monitoring guide.
For MySQL (DBaaS) server monitoring metrics, refer to the Virtual Server monitoring metrics guide.
| Performance items | Detailed description | unit |
|---|---|---|
| Active Locks | Number of Active Locks | cnt |
| Active Sessions | Number of Active Sessions | cnt |
| Binary Log Used [MB] | binary log usage | MB |
| Connection Usage [Total] | Database connection session utilization | % |
| Connections | Number of connections | cnt |
| Connections [MAX] | Number of connections | cnt |
| Connections | max connected threads count | cnt |
| Data Directory Used [MB] | data directory usage | MB |
| Instance Status [PID] | mysqld process pid | pid |
| Open Files | Number of DB files in open state | cnt |
| Open Files [MAX] | Number of DB files that can be opened | cnt |
| Open Files Usage | DB file maximum count usage rate | % |
| Relay Log Used [MB] | Relay log usage (MB) | MB |
| Running Threads | running thread count | cnt |
| Safe PID | safe program pid | pid |
| Slave Behind Master seconds | Time difference with the master node | sec |
| Slowqueries | Number of SQL queries running for a long time (over 5 minutes) (by DB) | cnt |
| Slowqueries [Total] | Number of SQL queries running for a long time (over 5 minutes) (total) | cnt |
| Tablespace Used | Tablespace usage | MB |
| Tablespace Used [Total] | Total tablespace usage | MB |
| Transaction Time [Long] | Maximum transaction execution time | sec |
| Wait Locks | Number of sessions blocked for more than 60 seconds by lock | cnt |