Skip to content

Alibaba Cloud Lindorm

Use the series of script packages in the script market named «Guance Cloud Sync» to synchronize cloud monitoring and cloud asset data to Guance.

Configuration

Install Func

It is recommended to activate Guance Integration - Extension - Managed Func: All prerequisites are automatically installed, please proceed with the script installation.

If you deploy Func yourself, refer to Self-deployed Func

Install Func

It is recommended to activate Guance Integration - Extension - Managed Func

If you deploy Func yourself, refer to Self-deployed Func

Activate 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)

Managed Version Activation Script

  1. Log in to Guance Console
  2. Click on the 【Manage】 menu and select 【Cloud Account Management】
  3. Click 【Add Cloud Account】, select 【Alibaba Cloud】, and fill in the required information on the interface; if you have configured cloud account information before, ignore this step.
  4. Click 【Test】. After testing successfully, click 【Save】. If the test fails, check whether the related configuration information is correct and retest.
  5. In the 【Cloud Account Management】 list, you can see the added cloud accounts. Click the corresponding cloud account to enter the details page.
  6. Click the 【Integration】 button on the cloud account details page. Under the Not Installed list, find Alibaba Cloud Lindorm, click the 【Install】 button, and install it via the pop-up installation interface.

Manual Activation Script

  1. Log in to the Func console, click 【Script Market】, enter the official script market, and search for guance_aliyun_lindorm.

  2. After clicking 【Install】, input the corresponding parameters: Alibaba Cloud AK ID, AK Secret, and account name.

  3. Click 【Deploy Start Script】, the system will automatically create a Startup script set and configure the corresponding start scripts automatically.

  4. After enabling, you can see the corresponding automatic trigger configurations under 「Management / Automatic Trigger Configurations」. Click 【Execute】 to immediately execute once without waiting for the regular time interval. Wait a moment, then view the execution task records and corresponding logs.

We default collect some configurations, see the Metrics section for more details.

Customize cloud object metrics

Verification

  1. In 「Management / Automatic Trigger Configurations」, confirm whether the corresponding tasks have the relevant automatic trigger configurations, and check the corresponding task records and logs for any anomalies.
  2. In Guance, 「Infrastructure / Custom」, check if there is asset information.
  3. In Guance, 「Metrics」, check if there is corresponding monitoring data.

Metrics

After configuring Alibaba Cloud - Cloud Monitoring, the default metric sets are as follows. You can collect more metrics through configuration. Alibaba Cloud Cloud Monitoring Metric Details

Note: The monitoring plugin needs to be installed in the Aliyun Lindorm console.

