Filebeat : Exiting: No outputs are defined. Please define one under the output section

sourabhjain104 · April 7, 2021, 1:58pm

Hello All,
I am trying to send logs data from my local drive to logstash using filebeat 7.11.0.
I was able to do it successfully and also create index pattern in kibana.
I wanted to do some modification so I deleted my index pattern and try to send data again into elasticsearch using Filebeat ==>Logstash==>Elasticsearch but its not working.
I gone through many articles but not able to solve my issue. (I deleted entire filebeat and created again and also deleted registery folder)
My filebeat.yml is:-

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

Filebeat Reference | Elastic

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: true

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

paths:
- "C:/ELK/intralogs/test/*.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: '^[0-9]{4}-[0-9]{2}-[0-9]{2}'

Defines if the pattern set under pattern should be negated or not. Default is false.

multiline.negate: true

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

filestream is an experimental input. It is going to replace log input in the future.

type: filestream

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.

#prospector.scanner.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

============================== 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: 1
#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"]

================================= Dashboards =================================

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:

=============================== 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 `<user>:<pass>`.

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

Protocol - either `http` (default) or `https`.

#protocol: "https"

Authentication credentials - either API key or username/password.

#api_key: "id:api_key"
#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"

================================= Processors =================================

processors:

add_host_metadata:
when.not.contains.tags: forwarded
add_cloud_metadata: ~
add_docker_metadata: ~
add_kubernetes_metadata: ~

================================== Logging ===================================

Sets log level. The default log level is info.

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",

"publisher", "service".

#logging.selectors: ["*"]

============================= X-Pack Monitoring ==============================

Filebeat can export internal metrics to a central Elasticsearch monitoring

cluster. This requires xpack monitoring to be enabled in Elasticsearch. The

reporting is disabled by default.

Set to true to enable the monitoring reporter.

#monitoring.enabled: false

Sets the UUID of the Elasticsearch cluster under which monitoring data for this

Filebeat instance will appear in the Stack Monitoring UI. If output.elasticsearch

is enabled, the UUID is derived from the Elasticsearch cluster referenced by output.elasticsearch.

#monitoring.cluster_uuid:

Uncomment to send the metrics to Elasticsearch. Most settings from the

Elasticsearch output are accepted here as well.

Note that the settings should point to your Elasticsearch monitoring cluster.

Any setting that is not set is automatically inherited from the Elasticsearch

output configuration, so if you have the Elasticsearch output configured such

that it is pointing to your Elasticsearch monitoring cluster, you can simply

uncomment the following line.

#monitoring.elasticsearch:

============================== Instrumentation ===============================

Instrumentation support for the filebeat.

#instrumentation:
# Set to true to enable instrumentation of filebeat.
#enabled: false

# Environment in which filebeat is running on (eg: staging, production, etc.)
#environment: ""

# APM Server hosts to report instrumentation results to.
#hosts:
#  - http://localhost:8200

# API Key for the APM Server(s).
# If api_key is set then secret_token will be ignored.
#api_key:

# Secret token for the APM Server(s).
#secret_token:

================================= Migration ==================================

This allows to enable 6.7 migration aliases

#migration.6_to_7.enabled: true

My logstash.conf looks like below :-

input {

beats{
type => "test"
port=> "5044"
}
}
output {
elasticsearch {
hosts => "http://localhost:9200"
index => "plwlogbeat"
}
stdout { codec => rubydebug }
}

and the error I am getting is :-

