Monitoring metrics
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 released in October 2025.
To ensure smooth service usage, proceed with the migration work according to the service termination schedule below.
Notice on Applying Monitoring Service 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 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 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.
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.
- Console menu termination (September 2026 service improvement work)
| Offering | Region | Cloud Monitoring console URL |
|---|---|---|
| Enterprise | kr-west1 | https://console.kr-west1.e.samsungsdscloud.com/console/monitoring |
| Enterprise | kr-east1 | https://console.kr-east1.e.samsungsdscloud.com/console/monitoring |
| Samsung | kr-west1 | https://console.kr-west1.s.samsungsdscloud.com/console/monitoring |
| Samsung | kr-east1 | https://console.kr-east1.s.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south1 | https://console.kr-south1.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south2 | https://console.kr-south2.g.samsungsdscloud.com/console/monitoring |
| Sovereign | kr-south3 | https://console.kr-south3.g.samsungscloud.com/console/monitoring |
- 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**.
- All services of Cloud Monitoring, including the API, will be permanently discontinued.
Detailed information about ServiceWatch is available in the ServiceWatch Overview.
Search Engine Monitoring Metrics
The table below shows the performance monitoring metrics for Event Streams that can be viewed through Cloud Monitoring. For detailed Cloud Monitoring usage, refer to the Cloud Monitoring guide.
Refer to the Virtual Server Monitoring Metrics guide for the Search Engine server monitoring metrics.
| Performance items | Detailed description | unit |
|---|---|---|
| Disk Usage | datadir usage | MB |
| Documents [Deleted] | Total number of deleted documents | cnt |
| Documents [Existing] | Total number of existing documents | cnt |
| Filesystem Bytes [Available] | Available file systems | bytes |
| Filesystem Bytes [Free] | Available file system | bytes |
| Filesystem Bytes [Total] | Total file system | bytes |
| Instance Status [PID] | Elasticsearch process PID | PID |
| JVM Heap Used [Init] | Heap init used by JVM (bytes) | bytes |
| JVM Heap Used [MAX] | Heap max used by JVM (bytes) | bytes |
| JVM Non Heap Used [Init] | init (bytes) outside the heap used by the JVM | bytes |
| JVM Non Heap Used [MAX] | max (bytes) other than the heap used by the JVM | bytes |
| Kibana Connections | Kibana connection | cnt |
| Kibana Memory Heap Allocated [Limit] | Maximum heap size allocated to a Node.js process (bytes) | bytes |
| Kibana Memory Heap Allocated [Total] | Maximum heap size allocated to a Node.js process (bytes) | bytes |
| Kibana Memory Heap Used | Maximum heap size allocated to a Node.js process (bytes) | bytes |
| Kibana Process Uptime | Kibana process | ms |
| Kibana Requests [Disconnected] | Request count metric | cnt |
| Kibana Requests [Total] | Request count metric | cnt |
| Kibana Response Time [Avg] | Response time metric | ms |
| Kibana Response Time [MAX] | Response time metric | ms |
| Kibana Status [PID] | Kibana process PID | PID |
| License Expiry Date [ms] | License expiration date [milisecond] | ms |
| License Status | License status | status |
| License Type | License type | type |
| Queue Time | Queue time | ms |
| Segments | Total number of segments | cnt |
| Segments Bytes | Total segment size (bytes) | bytes |
| Shards | Cluster shard count | cnt |
| Store Bytes | Total storage size (bytes) | bytes |