I have setup the filebeat to send logs to logstash . When I first started the filebeat it sent the data which I could see in kibana. (Data from filebeat to logstash to elasticsearch then to kibana) . But when when I stopped and started the filebeat again I keep getting the below message in the logs
2017-07-16T09:04:21Z INFO No non-zero metrics in the last 30s
2017-07-16T09:01:51Z INFO Setup Beat: filebeat; Version: 5.5.0
2017-07-16T09:01:51Z INFO Max Retries set to: 3
2017-07-16T09:01:51Z INFO Activated logstash as output plugin.
2017-07-16T09:01:51Z INFO Publisher name: ip-10-0-0-228
2017-07-16T09:01:51Z INFO Flush Interval set to: 1s
2017-07-16T09:01:51Z INFO Max Bulk Size set to: 2048
2017-07-16T09:01:51Z INFO filebeat start running.
2017-07-16T09:01:51Z INFO Registry file set to: /var/lib/filebeat/registry
2017-07-16T09:01:51Z INFO Loading registrar data from /var/lib/filebeat/registry
2017-07-16T09:01:51Z INFO States Loaded from registrar: 7
2017-07-16T09:01:51Z INFO Loading Prospectors: 1
2017-07-16T09:01:51Z INFO Start sending events to output
2017-07-16T09:01:51Z INFO Starting Registrar
2017-07-16T09:01:51Z INFO Prospector with previous states loaded: 0
2017-07-16T09:01:51Z INFO Starting prospector of type: log; id: 14941145153724516414
2017-07-16T09:01:51Z INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2017-07-16T09:01:51Z INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2017-07-16T09:02:21Z INFO No non-zero metrics in the last 30s
2017-07-16T09:02:51Z INFO No non-zero metrics in the last 30s
2017-07-16T09:03:21Z INFO No non-zero metrics in the last 30s
2017-07-16T09:03:51Z INFO No non-zero metrics in the last 30s
2017-07-16T09:04:21Z INFO No non-zero metrics in the last 30s
Configuration of my filebeat
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.
paths:
- /var/log/xxxx/logging.log
- /var/log/xxxx/logging.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
#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
#================================ 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
#================================ Outputs =====================================
# Configure what outputs to use when sending the data collected by the beat.
# Multiple outputs may be used.
#-------------------------- Elasticsearch output ------------------------------
#output.elasticsearch:
# Array of hosts to connect to.
#hosts: ["localhost:9200"]
# Optional protocol and basic auth credentials.
#protocol: "https"
#username: "elastic"
#password: "changeme"
#----------------------------- Logstash output --------------------------------
output.logstash:
# The Logstash hosts
hosts: ["x.x.x.x: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: 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: ["*"]
The logstash logs
[2017-07-16T09:01:53,326][INFO ][logstash.outputs.elasticsearch] New Elasticsearch output {:class=>"LogStash::Outputs::ElasticSearch", :hosts=>[#<Java::JavaNet::URI:0x5050a2d7>]}
[2017-07-16T09:01:53,331][INFO ][logstash.pipeline ] Starting pipeline {"id"=>"main", "pipeline.workers"=>2, "pipeline.batch.size"=>125, "pipeline.batch.delay"=>5, "pipeline.max_inflight"=>250}
[2017-07-16T09:01:53,651][INFO ][logstash.inputs.beats ] Beats inputs: Starting input listener {:address=>"0.0.0.0:5044"}
[2017-07-16T09:01:53,684][INFO ][logstash.pipeline ] Pipeline main started
[2017-07-16T09:01:53,752][INFO ][logstash.agent ] Successfully started Logstash API endpoint {:port=>9600}
The log files are getting updated so there no issues with the logs which I am monitoring.