Monitoring metrics
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.
Notice of Monitoring Service Application per 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 the Cloud Monitoring service and the ServiceWatch service.
- During the parallel operation period, you must prepare for the Servicewatch transition *
Performance and log data backup, the settings configured by the user integrated with existing Cloud Monitoring (ex. 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 |
- Service termination (service improvement work in November 2026)
- All Cloud Monitoring services, including the API, will be permanently discontinued.
- After the service ends in November, you cannot view Cloud Monitoring data. * Be sure to complete the ServiceWatch migration within the parallel operation period**.
- All Cloud Monitoring services, including the API, will be permanently discontinued.
Detailed information about ServiceWatch can be found in the ServiceWatch 개요.
Search Engine Monitoring Metrics
The table below shows the performance monitoring metrics for Event Streams that can be viewed through Cloud Monitoring. For detailed usage of Cloud Monitoring, refer to the Cloud Monitoring guide.
For the Search Engine’s server monitoring metrics, refer to the Virtual Server Monitoring Metrics guide.
| 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] | Maximum JVM heap (bytes) | bytes |
| JVM Non Heap Used [Init] | init (bytes) other than 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 repository size (bytes) | bytes |