MetricName MetricDescribe Dimensions Statistics Unit MinPeriods
load_one Average load every 5 minutes userId,instanceId,host Average,Maximum,Minimum load 60 s
load_five Average load every 5 minutes userId,instanceId,host Average,Maximum,Minimum load 60 s
cpu_system CPU utilization System userId,instanceId,host Average,Maximum,Minimum % 60 s
cpu_user CPU utilization User userId,instanceId,host Average,Maximum,Minimum % 60 s
cpu_idle CPU idle rate userId,instanceId,host Average,Maximum,Minimum % 60 s
cpu_wio CPU utilization IOWait userId,instanceId,host Average,Maximum,Minimum % 60 s
mem_total Total memory (total) userId,instanceId,host Average,Maximum,Minimum bytes 60 s
mem_used_percent Memory usage ratio userId,instanceId,host Average,Maximum,Minimum % 60 s
mem_free Free memory size (free) userId,instanceId,host Average,Maximum,Minimum bytes 60 s
mem_buff_cache Cache size (buff/cache) userId,instanceId,host Average,Maximum,Minimum bytes 60 s
mem_shared Shared memory size (shared) userId,instanceId,host Average,Maximum,Minimum bytes 60 s
bytes_in Network inflow per second userId,instanceId,host Average,Maximum,Minimum bytes/s 60 s
bytes_out Network outflow per second userId,instanceId,host Average,Maximum,Minimum bytes/s 60 s
storage_used_percent Storage space usage ratio userId,instanceId,host Average,Maximum,Minimum % 60 s
storage_used_bytes Storage space usage amount userId,instanceId,host Average,Maximum,Minimum bytes 60 s
storage_total_bytes Total storage space userId,instanceId,host Average,Maximum,Minimum bytes 60 s
hot_storage_used_percent Hot storage usage ratio userId,instanceId,host Average,Maximum % 60 s
hot_storage_used_bytes Hot storage usage amount userId,instanceId,host Average,Maximum bytes 60 s
hot_storage_total_bytes Total hot storage capacity userId,instanceId,host Average,Maximum bytes 60 s
cold_storage_used_percent Cold storage usage percentage userId,instanceId,host Average,Maximum,Minimum % 60 s
cold_storage_used_bytes Cold storage usage amount userId,instanceId,host Average,Maximum,Minimum bytes 60 s
cold_storage_total_bytes Total cold storage capacity userId,instanceId,host Average,Maximum,Minimum bytes 60 s
cold_storage_token_percent Cold storage read token usage ratio userId,instanceId,host Average,Maximum,Minimum % 60 s
store_locality Storage locality rate userId,instanceId,host Average,Maximum,Minimum % 60 s
disk_readbytes Disk read traffic userId,instanceId,host Average,Maximum,Minimum bytes/s 60 s
disk_writebytes Disk write traffic userId,instanceId,host Average,Maximum,Minimum bytes/s 60 s
table_cold_storage_used_bytes Wide table cold storage usage amount userId,instanceId,host Average,Maximum,Minimum bytes 60 s
table_hot_storage_used_bytes Wide table hot storage usage amount userId,instanceId,host Average,Maximum,Minimum Byte 60 s
read_ops Read request volume userId,instanceId,host Average,Maximum,Minimum countS 60 s
read_rt Average read RT userId,instanceId,host Average,Maximum,Minimum milliseconds 60 s
read_data_kb Read throughput userId,instanceId,host Average,Maximum,Minimum KB/s 60 s
get_num_ops Get request volume userId,instanceId,host Average,Maximum,Minimum countS 60 s
get_rt_avg Average Get RT userId,instanceId,host Average,Maximum,Minimum milliseconds 60 s
get_rt_p99 P99 delay for Get operations userId,instanceId,host Average,Maximum,Minimum milliseconds 60 s
scan_num_ops Scan request volume userId,instanceId,host Average,Maximum,Minimum countS 60 s
scan_rt_avg Average Scan delay userId,instanceId,host Average,Maximum,Minimum milliseconds 60 s
scan_rt_p99 P99 delay for Scan userId,instanceId,host Average,Maximum,Minimum milliseconds 60 s
thrift_call_num_ops Thrift request volume userId,instanceId Average count 60 s
thrift_call_mean Average thrift request duration userId,instanceId Average milliseconds 60 s
thrift_call_time_in_queue_ops Number of Thrift requests queued userId,instanceId Average count 60 s
thrift_call_time_in_queue Duration of Thrift requests queued userId,instanceId Average ms 60 s
write_ops Write request volume userId,instanceId,host Average,Maximum,Minimum countS 60 s
write_rt Average write RT userId,instanceId,host Average,Maximum,Minimum milliseconds 60 s
write_data_kb Write throughput userId,instanceId,host Average,Maximum,Minimum KB/s 60 s
put_num_ops Put request volume userId,instanceId,host Average,Maximum,Minimum countS 60 s
put_rt_avg Average Put RT userId,instanceId,host Average,Maximum,Minimum milliseconds 60 s
put_rt_p99 P99 delay for Put userId,instanceId,host Average,Maximum,Minimum milliseconds 60 s
above_memstore_count Number of times exceeding memstore limit userId,instanceId,host Average,Maximum,Minimum frequency 60 s
lql_connection sql connection count userId,instanceId,host Average,Maximum count 60 s
lql_select_ops Select request count userId,instanceId,host Average,Maximum countSecond 60 s
lql_upsert_avg_rt Average duration of upsert requests userId,instanceId,host Average,Maximum milliseconds 60 s
lql_upsert_ops upsert request count userId,instanceId,host Average,Maximum countSecond 60 s
lql_select_p99_rt p99 duration for select userId,instanceId,host Average,Maximum milliseconds 60 s
lql_select_avg_rt Average duration for select requests userId,instanceId,host Average,Maximum milliseconds 60 s
lql_upsert_p99_rt p99 duration for upsert userId,instanceId,host Average,Maximum milliseconds 60 s
lql_delete_ops Delete request count userId,instanceId,host Average,Maximum countSecond 60 s
lql_delete_avg_rt Average duration for delete requests userId,instanceId,host Average,Maximum milliseconds 60 s
lql_delete_p99_rt p99 duration for delete userId,instanceId,host Average,Maximum milliseconds 60 s
regions_per_ldserver Number of Regions managed by RegionServer userId,instanceId,host Average,Maximum,Minimum count 60 s
handler_queue_size HandlerQueue length userId,instanceId,host Average,Maximum,Minimum count 60 s
compaction_queue_size Compaction queue length userId,instanceId,host Average,Maximum,Minimum count 60 s
tsdb_jvm_used_percent JVM memory usage rate userId,instanceId,host Average,Maximum,Minimum % 60 s
tsdb_disk_used Disk usage userId,instanceId,host Average,Maximum,Minimum Gbyte 60 s
tsdb_hot_storage_used_bytes Time-series hot storage usage amount userId,instanceId,host Average,Maximum,Minimum bytes 60 s
tsdb_cold_storage_used_bytes Time-series cold storage usage amount userId,instanceId,host Average,Maximum,Minimum bytes 60 s
tsdb_datapoints_added Data point count userId,instanceId,host Average,Maximum,Minimum count 60 s
search_cold_storage_used_bytes Search cold storage usage amount userId,instanceId,host Average,Maximum,Minimum bytes 60 s
search_hot_storage_used_bytes Search hot storage usage amount userId,instanceId,host Average,Maximum,Minimum bytes 60 s
search_select_count Total number of selects userId,instanceId,host Average,Maximum,Minimum count 60 s
search_select_meanRate Average ops for selects userId,instanceId,host Average,Maximum,Minimum countS 60 s
search_select_mean_rt Average RT for selects userId,instanceId,host Average,Maximum,Minimum milliseconds 60 s
search_select_p95_rt p95 RT for selects userId,instanceId,host Average,Maximum,Minimum milliseconds 60 s
search_select_p999_rt p999 RT for selects userId,instanceId,host Average,Maximum,Minimum milliseconds 60 s
search_select_p99_rt p99 RT for selects userId,instanceId,host Average,Maximum,Minimum milliseconds 60 s
search_update_count Total number of updates userId,instanceId,host Average,Maximum,Minimum count 60 s
search_update_meanRate Average ops for updates userId,instanceId,host Average,Maximum,Minimum countS 60 s
search_update_mean_rt Average RT for updates userId,instanceId,host Average,Maximum,Minimum milliseconds 60 s
search_update_p95_rt p95 RT for updates userId,instanceId,host Average,Maximum,Minimum milliseconds 60 s
search_update_p99_rt p99 RT for updates userId,instanceId,host Average,Maximum,Minimum milliseconds 60 s
search_update_p999_rt p999 RT for updates userId,instanceId,host Average,Maximum,Minimum milliseconds 60 s
worker_count Number of worker nodes userId,instanceId,host Average,Maximum,Minimum count 60 s
failed_job_count Failed job count userId,instanceId,host Average,Maximum,Minimum count 60 s
warn_job_count Abnormal job count userId,instanceId,host Average,Maximum,Minimum count 60 s
task_delay_max Maximum task delay userId,instanceId,host Average,Maximum,Minimum ms 60 s
## Objects
Data structure of collected Alibaba Cloud Lindorm objects, which can be seen from 「Infrastructure - Custom」.
{
  "measurement": "aliyun_lindorm",
  "tags": {
    "name"           : "r-bp12xxxxxxx",
    "InstanceId"     : "r-bp12xxxxxxx",
    "InstanceStatus" : "CREATING",
    "NetworkType"    : "vpc",
    "PayType"        : "POSTPAY",
    "RegionId"       : "cn-hangzhou",
    "ServiceType"    : "lindorm_standalone",
    "VpcId"          : "vpc-bp1pxxxxxx4t75e73v",
    "ZoneId"         : "cn-hangzhou-f",
    "account_name"   : "xxx account",
    "cloud_provider" : "aliyun"
  },
  "fields": {
    "CreateTime"      : "2023-07-14 10:54:05",
    "EnableStream"    : "False",
    "InstanceStorage" : "20",
    "message"         : "{JSON instance data}"
  }
}

Note: Fields in tags and fields may change with subsequent updates.

Tip 1: The value of tags.name is the instance ID, used for unique identification.

Tip 2: fields.message is a JSON serialized string.

Feedback

Is this page helpful? ×