You can use Beats to collect the data of an Elastic Compute Service (ECS) instance. The data includes logs, network data, and metrics. Beats then sends the data to Alibaba Cloud Elasticsearch or Logstash for further processing, such as monitoring and analytics. This topic describes how to use a Filebeat shipper to collect the logs of an ECS instance.
- An Alibaba Cloud Elasticsearch or Logstash cluster is created.
- 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 when it collects the logs of ECS instances. If you select Elasticsearch for Output, you must enable the Auto Indexing feature for the Elasticsearch cluster. For more information, see Configure the YML file.
- An ECS instance is created in the same virtual private cloud (VPC) as the Elasticsearch or Logstash cluster.
When you create the ECS instance, select one of the following types of operating systems: Alibaba Cloud Linux, Red Hat Enterprise Linux (RHEL), and Community Enterprise Operating System (CentOS). Beats supports only these three types of operating systems. For more information, see Create an instance by using the wizard.Notice The default installation directory of Beats is /opt/aliyunbeats/. After you install Beats, the conf, logs, and data directories are generated on the ECS instance. The conf directory contains the configuration file, the logs directory contains the Beats log file, and the data directory contains the Beats data file. We recommend that you do not modify these files. Otherwise, errors may occur, or data may be incorrect. If an error occurs, you can view the Beats logs in the logs directory to locate the error.
- Cloud Assistant and Docker are installed on the ECS instance.
For more information, see Install the Cloud Assistant client and Deploy and use Docker on Alibaba Cloud Linux 2 instances.
- Log on to the Elasticsearch console.
- In the top navigation bar, select a region. In the left-side navigation pane, click Beats Data Shippers.
- Optional:If this is the first time you go to the Beats Data Shippers page, click Confirm in the Confirm Service Authorization message to authorize the system to create a service-linked role for your account.
Notice When Beats collects data from various data sources, it depends on the service-linked role and the rules specified for the role. Do not delete the service-linked role. Otherwise, the use of Beats is affected. For more information, see Overview of the Elasticsearch service-linked role.
- Configure and enable a Filebeat shipper to collect the logs of the ECS instance.
- In the Create Shipper section, move the pointer over Filebeat and click ECS Logs.
Note For other types of shippers, you can directly click the shipper type. For example, to create a Metricbeat shipper, click Metricbeat.
- In the Configure Shipper step, configure the following parameters. Then, click Next.
Parameter Description Shipper Name The name of the shipper. The name must be 1 to 30 characters in length and can contain letters, digits, underscores (_), and hyphens (-). The name must start with a letter. Version Set this parameter to 6.8.5, which is the only version supported by Filebeat. Output Select a destination for the data collected by the shipper. The system provides Elasticsearch and Logstash clusters for you to select. If you select an Elasticsearch cluster, the protocol used for access must be the same as that of the cluster. Username/Password If you select Elasticsearch for Output, enter the username and password used to access the destination Elasticsearch cluster. This way, the shipper can write data to the cluster. The default username is elastic. The password is specified when you create the cluster. If you forget the password, you can reset it. For more information about the procedure and precautions for resetting the password, see Reset the access password for an Elasticsearch cluster. Enable Kibana Monitoring Specifies whether to monitor the metrics of the shipper. If you select Elasticsearch for Output, the Kibana monitor uses the same Elasticsearch cluster as Output. If you select Logstash for Output, you must configure a monitor in the configuration file. Enable Kibana Dashboard Specifies whether to enable the default Kibana dashboard. Alibaba Cloud Kibana is deployed in a VPC. You must enable the Private Network Access feature for Kibana on the Kibana configuration page. For more information, see Configure an IP address whitelist for access to the Kibana console over the Internet or an internal network. Filebeat Log File Path This parameter is specific to Filebeat shippers. Alibaba Cloud deploys Beats with Docker. You must map the directory from which logs are collected to Docker. The directory that you specify must be consistent with
filebeat.yml. If you want to collect logs from a multi-level directory, you need only to specify one level in the directory. If the name of a level in the directory contains an
asterisk (*), you do not need to enter the name of this level when you specify the Filebeat Log File Path parameter. For example, if you want to collect logs from the directory
/var/log/*/*.logand you specify input.path:/var/log/*/*.log in for input.path, you need only to enter
/var/log/when you specify the Filebeat Log File Path parameter.
Shipper YML Configuration The YML configuration file of the shipper. You can modify the configuration file based on your business requirements. For more information, see Prepare the YML configuration files for a shipper.Notice If you already specify Output, you do not need to specify it again in Shipper YML Configuration. Otherwise, the system reports a shipper installation error.
- Optional:If this is the first time you go to the Install Shipper step, click Authorize Now. On the Cloud Resource Access Authorization page, click Agree to Authorization.
In the Install Shipper step, click Authorize Now to authorize the selected Elasticsearch cluster to access ECS instances.On the Cloud Resource Access Authorization page, click Agree to Authorization.Notice
- The authorization service is provided by Resource Access Management (RAM). After you confirm the authorization, the system automatically creates the system roles AliyunElasticsearchAccessingOOSRole and AliyunOOSAccessingECS4ESRole. The default system policy for AliyunElasticsearchAccessingOOSRole is AliyunElasticsearchAccessingOOSRolePolicy, and that for AliyunOOSAccessingECS4ESRole is AliyunOOSAccessingECS4ESRolePolicy. Do not delete the system roles and policies during the use of Beats.
- If the system roles or policies are deleted, you can go to the Cloud Resource Access Authorization page to perform authorization again.
- In the Install Shipper step, select the ECS instance on which you want to install the shipper.
Notice All the ECS instances within your account that reside in the same VPC as the Elasticsearch or Logstash cluster selected for Output are displayed. A shipper can be installed only on an ECS instance on which Cloud Assistant and Docker are installed.
- Click Enable.
- In the Enable Shipper dialog box, click Back to Beats Shippers. In the Manage Shippers section of the Beats Data Shippers page, view the newly created shipper.
After the value of Status for the shipper changes to Enabled, the shipper is created. The two numbers that follow Enabled indicate the number of ECS instances on which the shipper is installed and the total number of ECS instances on which you want to install the shipper. If the shipper is installed on all ECS instances, the two numbers are the same.
- In the Create Shipper section, move the pointer over Filebeat and click ECS Logs.
- View the running ECS instance.
After the shipper is created, you can view the running ECS instance to check whether shipper installation on the ECS instance succeeds and handle exceptions as prompted.
- In the Manage Shippers section, find the shipper that you created and click View Instances in the Actions column.
- In the View Instances panel, check whether the shipper installation on the ECS instance succeeds.
The Installed Shippers column provides the value Heartbeat Normal, Heartbeat Abnormal, or Installation Failed to indicate whether the shipper installation on an ECS instance succeeds. If the value of Installed Shippers is Heartbeat Abnormal or Installation Failed, you can remove the instance or retry the installation on the instance. If the retry fails, you can troubleshoot the issue based on the instructions provided in Installation failures of Beats shippers.
- Click Add Instance to add the ECS instances on which you want to install a shipper with the same configuration and type as the created shipper.
- Optional:View monitoring and dashboard information.
If you select Enable Kibana Monitoring or Enable Kibana Dashboard in the Configure Shipper step, you can view the monitoring information or dashboards in the Kibana console of the destination Elasticsearch cluster after the shipper is started.
- In the Manage Shippers section, find the shipper that you created and choose in the Actions column.
- On the logon page of the Kibana console, enter the username and password, and click Log in.
- In the left-side navigation pane, click Dashboard and click a metric whose dashboard you want to view. Then, you can view the dashboard of the metric.
- In the left-side navigation pane, click Monitoring and select a monitoring item whose information you want to view. Then, you can view the information of the monitoring item.