Filebeat config error


(Amritesh Mishra) #1

}}
2018-07-10T14:14:14.001+0100 INFO instance/beat.go:225 Setup Beat: filebeat; Version: 6.3.1
2018-07-10T14:14:14.001+0100 DEBUG [beat] instance/beat.go:242 Initializing output plugins
2018-07-10T14:14:14.001+0100 DEBUG [processors] processors/processor.go:49 Processors:
2018-07-10T14:14:14.002+0100 DEBUG [publish] pipeline/consumer.go:120 start pipeline event consumer
2018-07-10T14:14:14.002+0100 INFO pipeline/module.go:81 Beat name: ukmr0dltmi002
2018-07-10T14:14:14.002+0100 INFO instance/beat.go:275 filebeat stopped.
2018-07-10T14:14:14.002+0100 ERROR instance/beat.go:691 Exiting: no modules or inputs enabled and configuration reloading disabled. What files do you want me to watch?
Exiting: no modules or inputs enabled and configuration reloading disabled. What files do you want me to watch?

Above error we are getting when we are loading a config file to send the logs from one server to another


(Carlos PĂ©rez Aradros) #2

Hi @amritesh_mishra,

Could you please share your filebeat.yml? It looks like if no input or modules are configured.

Best regards


(Amritesh Mishra) #3

###################### 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

Change to true to enable this input configuration.
enabled: false

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

/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
Mutiline 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 =====================================

These settings control loading the sample dashboards to the Kibana index. Loading
the dashboards is disabled by default and can be enabled either by setting the
options here, or by using the -setup CLI flag or the setup command.
#setup.dashboards.enabled: false

The URL from where to download the dashboards archive. By default this URL
has a value which is computed based on the Beat name and version. For released
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: "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: "elastic"
#password: "changeme"

#----------------------------- Logstash output --------------------------------
output.logstash:
#The Logstash hosts
hosts: ["localhost:5044"]

Optional SSL. By default is off.
List of root certificates for HTTPS server verifications
#ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]

Certificate for SSL client authentication
#ssl.certificate: "/etc/pki/client/cert.pem"

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

#================================ Logging =====================================

Sets log level. The default log level is info.
Available log levels are: error, warning, info, debug
Available log levels are: error, warning, info, debug
#logging.level: debug

At debug level, you can selectively enable logging only for some components.
To enable all selectors use [""]. Examples of other selectors are "beat",
"publish", "service".
#logging.selectors: ["
"]


(Wahyu Putra) #4

Could you change enabled: false become enabled: true ?


(system) #5

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.