Filebeat is a log shipping tool. It collects logs from a device and sends them to an external storage.
In Filebeat’s Settings, specify a source of the logs you need, for example, logs of a specific service, internal storage, TCP port, or OS events. Indicate a location for log export—Gcore’s Logging servers. After that, Filebeat works automatically: once a required log is recorded in the system, the log shipper transfers it to our storage, and the log appears on OpenSearch Dashboards.
An up-to-date link for Filebeat installation is available on its Filebeat official webpage. Open the Filebeat website and click Download.
The Filebeat configuration file consists of two sections:
inputs determines the source of the logs you need to collect, and
output indicates the destination where they will be sent. Here’s how to set up the configuration file correctly:
filebeat.ymlfile and add the following data:
Customize the highlighted values:
You can also collect logs from other sources such as TCP, UDP, or syslog. For more details, refer to the "Configure inputs" section of the Filebeat documentation: Click the log source you need, and configure the
inputs section following the provided guide.
Save the changes in the Filebeat configuration file.
Restart Filebeat, and it will begin sending logs to your Gcore Logging storage.
Was this article helpful?
Discover our offerings, including virtual instances starting from 3.7 euro/mo, bare metal servers, AI Infrastructure, load balancers, Managed Kubernetes, Function as a Service, and Centralized Logging solutions.