Alibaba Cloud ElasticSearch¶
Alibaba Cloud ElasticSearch metrics display, including cluster status, index QPS, node CPU/memory/disk usage, etc.
Configuration¶
Install Func¶
It is recommended to enable TrueWatch integration - extension - managed Func: all prerequisites are automatically installed. Please continue with the script installation.
If you deploy Func yourself, refer to Self-deployed Func
Install Script¶
Note: Please prepare an Alibaba Cloud AK that meets the requirements in advance (for simplicity, you can directly grant global read-only permission
ReadOnlyAccess
)
To synchronize monitoring data of ElasticSearch cloud resources, we install the corresponding collection script: "TrueWatch Integration (Alibaba Cloud-ElasticSearch Collection)" (ID: truewatch_aliyun_elasticsearch
)
After clicking [Install], enter the corresponding parameters: Alibaba Cloud AK, Alibaba Cloud account name.
Click [Deploy Startup Script], and the system will automatically create a Startup
script set and automatically configure the corresponding startup script.
After it is enabled, you can see the corresponding automatic trigger configuration in "Manage / Automatic Trigger Configuration". Click [Execute] to run it immediately without waiting for the scheduled time. After a short wait, you can view the execution task records and corresponding logs.
If you want to collect corresponding logs, you need to enable the corresponding log collection script. If you want to collect billing information, you need to enable the cloud billing collection script.
We default collect some configurations, details see the metrics section
Configure custom cloud object metrics
Verification¶
- In "Manage / Automatic Trigger Configuration", confirm whether the corresponding tasks have the corresponding automatic trigger configurations. You can also check the corresponding task records and logs to check for any anomalies.
- On the TrueWatch platform, under "Infrastructure / Custom", check if there is asset information.
- On the TrueWatch platform, under "Metrics", check if there are corresponding monitoring data.
Metrics¶
After configuring Alibaba Cloud - Cloud Monitor, the default metric set is as follows. More metrics can be collected through configuration. Alibaba Cloud Cloud Monitor Metric Details
Metric Id | Metric Name | Dimensions | Statistics | Unit |
---|---|---|---|---|
ClusterAutoSnapshotLatestStatus |
Snapshot Status | userId,clusterId | Maximum | value |
ClusterIndexQPS |
Cluster Write QPS | userId,clusterId | Average | Count/Second |
ClusterQueryQPS |
Cluster Query QPS | userId,clusterId | Average | Count/Second |
ClusterStatus |
Cluster Status | userId,clusterId | Value,Maximum | value |
NodeCPUUtilization |
elasticsearch instance node CPU utilization | userId,clusterId,nodeIP | Average,Maximum | % |
NodeDiskUtilization |
elasticsearch instance node disk utilization | userId,clusterId,nodeIP | Average,Maximum | % |
NodeHeapMemoryUtilization |
elasticsearch instance node HeapMemory utilization | userId,clusterId,nodeIP | Average,Maximum | % |
NodeLoad_1m |
Node Load_1m | userId,clusterId,nodeIP | Average | value |
NodeStatsDataDiskR |
Number of read requests completed per second | userId,clusterId,nodeIP | Maximum | count |
NodeStatsDataDiskRm |
Size read per second | userId,clusterId,nodeIP | Maximum | MB/s |
NodeStatsDataDiskUtil |
IOUtil | userId,clusterId,nodeIP | Maximum | % |
NodeStatsDataDiskW |
Number of write requests completed per second | userId,clusterId,nodeIP | Maximum | count |
NodeStatsDataDiskWm |
Size written per second | userId,clusterId,nodeIP | Maximum | MB/s |
NodeStatsExceptionLogCount |
Exception Count | userId,clusterId,nodeIP | Maximum | Count |
NodeStatsFullGcCollectionCount |
Full Gc Count | userId,clusterId,nodeIP | Maximum | Count |
NodeStatsNetworkinPackages |
Node Network Inbound Packets | userId,clusterId,nodeIP | Maximum | count |
NodeStatsNetworkinRate |
Data Inbound Rate | userId,clusterId,nodeIP | Maximum | kB/s |
NodeStatsNetworkoutPackages |
Node Network Outbound Packets | userId,clusterId,nodeIP | Maximum | count |
NodeStatsNetworkoutRate |
Data Outbound Rate | userId,clusterId,nodeIP | Maximum | kB/s |
NodeStatsTcpEstablished |
Node TCP Connections | userId,clusterId,nodeIP | Maximum | count |
Objects¶
The structure of the collected Alibaba Cloud ElasticSearch object data can be viewed in "Infrastructure - Custom"
{
"measurement": "aliyun_elasticsearch",
"tags": {
"RegionId": "cn-hangzhou",
"esVersion": "7.4.0_with_X-Pack",
"instanceId": "es-cn-xxxx",
"name": "es-cn-xxxx",
"paymentType": "prepaid",
"resourceGroupId": "rg-acfm2l3p7xxxx",
"serviceVpc": "True",
"status": "active"
},
"fields": {
"advancedDedicateMaster": false,
"createdAt": "2021-04-07T06:10:50.527Z",
"extendConfigs": "[ {Cluster extended parameter configuration JSON data}, ...]",
"message": "{Instance JSON data}"
}
}
Logs¶
Prerequisites¶
Note 1: Before using this collector, you must install the "TrueWatch Integration Core package" and its accompanying third-party dependency packages. Note 2: This script's code execution depends on mongodb instance object collection. If custom object collection for mongodb is not configured, the slow log script cannot collect slow log data.
Install Script¶
On top of the previous setup, you need to install another script for Elasticsearch log collection
In "Manage / Script Market", click and install the corresponding script package:
- "TrueWatch Integration (Alibaba Cloud-ElasticSearch Collection)" (ID:
truewatch_aliyun_elasticsearch_log
)
Data Reporting Format¶
After the data is synchronized normally, you can view the data in "Infrastructure - Custom Objects" on TrueWatch.
An example of the reported data is as follows:
{
"measurement": "aliyun_elasticsearch_log",
"tags": {
"RegionId": "cn-hangzhou",
"esVersion": "7.10.0_with_X-Pack",
"host": "10.14.xxx.xxx",
"instanceId": "es-cn-xxxx",
"name": "es-cn-xxxx",
"paymentType": "prepaid",
"resourceGroupId": "rg-aekzkcwe4dxxxx",
"serviceVpc": "True",
"status": "active"
},
"fields": {
"timestamp": 1684304299000,
"contentCollection": "[ {Detailed Log Information JSON Data}, ...]",
"message": "{Instance JSON Data}"
}
}
log_types (Log Types) value meanings:
Value | Description |
---|---|
INSTANCELOG |
Main Log |
SEARCHSLOW |
Searching Slow Logs |
INDEXINGSLOW |
Indexing Slow Logs |
JVMLOG |
GC Logs |
ES_SEARCH_ACCESS_LOG |
ES Access Logs |
AUDIT |
Audit Logs |
Note: The fields in
tags
andfields
may change with subsequent updates. Note 1: The value of tags.name is the instance ID, used as unique identification. Note 2:fields.message
is a JSON serialized string.