Filebeat can't send logs to Graylog3

Filebeat on the remote server can’t send logs to graylog3 ,when i restarted all graylogservices the issue still exist ,when i reboot graylog server the issue solved and i can see logs normally:
I use filebeat 5.6.16 on remote server
I use graylog3,elasticsearch 5.6.16 ,logstash 5.6.16 on local server

i received below error in filebeat log on the remote server:

2019-06-26T18:36:54+02:00 INFO Harvester started for file: /home/dwh/GrayLog/log/ProcessOrderSample33.log
2019-06-26T18:36:57+02:00 ERR Failed to publish events (host:, caused by: read tcp> read: connection reset by peer
2019-06-26T18:36:57+02:00 INFO Error publishing events (retrying): read tcp> read: connection reset by peer
2019-06-26T18:37:13+02:00 INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=1 filebeat.harvester.running=1 filebeat.harvester.started=1 libbeat.logstash.call_count.PublishEvents=2 libbeat.logstash.publish.read_bytes=6 libbeat.logstash.publish.read_errors=1 libbeat.logstash.publish.write_bytes=3843 libbeat.logstash.published_and_acked_events=35 libbeat.logstash.published_but_not_acked_events=35 libbeat.publisher.published_events=35 registrar.states.current=1 registrar.states.update=36 registrar.writes=1

2- I see this warn in graylog3 server.log file:
2019-06-26T18:20:19.499+02:00 WARN [AbstractTcpTransport] receiveBufferSize (SO_RCVBUF) for input Beats2Input{title=filebeat,, nodeId=a254b10c-df99-4dae-be94-1845b87e387f} (channel [id: 0x2d767fd7, L:/]) should be 1048576 but is 2097152.

how did you send messages? You talk of Logstash and filebeat - what is the way a message should go. Means how do you have this configured.

thanks jan for your reply ,i installed filebeat on remote server and configured logstash output to the graylog server:

Also ,I configured input on Graylog as below:

  • bind_address:

  • no_beats_prefix:


  • number_worker_threads:


  • override_source:

  • port:


  • recv_buffer_size:


  • tcp_keepalive:


  • tls_cert_file:

  • tls_client_auth:


  • tls_client_auth_cert_file:

  • tls_enable:


  • tls_key_file:

  • tls_key_password:

logstash configuration on graylog server

Sample Logstash configuration for creating a simple

Beats -> Logstash -> Elasticsearch pipeline.

input {
beats {
port => 5044

output {
elasticsearch {
hosts => [“”]
index => “%{[@metadata][beat]}-%{[@metadata][version]}-%{+YYYY.MM.dd}”
#user => “elastic”
#password => “changeme”

filebeat configuration on remote server:
###################### Filebeat Configuration Example #########################

This file is an example configuration file highlighting only the most common

options. The filebeat.full.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 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.

  • input_type: log

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

    #- /var/log/*.log

    • /home/dwh/GrayLog/log/*.log
    • /home/tibuser/DeploymentPackages/OMS-I/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 field can be freely picked

    to add additional information to the crawled log files for filtering


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

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

#tags: [“service-X”, “web-tier”]

Optional fields that you can specify to add additional information to the



env: staging

#================================ Outputs =====================================

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

Multiple outputs may be used.

#dashboards.enabled: true
#-------------------------- Elasticsearch output ------------------------------

Array of hosts to connect to.

#hosts: [“localhost:9200”]

Optional protocol and basic auth credentials.

#protocol: “https”
#username: “elastic”
#password: “changeme”

#----------------------------- Logstash output --------------------------------

The Logstash hosts

hosts: “”

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: critical, 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: ["*"]

sorry to say - but you have one moving part wrong in your setup.

You would send from filebeat direct to Graylog. No logstash is needed - and special if you output to elasticsearch direct Graylog will not know of the messages you ingest.

oh - and if you format your post proper it would be better readable.

Thanks Jan for your reply.Could you please guide me to configure filebeat to send directly to Graylog?.I mean Filebeat has only two output parts ,one for elasticsearch and one for logstash!

yes - you use the output called logstash and point that to the beats input of Graylog.

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