Monitoring Metrics
In accordance with the Samsung Cloud Platform policy, the Cloud Monitoring service is scheduled to be discontinued.
As a result, services whose monitoring metrics are integrated with Cloud Monitoring will no longer support resource monitoring through Cloud Monitoring after the service improvement work in November 2026.
You can continue to monitor resources through the ServiceWatch service, released in October 2025.
To ensure a smooth service experience, complete the migration in accordance with the service end schedule below.
Guide to Applying Monitoring Services by Resource
- New resources: Resources created after the service improvement work in March 2026 provide monitoring by default using the ServiceWatch service.
- Existing resources: After the service improvement work in July 2026, monitoring will be provided concurrently through both the Cloud Monitoring service and the ServiceWatch service.
- You must prepare for the Servicewatch transition during the parallel operation period. *
Back up performance and log data, and preserve user-configured settings integrated with the existing Cloud Monitoring (e.g., Review the event policies and other settings, and then perform tasks such as resetting the ServiceWatch service to complete the process.
Notice of the Phased Deprecation 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 and can only connect via the separate region-specific URLs below.
- Console menu termination (September 2026 service improvement work)
| Legion | 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 Discontinuation (Service Improvement Work in November 2026)
- All Cloud Monitoring services, including the API, will be permanently shut down.
- **After the service ends in November, you can no longer query Cloud Monitoring data. * Complete the ServiceWatch migration within the mandatory parallel operation period.
- All Cloud Monitoring services, including the API, will be permanently shut down.
For more information about ServiceWatch, see ServiceWatch Overview.
MariaDB (DBaaS) Monitoring Metrics
The following table shows the performance monitoring metrics for MariaDB (DBaaS) that you can view through Cloud Monitoring. For detailed information on how to use Cloud Monitoring, refer to the Cloud Monitoring guide.
For server monitoring metrics for MariaDB (DBaaS), refer to the Virtual Server monitoring metrics guide.
| Performance Item | Detailed Description | Unit |
|---|---|---|
| Active Locks | Number of Active Locks | cnt |
| Active Sessions | Number of Active Sessions | cnt |
| Connection Usage [Total] | DB Connection Session Usage | % |
| Connections | Number of connections | cnt |
| Connections [MAX] | Maximum number of connected threads | cnt |
| Binary Log Used [MB] | Binary log usage | MB |
| Data Directory Used [MB] | Data directory usage | MB |
| Open Files | Number of open DB files | cnt |
| Open Files [MAX] | Number of openable DB files | cnt |
| Open Files Usage | DB file maximum count usage | % |
| Relay Log Used [MB] | Relay log usage | MB |
| Instance Status [PID] | mariadbd process | pid |
| Safe PID | mariadbd_safe process | pid |
| Slave Behind Master seconds | Time difference in data between the Master and Slave (run on the Slave only) | sec |
| Tablespace Used | Tablespace Usage | MB |
| Tablespace Used [Total] | Total Tablespace Usage | MB |
| Running Threads | Number of running threads | cnt |
| Slowqueries | Number of SQL queries running for an extended period (5 minutes or more) (by DB) | cnt |
| Slowqueries [Total] | Number of SQL queries running for an extended period (5 minutes or more) (total) | cnt |
| Transaction Time [Long] | Maximum transaction execution time | sec |
| Wait Locks | Number of sessions blocked for more than 60 seconds by a lock | cnt |