Monitoring Metrics for Logstash Clusters in Cloud Eye
You can use Cloud Eye to monitor cluster metrics of CSS in real time and quickly handle exceptions.
Function
This section describes CSS metrics that can be monitored by Cloud Eye as well as their namespaces and dimensions. You can use the management console or APIs provided by Cloud Eye to view the monitoring metrics and alarms generated for CSS.
- If the configuration center of a Logstash cluster does not have any records of operations on the pipeline list, the monitoring records of this Logstash cluster are empty.
- When the Events data of a pipeline changes dynamically, the monitoring data changes accordingly. When a pipeline task is being started or stopped, or the Events data is stable, the monitoring data remains unchanged.
Namespaces
SYS.ES
CSS.CUSTOM
Cluster Monitoring Metrics
- Table 1 describes the monitoring metrics of CSS clusters.
- Monitored object: CSS clusters This section describes the monitoring metrics for Logstash clusters.
- Monitoring period (original metric): 1 minute
Accumulated value: The value is accumulated from the time when a node is started. After the node is restarted, the value is reset to zero and accumulated again.
Metric ID |
Metric |
Description |
Value Range |
---|---|---|---|
max_jvm_heap_usage |
Max. JVM Heap Usage |
Maximum JVM heap usage of nodes in a CSS cluster Unit: % |
0-100% |
max_jvm_young_gc_time |
Max. JVM Young GC Duration |
Maximum accumulated JVM Young GC duration of nodes in a CSS cluster Unit: ms |
≥ 0 ms |
max_jvm_young_gc_count |
Max. JVM Young GC Count |
Maximum accumulated JVM Young GC count of nodes in a CSS cluster |
≥ 0 |
max_jvm_old_gc_time |
Max. JVM Old GC Duration |
Maximum accumulated JVM Old GC duration of nodes in a CSS cluster Unit: ms |
≥ 0 ms |
max_jvm_old_gc_count |
Max. JVM Old GC Count |
Maximum accumulated JVM Old GC count of nodes in a CSS cluster. |
≥ 0 |
max_cpu_usage |
Max. CPU Usage |
Maximum node CPU usage in a CSS cluster Unit: % |
0-100% |
max_load_average |
Max. Node Load |
Maximum number of average queued tasks per minute on nodes in a cluster |
≥ 0 |
avg_cpu_usage |
Avg. CPU Usage |
Average node CPU usage in a CSS cluster. Unit: % |
0-100% |
avg_load_average |
Avg. Node Load |
Average number of queued tasks per minute on nodes in a CSS cluster |
≥ 0 |
avg_jvm_heap_usage |
Avg. JVM Heap Usage |
Average node JVM heap usage in a CSS cluster Unit: % |
0-100% |
avg_jvm_old_gc_count |
Avg. GCs of Old-Generation JVM |
Average number of old-generation garbage collections of nodes in a CSS cluster |
≥ 0 |
avg_jvm_old_gc_time |
Avg. GC Duration of Old-Generation JVM |
Average old-generation garbage collection duration of nodes in a CSS cluster Unit: ms |
≥ 0 ms |
avg_jvm_young_gc_count |
Avg. GCs of Young-Generation JVM |
Average number of young-generation garbage collections of nodes in a CSS cluster |
≥ 0 |
avg_jvm_young_gc_time |
Avg. GC Duration of Young-Generation JVM |
Average young-generation garbage collection duration of nodes in a CSS cluster Unit: ms |
≥ 0 ms |
sum_events_in |
Total Records Passed Through the Input Plug-in |
Total number of records that have passed through the input plugin on all the nodes in a cluster |
≥ 0 |
sum_events_filtered |
Total Records Passed Through the Filtered Plug-in |
Total number of records that have passed through the filtered plugin on all the nodes in a cluster |
≥ 0 |
sum_events_out |
Total Records Passed Through the Out Plug-in |
Total number of records that have passed through the out plugin on all the nodes in a cluster |
≥ 0 |
Node Monitoring Metrics
- Table 2 describes the monitoring metrics of CSS cluster nodes.
- Monitored object: Cloud service nodes of CSS clusters
- Monitoring period (original metric): 1 minute
Metric ID |
Metric |
Description |
Value Range |
---|---|---|---|
jvm_heap_usage |
JVM Heap Usage |
JVM heap memory usage of a node. Unit: % |
0-100% |
cpu_usage |
CPU Usage |
CPU usage. Unit: % |
0-100% |
load_average |
Average Load |
Average number of queued tasks per minute on a node |
≥ 0 |
jvm_old_gc_count |
Total GCs of Old-Generation JVM |
Number of old-generation garbage collection times |
≥ 0 |
jvm_old_gc_time |
Total GC Duration of Old-Generation JVM |
Time spent on old-generation garbage collection Unit: ms |
≥ 0 ms |
jvm_young_gc_count |
Total GCs of Young-Generation JVM |
Number of young-generation garbage collection times |
≥ 0 |
jvm_young_gc_time |
GC Duration of Young-Generation JVM |
Time spent on young-generation garbage collection Unit: ms |
≥ 0 ms |
events_in |
Records Passed Through the Input Plug-in on Node |
Number of data records that have passed through the input plugin on the current node |
≥ 0 |
events_filtered |
Records Passed Through the Filtered Plug-in on Node |
Number of records that have passed through the filtered plugin on the current node |
≥ 0 |
events_out |
Records Passed Through the Out Plug-in on Node |
Number of records that have passed through the out plugin on the current node |
≥ 0 |
Logstash Pipeline Monitoring Metrics
- Table 3 describes the monitoring metrics of Logstash pipelines.
- Monitored object: Logstash pipelines used in CSS clusters
- Monitoring period (original metric): 1 minute
Metric ID |
Metric |
Description |
Value Range |
---|---|---|---|
logstash_pipeline_events_in |
Records Passed Through the Input Plug-in into Pipeline |
Number of records that have passed through the input plug-in during the current pipeline monitoring period |
≥ 0 |
logstash_pipeline_events_filtered |
Records Filtered for Pipeline |
Number of records that have passed through the filtered plug-in during the current pipeline monitoring period |
≥ 0 |
logstash_pipeline_events_out |
Records Passed Through the Out Plug-in Out of Pipeline |
Number of records that have passed through the out plug-in during the current pipeline monitoring period |
≥ 0 |
Dimension
Key |
Value |
---|---|
cluster_id |
CSS cluster |
cluster_id,instance_id |
CSS cluster node |
cluster_id,instance_id,pipeline_name |
Logstash pipeline name, node, CSS cluster |
cluster_id,pipeline_name |
Logstash pipeline name, CSS cluster |
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