Filebeat stopped sending the log entries

Hello ,

We have a typical issue here. Filebeat suddenly stopped sending the log entries and i can see the below message in the log.

2021-01-05T14:58:50.314+0100    INFO    [monitoring]    log/log.go:144  Non-zero
 metrics in the last 30s        {"monitoring": {"metrics": {"beat":{"cpu":{"syst
em":{"ticks":1937,"time":{"ms":141}},"total":{"ticks":4312,"time":{"ms":220},"va
lue":4312},"user":{"ticks":2375,"time":{"ms":79}}},"handles":{"open":183},"info"
:{"ephemeral_id":"4712218c-147a-4c2e-aa10-3e605837612f","uptime":{"ms":363052}},
"memstats":{"gc_next":70696576,"memory_alloc":58147480,"memory_total":532591216,
"rss":4096}},"filebeat":{"harvester":{"open_files":13,"running":13}},"libbeat":{
"config":{"module":{"running":0}},"output":{"read":{"bytes":36}},"pipeline":{"cl
ients":1,"events":{"active":8213}}},"registrar":{"states":{"current":152}}}}}

I have not made any changes for filebeat as well. After restarting the filebeat also i don't see any luck.

Filebeat.yml

###################### 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
  enabled: true
  paths:
    - E:/logging/CompassFeedbackAPI/*
    - E:/logging/CustomPropertiesAPI/*
    - E:/logging/InteractionAPI/*
    - E:/logging/Kafka/Kafka_consumer*
    - E:/logging/Kafka/Kafka_retry*
    - E:/logging/MasterDataApi/*
    - E:/logging/OSVFacade/V1/*
    - E:/logging/TDNotification/V3/*
    - E:/logging/VeDocAPI/*
  # 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']
  #exclude_lines: ['SBL-DAT-00327','SBL-UIF-00401','SBL-DAT-60171','^TaskConfigSval','^TaskConfigStat','^TaskConfig']
  # Include lines. A list of regular expressions to match. It exports the lines that are
  # matching any regular expression from the list.
  include_lines: ['^[0-9]{4}-[0-9]{2}-[0-9]{2}']
  # 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$']
  #exclude_files: ['FSMSrvr*','ServerMgr*','SvrTblCleanup*','SvrTaskPersist*','DbXtract*','GenNewDb*','RepAgent*','SynchMgr*','AsgnBatch*','GenTrig*']
  #exclude_files: ['EIM*','FSMSrvr*','ServerMgr*','SRBroker*','SRProc*','SvrTblCleanup*','SvrTaskPersist*','SCBroker*','CommSessionMgr*','DbXtract*','GenNewDb*','RepAgent*','SynchMgr*','AsgnSrvr*','AsgnBatch*','GenTrig*']
  # 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: '^[0-9]{4}-[0-9]{2}-[0-9]{2}'
  # Defines if the pattern set under pattern should be negated or not. Default is false.
  multiline.negate: true
  # 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
  tail_files: false
  ignore_older: 5h
  scan_frequency: 2s
  #clean_inactive: 25h
  close_inactive: 15m
filebeat.registry_flush: 60s
#============================= 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: PROD
#============================== 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: "localhost:5601"
  # Kibana Space ID
  # ID of the Kibana Space into which the dashboards should be loaded. By default,
  # the Default Space will be used.
  #space.id:
#============================= 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: ["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: ["53.XXX.XX.XX:6044"]
  worker: 4
  slow_start: true
  bulk_max_size: 2048
  # 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"
#================================ Processors =====================================
# Configure processors to enhance or manipulate events generated by the beat.
queue.mem:
  events: 8192
  flush.min_events: 2048
  flush.timeout: 5s
  
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: info
logging.files.rotateeverybytes: 52428800
# 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: false
# 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: 

Kindly help me please.

Hi!

Do you see any other log message? Do you run Filebeat in debug mode? This would be helpful so as to check if there is anything failing.

C.