Elasticsearch:Monitor an Alibaba Cloud Elasticsearch service with Uptime

Deployment architecture

• Single-instance deployment

  A single Heartbeat instance monitors a service from one location and sends data to Alibaba Cloud Elasticsearch. You can then use Uptime in Kibana to view the data and assess service status.

• Multi-instance deployment

  Two Heartbeat instances monitor the same service from different locations and send data to Alibaba Cloud Elasticsearch. You can use Uptime in Kibana to view the data and assess service status. If one instance fails, multiple monitoring locations help you identify the affected region.

For more deployment architectures, see Deployment Architecture.

Prerequisites

1. Create an Alibaba Cloud Elasticsearch instance and enable Auto Indexing.

   For more information, see Create an Alibaba Cloud Elasticsearch instance and Configure YML parameters.

2. Create an ECS instance to host Heartbeat. The ECS instance must reside in the same VPC as your Alibaba Cloud Elasticsearch instance.

   For more information, see Create an instance by using the wizard.

   Important

   When you create the ECS instance, select one of the following operating systems supported by Beats (including Heartbeat): Alibaba Cloud Linux, Red Hat, or CentOS.

3. Install Cloud Assistant and Docker on the ECS instance.

   For more information, see Install the Cloud Assistant agent and Deploy and use Docker.

Create a Heartbeat shipper

1. Log on to the Alibaba Cloud Elasticsearch console.

2. In the left-side navigation pane, click Beats Data Shippers.

3. In the Create Shipper section, click Heartbeat.

4. Install and configure the shipper.

   For more information, see Use Filebeat to collect logs from an ECS instance and Configure the YML file for a shipper.

   The following table describes the heartbeat.monitors parameters in the heartbeat.yml file used in this topic.

   
   # Configure monitors inline
   heartbeat.monitors:
   - type: http
   
     # List or urls to query
     urls: ["http://xxx.aliyuncs.com:9200"]
     usersname: elastic
     password: Es123456
     # Configure task schedule
     schedule: '@every 10s'
   

   Parameter	Description
   type	The monitor type. In this example, set this parameter to http. Note Heartbeat can check services over HTTP/HTTPS, TCP, and ICMP. For example, an HTTP/HTTPS monitor can verify the response code, body, and headers, while a TCP monitor can check a port and a string.
   urls	The URLs to check. You can specify multiple HTTP services. Because this example checks an Alibaba Cloud Elasticsearch service, set this parameter to the internal endpoint of the target instance.
   schedule	The check interval. @every 10s specifies a check every 10 seconds.

5. Click Next step.

6. In the list of ECS instances, select the instance where you want to install the shipper.

7. Click Start to start the shipper.

   The shipper is successfully installed when the Shipper Status is Enabled and the Installed Shippers in the View Instances window of the Actions column is Normal Heartbeat.

View monitoring data in Uptime

1. Log on to the Kibana console.

   This refers to the Kibana console of the Alibaba Cloud Elasticsearch instance configured as the shipper's Output. For more information, see Log on to the Kibana console.

2. In the left-side navigation pane, click Uptime to view the monitoring data.

   The Uptime overview page contains the following sections:

   • Endpoint status: Displays the number of Up, Down, and Total endpoints.

   • Status over time: A bar chart showing the monitoring status for each time period.

   • Monitor status: A table showing the status, host, port, type, and monitoring history for each monitor.

   • Error list: A table showing error types, monitor IDs, error counts, status codes, and error messages such as 502 Bad Gateway.

   • Red: Abnormal status. Check the Heartbeat communication or the Alibaba Cloud Elasticsearch status.

   • Blue: Normal status.