You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: deploy-manage/monitor/autoops/ec-autoops-nodes-view.md
+24-24Lines changed: 24 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,40 +37,40 @@ The **Open Events** panel lists open events sorted by severity and time. When th
37
37
38
38
The following table lists all the other panels in the **Nodes** view that drill down into specific monitoring areas, along with the names and descriptions of metrics they present.
39
39
40
-
| Area |Metrics name |Metrics description |
40
+
| Area |Metric name |Metric description |
41
41
| --- | --- | --- |
42
42
| Activity | Indexing rate | Number of documents being indexed per second on all primary and replica shards hosted on the node. |
43
43
|| Indexing latency | Average latency for indexing documents, which is the time it takes to index documents divided by the number that were indexed in all primary and replica shards hosted on the node. |
44
44
|| Search rate | Number of search requests being executed per second on all shards hosted on the node. |
45
45
|| Search latency | Average latency for searching, which is the time it takes to execute searches divided by the number of searches submitted to the node. |
46
-
| Host and Process | Load | Load average of the node over the last five minutes. |
46
+
| Host and Process | Load | Load average over the last five minutes depicting how many tasks have been waiting for CPU, or are blocked on I/O. <br> Comparing the load value to the number of CPU cores on the node helps to understand whether the system has spare capacity (load < # cores), is saturated (load = # cores), or is overloaded (load > # cores). |
47
47
|| CPU | Percentage of the CPU usage for the {{es}} process running on the node. |
48
48
|| Heap used in bytes | Total JVM heap memory used by the {{es}} process running on the node. |
49
-
|| GC | Average time spent doing GC in milliseconds on the node. |
50
-
| Thread pools | Write | Number of index, bulk and write operations in the queue, as well as the total number of completed and rejected operations in those pools. |
51
-
|| Search | Number of search operations in the queue, as well as the total number of completed and rejected operations in that pool. |
52
-
|| Management | Number of management operations in the queue, as well as the total number of completed and rejected operations in that pool. |
53
-
| | Snapshot | Number of snapshot operations in the queue, as well as the total number of completed and rejected operations in that pool.
49
+
|| GC | Average time spent doing GC on the node in milliseconds. |
50
+
| Thread pools | Write | Number of single-document index/delete/update, ingest processors, and bulk operations in the queue, as well as the total number of completed and rejected operations in that pool. |
51
+
|| Search | Number of search, count, and fetch operations in the queue, as well as the total number of completed and rejected operations in that pool. |
52
+
|| Management | Number of cluster management operations in the queue, as well as the total number of completed and rejected operations in that pool. |
53
+
|| Snapshot | Number of snapshot and restore operations in the queue, as well as the total number of completed and rejected operations in that pool. |
54
54
| Data | Disk usage | Amount of used disk storage on the node. |
55
-
|| Shards count |Number of primary and replica shards hosted on the node. |
56
-
|| Segment count |Number of segments hosted on the node. |
55
+
|| Shards count |Total number of primary and replica shards allocated to the node. |
56
+
|| Segment count |Total number of segments (i.e., the Lucene low-level inverted indices composing an {{es}} index) hosted on the node. |
57
57
|| Documents count | Number of documents hosted on the node. |
58
-
| HTTP | HTTP current open | Current number of open HTTP connections for the node. |
58
+
| HTTP | HTTP current open | Current number of HTTP connections opened on the node. |
59
59
|| HTTP connections open rate | Number of HTTP connections opened per second. |
60
-
| Circuit breakers | Parent Used |Estimated memory used for the parent circuit breaker. |
61
-
|| Field Data used |Estimated memory used for the field data circuit breaker. |
62
-
|| Request used |Estimated memory used for the request circuit breaker. |
63
-
|| Parent tripped | Total number of times the parent circuit breaker has been triggered and prevented an out-of-memory error. |
64
-
|| Field data tripped | Total number of times the field data circuit breaker has been triggered and prevented an-out-ofmemory error. |
65
-
|| Request tripped | Total number of times the request circuit breaker has been triggered and prevented an out-of-memory error. |
66
-
| Network | Network rx bytes | Size of RX packets received by the node during internal cluster communication. |
67
-
|| Network rx count | Total number of RX packets received by the node during internal cluster communication. |
68
-
|| Network tx bytes | Size of TX packets sent by the node during internal cluster communication. |
69
-
|| Network tx count | Total number of TX packets received by the node during internal cluster communication. |
70
-
| Disk | Disk read bytes | The total number of bytes read across all devices used by {{es}}. |
71
-
|| Disk read IOPS | The total number of completed read operations across all devices used by {{es}}. |
72
-
|| Disk write bytes | The total number of bytes written across all devices used by {{es}}. |
73
-
|| Disk write IOPS | The total number of completed write operations across all devices used by {{es}}. |
60
+
| Circuit breakers | Parent Used |The parent circuit breaker tracks the overall heap memory that is necessary for all circuit breakers, and prevents {{es}} from exceeding a pre-configured threshold. |
61
+
|| Field Data used |The field data circuit breaker tracks the necessary heap memory for holding field data and global ordinals (e.g., both used to perform aggregations) and prevents {{es}} from exceeding a pre-configured threshold. |
62
+
|| Request used |The request circuit breaker tracks the necessary heap memory for holding per-request data structures (e.g., memory used for calculating aggregations during a request) and prevents {{es}} from exceeding a pre-configured threshold. |
63
+
|| Parent tripped | Total number of times the parent circuit breaker has reached the pre-configured threshold and prevented an out-of-memory error. |
64
+
|| Field data tripped | Total number of times the field data breaker has reached the pre-configured threshold and prevented anout-of-memory error. |
65
+
|| Request tripped | Total number of times the request circuit breaker has reached the pre-configured threshold and prevented an out-of-memory error. |
66
+
| Network | Network rx bytes | Size of network packets received by the node during internal cluster communication. |
67
+
|| Network rx count | Total number of network packets received by the node during internal cluster communication. |
68
+
|| Network tx bytes | Size of network packets transmitted by the node during internal cluster communication. |
69
+
|| Network tx count | Total number of network packets transmitted by the node during internal cluster communication. |
70
+
| Disk | Disk read bytes | The total number of bytes read across all storage devices used by {{es}}. |
71
+
|| Disk read IOPS | The total number of read operations performed every second across all storage devices used by {{es}}. |
72
+
|| Disk write bytes | The total number of bytes written across all storage devices used by {{es}}. |
73
+
|| Disk write IOPS | The total number of write operations performed every second across all storage devices used by {{es}}. |
74
74
| Activity-Additional | Merge rate | Number of merge operations being executed per second on all shards hosted on the node. |
75
75
|| Merge latency | Average latency for merging, which is the time it takes to execute merges divided by the number of merge operations submitted to the node. |
76
76
|| Indexing failed | Number of failed indexing operations on the node. |
0 commit comments