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, 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 July 2026 are monitored by default using the ServiceWatch service.
    • Existing resources: After the service improvement work in September 2026 We provide monitoring concurrently via Cloud Monitoring and ServiceWatch services.
    • During the parallel operation period, we must prepare for the Servicewatch transition. *
      Performance and log data backup, user-configured settings linked with existing Cloud Monitoring (e.g. 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 (service improvement work in November 2026)
    • 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 개요.

EPAS(DBaaS) Monitoring Metrics

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

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

Performance itemsDetailed descriptionunit
Active Locks [Access Exclusive]Number of Access Exclusive Lockscnt
Active Locks [Access Share]Number of Access Share Lockscnt
Active LocksNumber of Active Lockscnt
Active Locks [Total]Total number of active lockscnt
Active SessionsNumber of Sessions in Active statecnt
Active Sessions [Total]Total number of Sessions in Active statecnt
Apply Lag TimeApply lag timemin
Check No ReplicationCheck No Replication valuecnt
Check ReplicationCheck Replication Status valuestatus
Connection UsageDB connection usage rate (%)%
Connection Usage [Total]DB connection usage rate (%)%
DB Age MaxDatabase age (frozen XID) valueage
Exclusive LocksNumber of Exclusive Lockscnt
Idle In Transaction SessionsNumber of sessions in Idle in transaction statecnt
Idle In Transaction Sessions [Total]Total number of sessions in idle in transaction statecnt
Idle SessionsNumber of idle sessionscnt
Idle Sessions [Total]Total number of idle sessionscnt
Row Exclusive LocksNumber of Row Exclusive Lockscnt
Row Share LocksRow Share Locks countcnt
Share LocksNumber of Share Lockscnt
Share Row Exclusive LocksNumber of Share Row Exclusive Lockscnt
Share Update Exclusive LocksNumber of Share Update Exclusive Lockscnt
SlowqueriesNumber of SQL queries running for a long time (over 5 minutes)cnt
Tablespace UsedTable space sizebytes
Tablespace Used [Total]Table space sizebytes
Tablespace Used Bytes [MB]File system directory usage (MB)MB
Tablespaces [Total]File system directory usage (MB)MB
Transaction Time Max [Long]Long-running Transaction time (minutes)min
Transaction Time Max Total [Long]Long-running Transaction time (minutes)min
Wait LocksNumber of lock-waiting sessions (by DB)cnt
Wait Locks [Long Total]Number of lock-waiting sessions (300 seconds)cnt
Wait Locks [Long]Number of sessions waiting due to a lockcnt
Wait Locks [Total]Total number of sessions waiting due to lock occurrencecnt
Waiting SessionsNumber of Sessions in Waiting statecnt
Waiting Sessions [Total]Total number of Sessions in Waiting statecnt
Table. EPAS (DBaaS) Monitoring Metrics
Server Types
How-to guides