The advanced monitoring and alerting service collects both basic metrics and engine metrics. This provides real-time insight into your Alibaba Cloud Elasticsearch cluster and its underlying engine. You can use this data to quickly understand the health of your cluster and troubleshoot performance or stability issues. This topic describes how to view this monitoring data.
Prerequisites
-
An Alibaba Cloud Elasticsearch instance is created in a region that supports the advanced monitoring and alert service.
-
The advanced monitoring and alert service is available in the following regions: Hangzhou, Beijing, Shanghai, Shenzhen, Qingdao, Zhangjiakou, Chengdu, Guangzhou, Ulanqab, Beijing Finance Cloud, US (Virginia), US (Silicon Valley), Japan (Tokyo), Indonesia (Jakarta), and China (Hong Kong). The regions available in the console are definitive.
-
For more information about how to create an instance, see Create an Alibaba Cloud Elasticsearch instance.
-
-
Learn how to use Grafana monitoring dashboards. For more information, see Grafana dashboards.
Limits
-
The advanced monitoring and alert feature provides monitoring and alerts for infrastructure metrics, engine metrics, and log data. Only Elasticsearch 6.7.0 or 7.10.0 with a kernel version later than 1.2.0 supports engine metric monitoring. To upgrade the kernel version, see Upgrade versions.
-
You cannot access the advanced monitoring and alert service when you use a RAM role for single sign-on (SSO) to the Alibaba Cloud Management Console. For more information, see Log on to the Alibaba Cloud Management Console using a RAM role for SSO. To access the service, use a Resource Access Management (RAM) user for SSO to the Alibaba Cloud Management Console. For more information, see Log on to the Alibaba Cloud Management Console using a RAM user for SSO.
Procedure
Log on to the Alibaba Cloud Elasticsearch console.
In the left-side navigation pane, click Advanced Monitoring and Alerting.
NoteBy default, the advanced monitoring and alerting service displays data from instances across all regions under your account.
On the Advanced Monitoring and Alerting page, choose to view the metric data for all connected instances.
They differ mainly in the monitoring objects they support, as described in the following table.
Metric
Description
Basic metrics
Provides coarse-grained resource monitoring for a centralized overview of your cluster's resource status. It supports monitoring items related to cluster, index, node resource, node network, node disk, node JVM, and Thread_pool.
NoteFor instances in regions outside the Chinese mainland that are earlier than version 7.10, the supported basic metrics are different. Unsupported metrics show no data. The available metrics are listed in the console.
Engine metrics
Provides fine-grained resource monitoring for insight into multi-dimensional data processing status. It supports monitoring items related to search, bulk, indexing service, Openstore, cache, refresh, merge, cluster state, segment replication, and isolator.
Note-
The Grafana dashboards in the Advanced Monitoring and Alerting service function in the same way as open source Grafana dashboards. For more information, see the Grafana documentation.
-
The default monitoring dashboards provided by the Advanced Monitoring and Alerting service cannot be modified. To create a dashboard that better suits your business needs, you can configure a custom monitoring dashboard.
For a detailed description of the monitoring items, see Basic metrics and Engine metrics.
-
View monitoring data for a specific instance, node, or index.
Hover over a monitoring chart and press the Esc key. The Grafana menu and filter bar appear.
In the filter bar, enter or select filter criteria to view specific monitoring data.
Default filter items for basic metrics: Includes source (default: es-metric), instanceId, index, node_ip, and regionId.
Default filter items for engine metrics: Includes datasource (default: es-metric), instanceId, ip, index, shardId, and regionId.
Parameter
Description
source/datasource
The data source for metric monitoring has a default value of es-metric.
NoteThe
defaultdata source in the drop-down list is the same as thees-metricdata source.instanceId
Filters the monitoring data by instance ID. The default value is *, which indicates that the monitoring data for all instances is displayed.
ip/node_ip
Filters monitoring data by cluster node IP address. The default is *, which indicates no IP address restriction, allowing you to view the monitoring data for all nodes in the instance.
index
Filter monitoring data by index name. The default value is *, which indicates that monitoring data for all indexes is displayed.
shardId
Filters the monitoring data by shardId. The default value * indicates that no restrictions are applied and returns the monitoring data for all shards.
regionId
Filter monitoring data by region. The default is ALL, which displays monitoring data for instances in all regions.