C:\ELK\filebeat-7.11.0-windows-x86_64>filebeat.exe -e -c fields.yml
2021-04-07T15:44:55.757+0200 INFO instance/beat.go:660 Home path: [C:\ELK\filebeat-7.11.0-windows-x86_64] Config path: [C:\ELK\filebeat-7.11.0-windows-x86_64] Data path: [C:\ELK\filebeat-7.11.0-windows-x86_64\data] Logs path: [C:\ELK\filebeat-7.11.0-windows-x86_64\logs]
2021-04-07T15:44:55.757+0200 INFO instance/beat.go:668 Beat ID: cd8eb170-7035-4cd0-b51c-81024dbc6baa
2021-04-07T15:44:55.758+0200 INFO [beat] instance/beat.go:996 Beat info {"system_info": {"beat": {"path": {"config": "C:\ELK\filebeat-7.11.0-windows-x86_64", "data": "C:\ELK\filebeat-7.11.0-windows-x86_64\data", "home": "C:\ELK\filebeat-7.11.0-windows-x86_64", "logs": "C:\ELK\filebeat-7.11.0-windows-x86_64\logs"}, "type": "filebeat", "uuid": "cd8eb170-7035-4cd0-b51c-81024dbc6baa"}}}
2021-04-07T15:44:55.759+0200 INFO [beat] instance/beat.go:1005 Build info {"system_info": {"build": {"commit": "84c4d4c4034fcb49c1a318ccdc7311d70adee15b", "libbeat": "7.11.0", "time": "2021-02-08T22:42:11.000Z", "version": "7.11.0"}}}
2021-04-07T15:44:55.759+0200 INFO [beat] instance/beat.go:1008 Go runtime info {"system_info": {"go": {"os":"windows","arch":"amd64","max_procs":8,"version":"go1.14.14"}}}
2021-04-07T15:44:55.845+0200 INFO [beat] instance/beat.go:1012 Host info {"system_info": {"host": {"architecture":"x86_64","boot_time":"2021-04-07T09:01:04.88+02:00","name":"PORT-145","ip":["fe80::f9f7:1f19:cad5:c141/64","169.254.193.65/16","fe80::9c8b:a0ef:4837:4a5a/64","169.254.74.90/16","fe80::240d:8d2a:cef4:e2ef/64","192.168.56.1/24","fe80::d5f3:4e64:e909:f888/64","169.254.248.136/16","fe80::8dd2:c1ed:57c9:64/64","169.254.0.100/16","fe80::f13f:f5e5:d4e2:c90c/64","192.168.0.13/24","::1/128","127.0.0.1/8"],"kernel_version":"10.0.19041.867 (WinBuild.160101.0800)","mac":["68:f7:28:13:bf:68","0a:00:27:00:00:0a","0a:00:27:00:00:32","80:19:34:ad:74:b6","82:19:34:ad:74:b5","80:19:34:ad:74:b5"],"os":{"family":"windows","platform":"windows","name":"Windows 10 Pro","version":"10.0","major":10,"minor":0,"patch":0,"build":"19042.867"},"timezone":"CEST","timezone_offset_sec":7200,"id":"3a10ed6d-322b-4fec-8fb8-05100b2b5b7b"}}}
2021-04-07T15:44:55.846+0200 INFO [beat] instance/beat.go:1041 Process info {"system_info": {"process": {"cwd": "C:\ELK\filebeat-7.11.0-windows-x86_64", "exe": "C:\ELK\filebeat-7.11.0-windows-x86_64\filebeat.exe", "name": "filebeat.exe", "pid": 11588, "ppid": 12652, "start_time": "2021-04-07T15:44:53.887+0200"}}}
2021-04-07T15:44:55.847+0200 INFO instance/beat.go:304 Setup Beat: filebeat; Version: 7.11.0
2021-04-07T15:44:55.848+0200 INFO instance/beat.go:337 No outputs are defined. Please define one under the output section.
2021-04-07T15:44:55.848+0200 INFO instance/beat.go:437 filebeat stopped.
2021-04-07T15:44:55.848+0200 ERROR instance/beat.go:971 Exiting: No outputs are defined. Please define one under the output section.
Exiting: No outputs are defined. Please define one under the output section.

Can you please help me?
Thank you.

system · May 5, 2021, 3:58pm

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

Topic		Replies	Views
I have installed File beat 7.17.3 version on a Windows server, it is not getting the logs to the ELK Server Elasticsearch	2	210	August 11, 2022
Filebeat logs are not being send to logstash Beats filebeat	5	514	April 23, 2024
Can't send logs from filebeats to logstash Beats filebeat	5	4204	September 21, 2019
[monitoring] log/log.go:144 Non-zero metrics in the last 30s Beats	1	1547	February 13, 2019
Filebeat is running but not sending logs/data to logstash Beats filebeat	2	996	September 4, 2019

Filebeat : Exiting: No outputs are defined. Please define one under the output section

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:

Filebeat Reference | Elastic

For more available modules and options, please see the filebeat.reference.yml sample

configuration file.

============= 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.

Change to true to enable this input configuration.

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

Exclude lines. A list of regular expressions to match. It drops the lines that are

matching any regular expression from the list.

Include lines. A list of regular expressions to match. It exports the lines that are

matching any regular expression from the list.

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.

Optional additional fields. These fields can be freely picked

to add additional information to the crawled log files for filtering

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 [

Defines if the pattern set under pattern should be negated or not. Default is 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

filestream is an experimental input. It is going to replace log input in the future.

Change to true to enable this input configuration.

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

Exclude lines. A list of regular expressions to match. It drops the lines that are

matching any regular expression from the list.

Include lines. A list of regular expressions to match. It exports the lines that are

matching any regular expression from the list.

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.

Optional additional fields. These fields can be freely picked

to add additional information to the crawled log files for filtering

level: debug

review: 1

============================== Filebeat modules ==============================

Glob pattern for configuration loading

Set to true to enable config reloading

Period on which files under path should be checked for changes

== Elasticsearch template setting ===

============= 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.

The tags of the shipper are included in their own field with each

transaction published.

================================= Dashboards =================================

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.

=============================== 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.

The cloud.auth setting overwrites the output.elasticsearch.username and

output.elasticsearch.password settings. The format is <user>:<pass>.

================================== Outputs ===================================

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

---------------------------- Elasticsearch Output ----------------------------

Array of hosts to connect to.

Protocol - either http (default) or https.

Authentication credentials - either API key or username/password.

------------------------------ Logstash Output -------------------------------

The Logstash hosts

Optional SSL. By default is off.

List of root certificates for HTTPS server verifications

Certificate for SSL client authentication

Client Certificate Key

================================= Processors =================================

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.

The cloud.auth setting overwrites the `output.elasticsearch.username` and

`output.elasticsearch.password` settings. The format is `<user>:<pass>`.

Protocol - either `http` (default) or `https`.