Filebeat to Logstash (in Elastic Stack) over LAN


(Chadmando) #1

Hello, looking for some help pushing logs from Ubuntu 18 to an elastic static installation running on the same subnet.

Filebeat on Ubuntu is version 6.6.0 doesn't show publishing errors or other errors. When I run with the -e flag all seems good. .yml file has correct output setup, IP, port, etc. service is running.

Elastic Stack install is 6.4.1. Firewall is open for port 5044 and logstash can read local using its local filebeat.

I have tried capturing traffic from the source server but i can't seem to pickup any outbound traffic with a destination of the elastic stack on port 5044.

Is this a versioning issue? Is there something obvious that I am not seeing to get filebeat unstuck?

Any help is appreciated


(Lucio Palmieri) #2

Hi @chadmando,
to make sure the filebeat configuration is correct, run the command:
$ sudo filebeat test config
and check the command output is
Config OK
then
$ sudo cat /etc/filebeat/filebeat.yml
and copy and paste the output in this Topic please.


(Chadmando) #3

Thank you for the response.

results of test config = Config OK

Here is the filebeat.yml file contents:

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

  # Paths that should be crawled and fetched. Glob based paths.
  paths:
    - /var/log/my.meraki.net/*/*.log
    - /var/log/192.168.200.1/*/*.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 =====================================
# 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: "192.168.100.24:5601"


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

  # Enabled ilm (beta) to use index lifecycle management instead daily indices.
  #ilm.enabled: false

  # Optional protocol and basic auth credentials.
  #protocol: "https"
  #username: "elastic"
  #password: "changeme"

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


#================================ Processors =====================================

# Configure processors to enhance or manipulate events generated by the beat.

processors:
  - add_host_metadata: ~
  - add_cloud_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",
# "publish", "service".
logging.selectors: ["publish"]

(Lucio Palmieri) #4

Hi @chadmando ,
to make sure the logstash port is open, run the command
$ sudo nmap -p 5044 -Pn 192.168.100.24
and post the output please

if nmap is not present in you system, install it
$ sudo apt-get install nmap


(Chadmando) #5

5044/tcp open ... Host is up. All good on that front. Could it be an issue with the logstash configuration?


(Lucio Palmieri) #6

of course yes
post the logstash configuration


(Chadmando) #7

just to confirm. I did check with netstat and there is an established connection between the filebeat endpoint and 192.168.100.24:5044


(Lucio Palmieri) #8

the logstah output is elasticsearch?

check the free disk space on output host with
$df -h

you should also check the logstash log


(Chadmando) #9

disk space is ok. 16+GB free space.

This is a test installation. The target logstash is sending to full ELK installation. I am using a preconfigured appliance specifically setup to ingest logs for the purposes of security analysis. If I run a sudo service logstash status the return doesn't show the configuration file used to start logstash. Instead it shows a jvm type file. I have a folder of config files for logstash depending on the source.

Is there anything specific I can send to provide more insight into the logstash setup and configuration that would be helpful?


(system) closed #10

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