Configure Filebeat Output & YML Settings in Elasticsearch - Elasticsearch

After installing a shipper, update its configuration on the Beats Data Shippers page of the Elasticsearch console.

Prerequisites

Before you begin, make sure you have:

A shipper installed. For instructions, see Collect the logs of an ECS instance.

This topic uses a Filebeat shipper as an example.

Modify the configuration

Log on to the Alibaba Cloud Elasticsearch console.
In the left-side navigation pane, click Beats Data Shippers.
In the Manage Shippers section, find the Filebeat shipper and click Configure in the Actions column.

In the Configure Shipper panel, click Modify, then update the settings based on your requirements.

Data output

Parameter	Description
Output	The destination for the data collected by the shipper. Select an Elasticsearch or Logstash cluster. The protocol must match that of the selected Elasticsearch cluster.
Username and Password	Required when Output is set to Elasticsearch. The shipper uses these credentials to write data to the cluster. The default username is `elastic`. The password is the one you set when creating the cluster. If you forgot the password, see Reset the access password for an Elasticsearch cluster.

Monitoring and visualization

Parameter	Description
Enable Kibana Monitoring	Monitors shipper metrics. If Output is Elasticsearch, Kibana monitoring uses the same cluster. If Output is Logstash, configure the monitor separately in the Logstash cluster configuration file.
Enable Kibana Dashboard	Enables the default Kibana dashboard. Alibaba Cloud Kibana runs in a virtual private cloud (VPC), so you must enable Private Network Access on the Kibana Configuration page first. For details, see Configure a public or private IP address whitelist for Kibana.

Log collection

Parameter	Description
Filebeat File Path	Filebeat-specific. Alibaba Cloud deploys Beats with Docker, so map the log source directory to Docker. Use a path consistent with `input.path` in `filebeat.yml`.
Shipper YML Configuration	The YML configuration file for the shipper. For guidance, see Prepare a YML configuration file for a shipper. Do not define the output destination here if you have already set Output above.

Important

Define the output destination in only one place — either the Output field in the console or in Shipper YML Configuration. Configuring both causes a shipper installation error.

Click Save.
The shipper enters the Enabling state. When the state changes to Enabled, the configuration update is complete.