The page has been translated by Gen AI.
Monitoring metrics
Cloud Monitoring Service Termination Notice
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 July 2026 are provided with monitoring using the ServiceWatch service by default.
- Existing resources: After the service improvement work in September 2026, we provide monitoring in parallel using Cloud Monitoring and ServiceWatch services.
- During the parallel operation period, we must prepare for the Servicewatch transition *
Performance and log data backup, the user-configured settings linked with existing Cloud Monitoring (e.g. Check the event policies, etc., and perform tasks such as resetting the ServiceWatch service, 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 |
Table. Cloud Monitoring console URLs by region
- Service termination (November 2026 service improvement work)
- All Cloud Monitoring services, including the API, are being permanently terminated.
- After the service ends in November, Cloud Monitoring data cannot be viewed. * Be sure to complete the ServiceWatch migration within the parallel operation period**.
- All Cloud Monitoring services, including the API, are being permanently terminated.
Detailed information about ServiceWatch can be found in the ServiceWatch 개요.
CacheStore(DBaaS) Monitoring Metrics
The table below shows the performance monitoring metrics for CacheStore (DBaaS) that can be viewed through Cloud Monitoring. For detailed usage of Cloud Monitoring, refer to the Cloud Monitoring guide.
For CacheStore (DBaaS) server monitoring metrics, refer to the Virtual Server Monitoring Metrics guide.
| Performance items | Detailed description | unit |
|---|---|---|
| Active Defragmentation Keys [Hits] | Number of keys after defragmentation | cnt |
| Active Defragmentation Keys [Miss] | Number of keys skipped in the active defragmentation removal process | cnt |
| Active Defragmentationd [Hits] | Number of value reallocations performed by the active defragmentation process | cnt |
| Active Defragmentations [Miss] | Count of value reallocations interrupted by the active defragmentation removal process | cnt |
| Allocated Bytes [OS] | Number of bytes allocated by CacheStore (DBaaS) and recognized by the operating system (resident set size) | bytes |
| Allocated Bytes [Redis] | Total bytes allocated by CacheStore (DBaaS) | bytes |
| AOF Buffer Size | AOF buffer size | bytes |
| AOF File Size [Current] | AOF current file size | bytes |
| AOF File Size [Lastest Startup] | AOF file size on recent startup or rewrite | bytes |
| AOF Rewrite Buffer Size | AOF rewrite buffer size | bytes |
| AOF Rewrite Current Time | Time of the ongoing AOF rewrite operation when applicable | sec |
| AOF Rewrite Last Time | Final AOF rewrite operation time | sec |
| Calls | Number of calls that reached command execution (not rejected) | cnt |
| Changes [Last Saved] | Number of changes after the final dump | cnt |
| Client Output Buffer [MAX] | Longest output list among current client connections | cnt |
| Clients [Sentinel] | Number of client connections (Sentinel) | cnt |
| Connected Slaves | Number of connected slaves | cnt |
| Connections [Blocked] | Number of clients pending blocking calls (BLPOP, BRPOP, BRPOPLPUSH) | cnt |
| Connections [Current] | Number of client connections (excluding slave connections) | cnt |
| Copy On Write Allocated Size [AOF] | COW allocation size during final RBD save operation | bytes |
| Copy On Write Allocated Size [RDB] | COW allocation size during final RBD save operation | bytes |
| CPU Time [Average] | Average CPU time used per command execution | cnt |
| CPU Time [Total] | Total CPU time used by these commands | usec |
| CPU Usage [System Process] | System CPU usage used by background processes | % |
| CPU Usage [System] | System CPU usage on the CacheStore (DBaaS) server | % |
| CPU Usage [User Process] | User CPU usage used by background processes | % |
| CPU Usage [User] | System CPU usage used by background processes | % |
| Dataset Used | Dataset size | bytes |
| Disk Used | datadir usage | MB |
| Evicted Keys | Number of evicted keys caused by the maxmemory limit | cnt |
| Fsyncs [Delayed] | Delayed fsync counter | cnt |
| Fsyncs [Pending] | Number of pending fsync operations in the background I/O queue | cnt |
| Full Resyncs | Number of full resynchronizations with the slave | cnt |
| Keys [Expired] | Total number of key expiration events | cnt |
| Keys [Keyspace] | Number of keys in the key space | cnt |
| Lastest Fork Duration Time | Recent fork operation time | usec |
| Lookup Keys [Hit] | Number of successful key lookups in the dictionary | cnt |
| Lookup Keys [Miss] | Number of failed key lookups in the main dictionary | cnt |
| Lua Engine Memory Used | Memory used by the Lua engine | bytes |
| Master Last Interaction Time Ago | Time elapsed since the final interaction with the master | sec |
| Master Last Interaction Time Ago [Sync] | Time elapsed since the final interaction with the master | sec |
| Master Offset | Current replication offset of the server | pid |
| Master Second Offset | Offset until the replica ID is accepted | pid |
| Master Sync Left Bytes | Remaining bytes before synchronization completes | bytes |
| Memory Fragmentation Rate | used_memory_rss and used_memory ratio | % |
| Memory Fragmentation Rate [Allocator] | Fragmentation ratio | % |
| Memory Fragmentation Used | bytes between used_memory_rss and used_memory | bytes |
| Memory Fragmentation Used [Allocator] | Resident byte | bytes |
| Memory Max Value | Memory limit | bytes |
| Memory Resident [Allocator] | resident memory | bytes |
| Memory RSS Rate [Allocator] | Resident ratio | % |
| Memory Used [Active] | Active memory | bytes |
| Memory Used [Allocated] | Allocated memory | bytes |
| Memory Used [Resident] | Resident byte | bytes |
| Network In Bytes [Total] | Total network input (bytes) | bytes |
| Network Out Bytes [Total] | Total network output (bytes) | bytes |
| Network Read Rate | Network read speed (KB/sec) | cnt |
| Network Write Rate | Network write speed (KB/sec) | cnt |
| Partial Resync Requests [Accepted] | Number of accepted partial resynchronization requests | cnt |
| Partial Resync Requests [Denied] | Number of rejected partial resynchronization requests | cnt |
| Peak Memory Consumed | Maximum memory used by CacheStore (DBaaS) | bytes |
| Processed Commands | Number of commands processed per second | cnt |
| Processed Commands [Total] | Total number of processed commands | cnt |
| Pub/Sub Channels | Global number of publish/subscribe channels with client subscriptions | cnt |
| Pub/Sub Patterns | Global count of publish/subscribe pattern with client subscriptions | cnt |
| RDB Saved Duration Time [Current] | Time of the ongoing RDB save operation if applicable | sec |
| RDB Saved Duration Time [Last] | Final RDB save operation time | sec |
| Received Connections [Total] | Total number of received connections | cnt |
| Rejected Connections [Total] | Total number of rejected connections | cnt |
| Replication Backlog Actove Count | Replication backlog enable flag | cnt |
| Replication Backlog Master Offset | Master offset of the replication backlog buffer | cnt |
| Replication Backlog Size | Data size of the replication backlog buffer | bytes |
| Replication Backlog Size [Total] | Total size of the replication backlog buffer | bytes |
| Slave Priority | Server priority as a fault remediation target | cnt |
| Slave Replication Offset | Replication offset of the slave server | pid |
| Slow Operations | Number of slow tasks | cnt |
| Sockets [MIGRATE] | Number of sockets opened for migration | cnt |
| Tracked Keys [Expiry] | Number of keys tracked for expiration (applicable only to writable slaves) | cnt |
| Instance Status [PID] | redis-server process PID | pid |
| Sentinel Status [PID] | sentinel process PID | pid |
Table. CacheStore (DBaaS) Monitoring Metrics