Filebeat is not sending the log data to Elasticsearch


(Francisco Yañez) #1

Francisco_YanezFrancisco Yañez
22m

Hello I have just installed Elastic stack on my server and all is working fine but on the client I am trying to ship logs and it is just not working I have read quite a few posts and change a few things on the config file but nothing is working. I am posting my config file just in case anyone can see the error if why Filebeat is not working

###################### Filebeat Configuration Example #########################
This file is an example configuration file highlighting only the most common
options. The filebeat.reference.yml file from the same directory contains all the
supported options with more comments. You can use it as a reference.
You can find the full configuration reference here:
https://www.elastic.co/guide/en/beats/filebeat/index.html
For more available modules and options, please see the filebeat.reference.yml sample
configuration file.

#=========================== Filebeat inputs =============================

filebeat.inputs:
Each - is an input. Most options can be set at the input level, so
you can use different inputs for various configurations.
Below are the input specific configurations.

type: log

document_type: syslog
Change to true to enable this input configuration.

enabled: true
Paths that should be crawled and fetched. Glob based paths.

paths:
- /var/log/auth.log
- /var/log/syslog
- /var/log/*.log

#- c:\programdata\elasticsearch\logs*
Exclude lines. A list of regular expressions to match. It drops the lines that are
matching any regular expression from the list.

#exclude_lines: ['^DBG']
Include lines. A list of regular expressions to match. It exports the lines that are
matching any regular expression from the list.

#include_lines: ['^ERR', '^WARN']
Exclude files. A list of regular expressions to match. Filebeat drops the files that
are matching any regular expression from the list. By default, no files are dropped.

#exclude_files: ['.gz$']
Optional additional fields. These fields can be freely picked
to add additional information to the crawled log files for filtering

#fields:
level: debug
review: 1
Multiline options
Multiline can be used for log messages spanning multiple lines. This is common
for Java Stack Traces or C-Line Continuation
The regexp Pattern that has to be matched. The example pattern matches all lines starting with [

#multiline.pattern: ^[
Defines if the pattern set under pattern should be negated or not. Default is false.

#multiline.negate: false
Match can be set to "after" or "before". It is used to define if lines should be append to a pattern
that was (not) matched before or after or as long as a pattern is not matched based on negate.
Note: After is the equivalent to previous and before is the equivalent to to next in Logstash

#multiline.match: after

#============================= Filebeat modules ===============================

filebeat.config.modules:
Glob pattern for configuration loading

path: ${path.config}/modules.d/*.yml
Set to true to enable config reloading

reload.enabled: false
Period on which files under path should be checked for changes

#reload.period: 10s

#==================== Elasticsearch template setting ==========================

setup.template.settings:
index.number_of_shards: 3
#index.codec: best_compression
#_source.enabled: false

#================================ General =====================================
The name of the shipper that publishes the network data. It can be used to group
all the transactions sent by a single shipper in the web interface.

#name:
The tags of the shipper are included in their own field with each
transaction published.

#tags: ["service-X", "web-tier"]
Optional fields that you can specify to add additional information to the
output.

#fields:
env: staging

#============================== Dashboards =====================================
versions, this URL points to the dashboard archive on the artifacts.elastic.co
website.

#setup.dashboards.url:

#============================== Kibana =====================================
Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
This requires a Kibana endpoint configuration.

setup.kibana:

#Kibana Host
Scheme and port can be left out and will be set to the default (http and 5601)
In case you specify and additional path, the scheme is required: http://localhost:5601/path
IPv6 addresses should always be defined as: https://[2001:db8::1]:5601

host: "http://localhost:5601"

#============================= Elastic Cloud ==================================
These settings simplify using filebeat with the Elastic Cloud (https://cloud.elastic.co/).
The cloud.id setting overwrites the output.elasticsearch.hosts and
setup.kibana.host options.
You can find the cloud.id in the Elastic Cloud web UI.

#cloud.id:
The cloud.auth setting overwrites the output.elasticsearch.username and
output.elasticsearch.password settings. The format is :.

#cloud.auth:

#================================ Outputs =====================================
Configure what output to use when sending the data collected by the beat.

#-------------------------- Elasticsearch output ------------------------------
output.elasticsearch:
Array of hosts to connect to.

hosts: ["localhost:9200"]
Optional protocol and basic auth credentials.

#protocol: "https"
#username: ""
#password: "**"

#----------------------------- Logstash output --------------------------------
#output.logstash:
The Logstash hosts
hosts: ["localhost:5044"]
bulk_max_size: 1024
Optional SSL. By default is off.

#tls:
List of root certificates for HTTPS server verifications
List of root certificates for HTTPS server verifications

#ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]
certificate_authorities: ["/etc/pki/tls/certs/logstash-forwarder.crt"]
Certificate for SSL client authentication

#ssl.certificate: "/etc/pki/client/cert.pem"
Client Certificate Key

#ssl.key: "/etc/pki/client/cert.key"