Monitoring Clusters Using Cloud Eye
This section describes metrics reported by GES to Cloud Eye as well as their namespaces, lists, and dimensions. You can use APIs provided by Cloud Eye to query the metric information generated for GES.
Namespace
SYS.GES
Monitoring Metrics
Metric ID |
Metric |
Description |
Value Range |
Monitored Object |
---|---|---|---|---|
ges001_vertex_util |
Vertex Capacity Usage |
Vertex usage in a graph instance. The value is the ratio of used vertices to the total vertices. Unit: % |
0–100 Type: float |
GES instance |
ges002_edge_util |
Edge Capacity Usage |
Edge usage of a graph instance. The value is the ratio of the used edges to the total edges. Unit: % |
0–100 Type: float |
GES instance |
ges003_average_import_rate |
Average Import Rate |
Average rate of importing vertices or edges to a graph instance Unit: count/s |
0–400000 Type: float |
GES instance |
ges004_request_count |
Request Quantity |
Number of requests received by a graph instance Unit: count |
≥ 0 Type: integer |
GES instance |
ges005_average_response_time |
Average Response Time |
Average response time of requests received by a graph instance Unit: ms |
≥ 0 Type: integer |
GES instance |
ges006_min_response_time |
Minimum Response Time |
Minimum response time of requests received by a graph instance Unit: ms |
≥ 0 Type: integer |
GES instance |
ges007_max_response_time |
Maximum Response Time |
Maximum response time of requests received by a graph instance Unit: ms |
≥ 0 Type: integer |
GES instance |
ges008_read_task_pending_queue_size |
Length of the Waiting Queue for Read Tasks |
Length of the waiting queue for read requests received by a graph instance. This metric is used to view the number of read requests waiting in the queue. Unit: count |
≥ 0 Type: integer |
GES instance |
ges009_read_task_pending_max_time |
Maximum Waiting Duration of Read Tasks |
Maximum waiting duration of read requests received by a graph instance Unit: ms |
≥ 0 Type: integer |
GES instance |
ges010_pending_max_time_ read_task_type |
Type of the Read Task That Waits the Longest |
Type of the read request that waits the longest in a graph instance. You can find the corresponding task name in GES documents. |
≥ 1 Type: integer |
GES instance |
ges011_read_task_running_queue_size |
Length of the Running Queue for Read Tasks |
Length of the running queue for read requests received by a graph instance. This metric is used to view the number of running read requests. Unit: count |
≥ 0 Type: integer |
GES instance |
ges012_read_task_running_max_time |
Maximum Running Duration of Read Tasks |
Maximum running duration of read requests received by a graph instance Unit: ms |
≥ 0 Type: integer |
GES instance |
ges013_running_max_time_ read_task_type |
Type of the Read Task That Runs the Longest |
Type of the read request that runs the longest in a graph instance. You can find the corresponding task name in GES documentation. |
≥ 1 Type: integer |
GES instance |
ges014_write_task_pending_queue_size |
Length of the Waiting Queue for Write Tasks |
Length of the waiting queue for write requests received by a graph instance. This metric is used to view the number of write requests waiting in the queue. Unit: count |
≥ 0 Type: integer |
GES instance |
ges015_write_task_pending_max_time |
Maximum Waiting Duration of Write Tasks |
Maximum waiting duration of write requests received by a graph instance Unit: ms |
≥ 0 Type: integer |
GES instance |
ges016_pending_max_time_ write_task_type |
Type of the Write Task That Waits the Longest |
Type of the write request that waits the longest in a graph instance. You can find the corresponding task name in GES documents. |
≥ 1 Type: integer |
GES instance |
ges017_write_task_running_queue_size |
Length of the Running Queue for Write Tasks |
Length of the running queue for write requests received by a graph instance. This metric is used to view the number of running write requests. Unit: count |
≥ 0 Type: integer |
GES instance |
ges018_write_task_running_max_time |
Maximum Running Duration of Write Tasks |
Maximum running duration of write requests received by a graph instance Unit: ms |
≥ 0 Type: integer |
GES instance |
ges019 _running_max_time_ write_task_type |
Type of the Write Task That Runs the Longest |
Type of the write request that runs the longest in a graph instance. You can find the corresponding task name in GES documentation. |
≥ 1 Type: integer |
GES instance |
ges020_computer_resource_usage |
Computing Resource Usage |
Compute resource usage of each graph instance Unit: % |
0–100 Type: float |
GES instance |
ges021_memory_usage |
Memory Usage |
Memory usage of each graph instance Unit: % |
0–100 Type: float |
GES instance |
ges022_iops |
IOPS |
Number of I/O requests processed by each graph instance per second Unit: count/s |
≥ 0 Type: integer |
GES instance |
ges023_bytes_in |
Network Input Throughput |
Data input to each graph instance per second over the network Unit: byte/s |
≥ 0 Type: float |
GES instance |
ges024_bytes_out |
Network Output Throughput |
Data sent to the network per second from each graph instance Unit: byte/s |
≥ 0 Type: float |
GES instance |
ges025_disk_usage |
Disk Usage |
Disk usage of each graph instance Unit: % |
0–100 Type: float |
GES instance |
ges026_disk_total_size |
Total Disk Size |
Total data disk space of each graph instance Unit: GB |
≥ 0 Type: float |
GES instance |
ges027_disk_used_size |
Disk Space Used |
Used data disk space of each graph instance Unit: GB |
≥ 0 Type: float |
GES instance |
ges028_disk_read_throughput |
Disk Read Throughput |
Data volume read from the disk in a graph instance per second Unit: byte/s |
≥ 0 Type: float |
GES instance |
ges029_disk_write_throughput |
Disk Write Throughput |
Data volume written to the disk in a graph instance per second Unit: byte/s |
≥ 0 Type: float |
GES instance |
ges030_avg_disk_sec_per_read |
Average Time per Disk Read |
Average time per disk read for a graph instance Unit: second |
≥ 0 Type: float |
GES instance |
ges031_avg_disk_sec_per_write |
Average Time per Disk Write |
Average time per disk write for a graph instance Unit: second |
≥ 0 Type: float |
GES instance |
ges032_avg_disk_queue_length |
Average Disk Queue Length |
Average I/O queue length of the disk in a graph instance Unit: count |
≥ 0 Type: integer |
GES instance |
Dimensions
Key |
Value |
---|---|
instance_id |
GES instance |
Mapping Between Task Types and Names
Type |
Name |
---|---|
100 |
Querying vertices |
101 |
Creating a vertex |
102 |
Deleting a vertex |
103 |
Modifying a vertex property |
104 |
Adding a vertex label |
105 |
Deleting a vertex label |
200 |
Querying edges |
201 |
Creating an edge |
202 |
Deleting an edge |
203 |
Modifying an edge property |
300 |
Querying schema details |
301 |
Adding a label |
302 |
Modifying a label |
303 |
Querying a label |
304 |
Modifying a property |
400 |
Querying graph details |
401 |
Clearing graphs |
402 |
Incrementally importing graph data online |
403 |
Creating a graph |
405 |
Deleting a graph |
406 |
Exporting graphs |
407 |
filtered_khop |
408 |
Querying path details |
409 |
Incrementally importing graph data offline |
500 |
Creating a graph backup |
501 |
Restoring a graph from a backup |
601 |
Creating an index |
602 |
Querying indexes |
603 |
Updating an index |
604 |
Deleting an index |
700 |
Running an algorithm |
Viewing Instance Monitoring Information
- Log in to the GES management console and choose Graph Management.
- In the graph list, locate the row that contains the target graph, choose More, and select View Metric to access the Cloud Eye management console. By default, the graph instance monitoring information is displayed.
You can select a monitoring metric name and time range to check the performance curve.
Transferring Data to OBS
On Cloud Eye, raw metric data is only stored for two days. However, if you subscribe to OBS, you can synchronize the raw data and extend the storage period.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot