This topic describes how to use Alibaba Cloud Heartbeat to check the status of Internet Control Message Protocol (ICMP) and HTTP services. It can also generate visual charts.
Background information
- ICMPv4 or ICMPv6 monitor: sends ICMP requests to check whether a service is available. This type of monitor connects to a service over ICMP. If you want to use an ICMP monitor, root permissions are required.
- TCP monitor: sends or receives specific workloads to check whether a service is available. This type of monitor connects to a service over TCP.
- HTTP monitor: checks whether a service is available based on specific status codes,
response headers, or response content. This type of monitor connects to a service
over HTTP.
Note TCP and HTTP monitors support Secure Sockets Layer (SSL), Transport Layer Security (TLS), and some proxy settings.
Prerequisites
- An Alibaba Cloud Elasticsearch cluster is created.
For more information, see Create an Elasticsearch cluster.
- The Auto Indexing feature is enabled for the Elasticsearch cluster.
For security purposes, Alibaba Cloud Elasticsearch disables the Auto Indexing feature by default. However, Beats depends on this feature. If you select Elasticsearch for Output when you create a shipper, you must enable the Auto Indexing feature. For more information, see Enable auto indexing.
- An Alibaba Cloud Elastic Compute Service (ECS) instance is created in the same virtual
private cloud (VPC) as the Elasticsearch cluster.
For more information, see Create an instance by using the provided wizard.
Notice Beats supports only Aliyun Linux, Red Hat Linux, and CentOS. - Cloud Assistant and Docker are installed on the ECS instance.
For more information, see Install the Cloud Assistant client and Deploy and use Docker.