When specifying paths manually you need to set the input configuration to enabled: true in the Filebeat configuration file. You can configure paths manually for Container, Docker, Logs, Netflow, Redis, Stdin, Syslog, TCP and UDP. This means that you are not using a module and are instead specifying inputs in the filebeat.inputs section of the configuration file. filebeat modules enable apache2Įnabling modules isn't required but it is one of the easiest ways of getting Filebeat to look in the correct place for data.
#FILEBEATS COMMAND LINE HOW TO#
An example on how to enable a module to process apache logs is to run the following command.
This means that Filebeat does not know what data it is looking for unless we specify this manually. In the above screenshot you can see that there are no enabled Filebeat modules. You will also notice the response tells us which modules are enabled or disabled. You can check the list of modules available to you by running the Filebeat modules list command. Modules are the easiest way to get Filebeat to harvest data as they come preconfigured for the most common log formats. The easiest way to do this is by enabling the modules that come installed with Filebeat. Inputs are essentially the location you will be choosing to process logs and metrics from.
Check you have correctly set-up the inputsįirst you are going to check that you have set the inputs for Filebeat to collect data from. This article will help you diagnose issues with your Filebeat configuration file. Are you using a configuration file in an alternative location Check your output contains your Logstash host and portģ. Check you have correctly set-up the inputsĢ.
0 kommentar(er)
