ELK Docker with Filebeat Dashboard Problem


(André Vertgewall) #1

Hello together,

I'm trying to setup an ELK stack using the docker elk (https://github.com/deviantony/docker-elk).
For testing purpose I use two virtual machines running ubuntu. One with the ELK docker and one sending the logs using filebeat

yaml:

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

  # 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: "192.168.1.93: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: ["192.168.1.93:9200"]

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

I removed the lines underneath Easticsearch Output, as they are commented out and Body is only allowed to have 7000 chars.

Now the Problem:
I get all data under Discovery, but if I try to use the preconfigured Dashboards I only get No Result.
Nothing changed from default values.
Index-Pattern is: filebeat-*.
Any Ideas?


(Andrew Kroh) #2

What Filebeat dashboard are you trying to use? The dashboards provided with Filebeat are associated with modules. So you need to be using a Filebeat module.


(André Vertgewall) #3

For ex the ssh login board.
The tutorial said, they should work out of the box, or did I miss something?


(Andrew Kroh) #4

Do you have the system module enabled?

It looks like you enabled the prospector from the default config. You'll want to disable that since your going to use the system module.

- type: log

  # Change to true to enable this prospector configuration.
  enabled: true <---- Turn this off.

(André Vertgewall) #5
Enabled:
system

Disabled:
apache2
auditd
icinga
kafka
logstash
mysql
nginx
osquery
postgresql
redis
traefik

changing enabled: true to falls and it doesn't send data anymore.
Still no logs in Dashboard


(Andrew Kroh) #6

I did a quick test on my machine with a clean install of ES, Kibana, and Filebeat. After bringing up ES and Kibana, all I needed to do was run:

tar xf filebeat-6.2.2-darwin-x86_64.tar.gz
cd filebeat-6.2.2-darwin-x86_64
./filebeat modules enable system
./filebeat setup -e
./filebeat -e

Then opened the [Filebeat System] Syslog dashboard in Kibana. I set the Timepicker to "Last 7 days" and I had data. My machine isn't using UTC for its timezone so I would need to use the convert_timezone option since syslog does not include the timezone is its timestamps.

Is your machine using UTC timezone? If not, try expanding the timepacker range.

If that doesn't work then check the filebeat log output for errors. You can also enable debug with logging.level: debug to get more verbose output from Filebeat.


(André Vertgewall) #7

Thanks, I started all over and now it's working :slight_smile:
Thanks for your help.

Another Question: i want to monitor my laravel logs. So i've added the logpath to the config. Is there anything i need to do before it is running?


(system) #8

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