filebeat 没有抓取到docker容器日志

docker-compose部分配置：

  webmvc-sleuth-2:

    build: ./webmvc-sleuth-2

    image: yokv/webmvc-sleuth-2

    container_name: webmvc-sleuth-2

    ports:

      - 8083:8080

    networks:

      - appnet

  filebeat-docker:

    image: yokv/filebeat:6.2.4

    container_name: filebeat-docker

    environment:

      - xpack.security.enabled=false

    networks:

      - elk_elk-net

    volumes:

      - ./webmvc-sleuth-2/beat/filebeat.yml:/usr/share/filebeat/filebeat.yml

      - /var/run/docker.sock:/var/run/docker.sock

filebeat配置:

###################### 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/e ... .html



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

# configuration file.





filebeat.autodiscover:

  providers:

    - type: docker

      enabled: true

      templates:

        - condition:

            equals:

              docker.container.image: yokv/webmvc-sleuth-2

          config:

            - type: docker

              containers.ids:

                - "${data.docker.container.id}"

              exclude_lines: ["^\\s+[\\-`('.|_]"]  # drop asciiart lines





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

#  tags: ["webmvc-sleuth-0"]

#  encoding: utf-8

#  json.keys_under_root: true

#  json.overwrite_keys: true

#  paths:

#    - /data/logs/*.log



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



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



  # Optional protocol and basic auth credentials.

  #protocol: "https"

  #username: "elastic"

  #password: "changeme"



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

output.logstash:

  # The Logstash hosts

   hosts: ["logstash:5052"]



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



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

xpack.monitoring.enabled: true



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

# Elasticsearch output are accepted here as well. Any setting that is not set is

# automatically inherited from the Elasticsearch output configuration, so if you

# have the Elasticsearch output configured, you can simply uncomment the

# following line.

xpack.monitoring.elasticsearch:

  hosts: ["elasticsearch:9200"]

filebeat 日志：

2018-05-07T16:22:39.388Z    INFO    instance/beat.go:468    Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]

2018-05-07T16:22:39.389Z    INFO    instance/beat.go:475    Beat UUID: 4ddcfaae-98bf-485b-89ce-3c6c092d610b

2018-05-07T16:22:39.389Z    INFO    instance/beat.go:213    Setup Beat: filebeat; Version: 6.2.4

2018-05-07T16:22:39.389Z    INFO    pipeline/module.go:76    Beat name: 8b85697806cb

2018-05-07T16:22:39.390Z    INFO    elasticsearch/client.go:145    Elasticsearch url: http://elasticsearch:9200

2018-05-07T16:22:39.390Z    INFO    [monitoring]    log/log.go:97    Starting metrics logging every 30s

2018-05-07T16:22:39.390Z    INFO    elasticsearch/elasticsearch.go:154    Start monitoring endpoint init loop.

2018-05-07T16:22:39.391Z    INFO    instance/beat.go:301    filebeat start running.

2018-05-07T16:22:39.391Z    INFO    registrar/registrar.go:73    No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.

2018-05-07T16:22:39.393Z    INFO    elasticsearch/elasticsearch.go:177    Stop monitoring endpoint init loop.

2018-05-07T16:22:39.393Z    INFO    elasticsearch/elasticsearch.go:183    Start monitoring metrics snapshot loop.

2018-05-07T16:22:39.482Z    INFO    registrar/registrar.go:110    Loading registrar data from /usr/share/filebeat/data/registry

2018-05-07T16:22:39.482Z    INFO    registrar/registrar.go:121    States Loaded from registrar: 0

2018-05-07T16:22:39.482Z    WARN    beater/filebeat.go:261    Filebeat is unable to load the Ingest Node pipelines for the configured modules because the Elasticsearch output is not configured/enabled. If you have already loaded the Ingest Node pipelines or are using Logstash pipelines, you can ignore this warning.

2018-05-07T16:22:39.482Z    INFO    crawler/crawler.go:48    Loading Prospectors: 0

2018-05-07T16:22:39.482Z    INFO    crawler/crawler.go:82    Loading and starting Prospectors completed. Enabled prospectors: 0

2018-05-07T16:22:39.486Z    INFO    autodiscover/autodiscover.go:77    Starting autodiscover manager

2018-05-07T16:22:39.700Z    WARN    [cfgwarn]    docker/prospector.go:25    EXPERIMENTAL: Docker prospector is enabled.

2018-05-07T16:22:39.700Z    INFO    log/prospector.go:111    Configured paths: [/var/lib/docker/containers/4847a715b1e4a63cd10daa05e62957c6b513aa20220be471789e103e1da56a30/*.log]

2018-05-07T16:22:39.700Z    INFO    autodiscover/autodiscover.go:145    Autodiscover starting runner: prospector [type=docker, ID=16047994292498624578]

在宿主机上发现存在日志文件，并且有日志，但是日志没有抓取到
/var/lib/docker/containers/4847a715b1e4a63cd10daa05e62957c6b513aa20220be471789e103e1da56a30/4847a715b1e4a63cd10daa05e62957c6b513aa20220be471789e103e1da56a30.log