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 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 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 concurrent monitoring through 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 integrated with existing Cloud Monitoring (e. You need to review the event policies, etc., perform tasks such as resetting the ServiceWatch service, and 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, 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 개요.

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 itemsDetailed descriptionunit
Active Defragmentation Keys [Hits]Number of keys after defragmentationcnt
Active Defragmentation Keys [Miss]Number of keys skipped in the active defragmentation removal processcnt
Active Defragmentationd [Hits]Number of value reallocations performed by the active defragmentation removal processcnt
Active Defragmentations [Miss]Count of value reallocations interrupted by the active defragmentation removal processcnt
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 SizeAOF buffer sizebytes
AOF File Size [Current]AOF current file sizebytes
AOF File Size [Lastest Startup]AOF file size on recent start or rewritebytes
AOF Rewrite Buffer SizeAOF rewrite buffer sizebytes
AOF Rewrite Current TimeIf applicable, the time of the ongoing AOF rewrite operationsec
AOF Rewrite Last TimeFinal AOF rewrite timesec
CallsNumber of calls that reached command execution (not rejected)cnt
Changes [Last Saved]Number of changes after the final dumpcnt
Client Output Buffer [MAX]Longest output list among current client connectionscnt
Clients [Sentinel]Number of client connections (Sentinel)cnt
Connected SlavesNumber of connected slavescnt
Connections [Blocked]Number of clients pending on 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 operationbytes
Copy On Write Allocated Size [RDB]COW allocation size during the final RBD save operationbytes
CPU Time [Average]Average CPU time used per command executioncnt
CPU Time [Total]Total CPU time used by these commandsusec
CPU Usage [System Process]System CPU usage 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 by background processes%
Dataset UsedDataset sizebytes
Disk Useddatadir usageMB
Evicted KeysNumber of evicted keys caused by the maxmemory limitcnt
Fsyncs [Delayed]Delayed fsync countercnt
Fsyncs [Pending]Number of pending fsync operations in the background I/O queuecnt
Full ResyncsNumber of full resynchronizations with the slavecnt
Keys [Expired]Total number of key expiration eventscnt
Keys [Keyspace]Number of keys in the key spacecnt
Lastest Fork Duration TimeRecent fork (fork) operation timeusec
Lookup Keys [Hit]Number of successful key lookups in the dictionarycnt
Lookup Keys [Miss]Number of failed key lookups in the main dictionarycnt
Lua Engine Memory UsedMemory used by the Lua enginebytes
Master Last Interaction Time AgoTime elapsed since the final interaction with the mastersec
Master Last Interaction Time Ago [Sync]Time elapsed since the final interaction with the mastersec
Master OffsetCurrent replication offset of the serverpid
Master Second OffsetOffset until the replication ID is acceptedpid
Master Sync Left BytesRemaining bytes before synchronization completesbytes
Memory Fragmentation RateRatio of used_memory_rss to used_memory%
Memory Fragmentation Rate [Allocator]Fragmentation ratio%
Memory Fragmentation UsedBytes between used_memory_rss and used_memorybytes
Memory Fragmentation Used [Allocator]resident bytebytes
Memory Max ValueMemory limitbytes
Memory Resident [Allocator]resident memorybytes
Memory RSS Rate [Allocator]Resident ratio%
Memory Used [Active]Active memorybytes
Memory Used [Allocated]Allocated memorybytes
Memory Used [Resident]Resident bytebytes
Network In Bytes [Total]Total network input (bytes)bytes
Network Out Bytes [Total]Total network output (bytes)bytes
Network Read RateNetwork read speed (KB/sec)cnt
Network Write RateNetwork write speed (KB/sec)cnt
Partial Resync Requests [Accepted]Number of accepted partial resynchronization requestscnt
Partial Resync Requests [Denied]Number of rejected partial resynchronization requestscnt
Peak Memory ConsumedMaximum memory used by CacheStore (DBaaS)bytes
Processed CommandsNumber of commands processed per secondcnt
Processed Commands [Total]Total number of processed commandscnt
Pub/Sub ChannelsGlobal count of pub/sub channels with client subscriptionscnt
Pub/Sub PatternsGlobal count of publish/subscribe patterns with client subscriptionscnt
RDB Saved Duration Time [Current]If applicable, the time of the ongoing RDB save operationsec
RDB Saved Duration Time [Last]Final RDB save operation timesec
Received Connections [Total]Total number of received connectionscnt
Rejected Connections [Total]Total number of rejected connectionscnt
Replication Backlog Actove CountReplication backlog activation flagcnt
Replication Backlog Master OffsetMaster offset of the replication backlog buffercnt
Replication Backlog SizeData size of the replication backlog bufferbytes
Replication Backlog Size [Total]Total size of the replication backlog bufferbytes
Slave PriorityServer priority as a fault remediation targetcnt
Slave Replication OffsetReplication offset of the slave serverpid
Slow OperationsNumber of slow taskscnt
Sockets [MIGRATE]Number of sockets opened for migrationcnt
Tracked Keys [Expiry]Number of keys tracked for expiration (applicable only to writable slaves)cnt
Instance Status [PID]redis-server process PIDpid
Sentinel Status [PID]sentinel process PIDpid
Table. CacheStore (DBaaS) Monitoring Metrics
Server Types
How-to guides