USE Filebeat 6.2 can't work with kafka


(Richard2017) #1

I installed Filebeat 6.2 ,and want to use filebeat modules , filebeat ->kafka 0.10.1->logstash -> ES.

filebeat.yml:
output.kafka:
enabled: true
hosts: ["10.2.33.33:9092","10.2.33.34:9092","10.2.33.35:9092"]
topic: systemoslog
required_acks: 1
compression: gzip
max_message_bytes: 1000000
client_id: histest

When i run "filebeat -e setup",i got below error ,because i setup kafka output,can't setup ES output again,could you me check out?
[root@his-test filebeat]# filebeat -e setup
2018-06-05T13:36:20.795+0800 INFO instance/beat.go:468 Home path: [/usr/share/filebeat] Config path: [/etc/filebeat] Data path: [/var/lib/filebeat] Logs path: [/var/log/filebeat]
2018-06-05T13:36:20.795+0800 DEBUG [beat] instance/beat.go:495 Beat metadata path: /var/lib/filebeat/meta.json
2018-06-05T13:36:20.796+0800 INFO instance/beat.go:475 Beat UUID: 37b03a9f-4b5a-4519-a3c7-dde66fa5a881
2018-06-05T13:36:20.796+0800 INFO instance/beat.go:213 Setup Beat: filebeat; Version: 6.2.4
2018-06-05T13:36:20.796+0800 DEBUG [beat] instance/beat.go:230 Initializing output plugins
2018-06-05T13:36:20.796+0800 DEBUG [processors] processors/processor.go:49 Processors:
2018-06-05T13:36:20.796+0800 DEBUG [kafka] kafka/kafka.go:119 initialize kafka output
2018-06-05T13:36:20.796+0800 INFO pipeline/module.go:76 Beat name: his-test
2018-06-05T13:36:20.796+0800 ERROR instance/beat.go:667 Exiting: Template loading requested but the Elasticsearch output is not configured/enabled
Exiting: Template loading requested but the Elasticsearch output is not configured/enabled


(Harsh Bajaj) #2

HI @richard2017,

Could you please share you full filebeat.yml file here for more understanding this issue?

This below error is showing you have configured somewhere template configuration which is invalid for kafka and valid for ES only. Please check and remove if you configured.

Regards,


(Richard2017) #3

#=========================== Filebeat prospectors =============================

filebeat.prospectors:

Each - is a prospector. Most options can be set at the prospector level, so

you can use different prospectors for various configurations.

Below are the prospector specific configurations.

  • type: log

    Change to true to enable this prospector 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: "10.2.87.76: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 <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: ["10.2.87.76:9200","10.2.87.77:9200","10.2.87.78:9200"]

index: "system-%{[beat.version]}-%{+yyyy.MM.dd}"

Optional protocol and basic auth credentials.

#protocol: "https"
#username: "elastic"
#password: "changeme"
#setup.template.name: "system"
#setup.template.pattern: "system-"
#setup.dashboards.index: "system-
"
#setup.template.overwrite: true
#setup.template.enabled: false
#----------------------------- Logstash output --------------------------------
#output.logstash:

The Logstash hosts

hosts: ["10.2.69.210: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

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: ["*"]
output.kafka:
enabled: true
hosts: ["10.2.33.33:9092","10.2.33.34:9092","10.2.33.35:9092"]
topic: systemoslog
required_acks: 1
compression: gzip
max_message_bytes: 1000000
client_id: histest


(Richard2017) #4

I enabled filebeat module "system“


(Richard2017) #6

[root@his-test filebeat]# filebeat setup -e
2018-06-05T15:14:46.754+0800 INFO instance/beat.go:468 Home path: [/usr/share/filebeat] Config path: [/etc/filebeat] Data path: [/var/lib/filebeat] Logs path: [/var/log/filebeat]
2018-06-05T15:14:46.755+0800 DEBUG [beat] instance/beat.go:495 Beat metadata path: /var/lib/filebeat/meta.json
2018-06-05T15:14:46.755+0800 INFO instance/beat.go:475 Beat UUID: 37b03a9f-4b5a-4519-a3c7-dde66fa5a881
2018-06-05T15:14:46.755+0800 INFO instance/beat.go:213 Setup Beat: filebeat; Version: 6.2.4
2018-06-05T15:14:46.755+0800 DEBUG [beat] instance/beat.go:230 Initializing output plugins
2018-06-05T15:14:46.755+0800 DEBUG [processors] processors/processor.go:49 Processors:
2018-06-05T15:14:46.755+0800 DEBUG [kafka] kafka/kafka.go:119 initialize kafka output
2018-06-05T15:14:46.756+0800 INFO pipeline/module.go:76 Beat name: his-test
2018-06-05T15:14:46.757+0800 ERROR instance/beat.go:667 Exiting: Template loading requested but the Elasticsearch output is not configured/enabled
Exiting: Template loading requested but the Elasticsearch output is not configured/enabled


(Pjanzen) #7

Because your output is kafka you cannot run filebeat setup -e you need to load the templates manually. PLease read this


(system) #8

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