The page has been translated by Gen AI.

Monitoring metrics

Cloud Monitoring 서비스 종료 안내

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.

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

  1. Guide to Applying Resource-Specific Monitoring Service

    • New resources: Resources created after the March 2026 service improvement work are provided with monitoring using the ServiceWatch service by default.
    • Existing resources: After the service improvement work in July 2026 We provide concurrent monitoring via Cloud Monitoring service and ServiceWatch service.
    • During the parallel operation period, you must prepare for the Servicewatch transition. *
      Performance and log data backup, the settings configured by users linked with existing Cloud Monitoring (e.g. You must check the event policies, etc., and perform tasks such as resetting the ServiceWatch service, then complete them.
  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. * Make sure to complete the ServiceWatch migration within the parallel operation period**.

For more details about ServiceWatch, see the ServiceWatch 개요.

MariaDB(DBaaS) Monitoring Metrics

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

For MariaDB (DBaaS) server monitoring metrics, see the Virtual Server 모니터링 지표 guide.

Performance itemsDetailed descriptionunit
Active LocksNumber of Active Lockscnt
Active SessionsNumber of Active Sessionscnt
Connection Usage [Total]DB connection session usage rate%
ConnectionsConnection countcnt
Connections [MAX]max connected threads countcnt
Binary Log Used [MB]binary log usageMB
Data Directory Used [MB]data directory usageMB
Open FilesNumber of DB files in open statecnt
Open Files [MAX]Number of DB files that can be openedcnt
Open Files UsageMaximum utilization rate of DB files%
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 (execute on slave only)sec
Tablespace UsedTablespace usageMB
Tablespace Used [Total]Total tablespace usageMB
Running Threadsrunning thread countcnt
SlowqueriesNumber of long-running (over 5 minutes) SQL queries (by DB)cnt
Slowqueries [Total]Number of SQL queries running for a long time (over 5 minutes) (total)cnt
Transaction Time [Long]Maximum transaction execution timesec
Wait LocksNumber of sessions blocked for 60 seconds or more due to lockcnt
Table. MariaDB(DBaaS) Monitoring Metrics
Server type
ServiceWatch metric