Is config reload logged?

Hi, I am using config reload on logs like described here:
https://www.elastic.co/guide/en/beats/filebeat/current/_live_reloading.html

#=========================== Filebeat inputs =============================
# Enable filebeat config reloading
filebeat.config:
  inputs:
    enabled: true
    path: inputs.d/*.yml
    reload.enabled: true
    reload.period: 30s

How can I see in filebeat logs when the reload has been done successfully?

Inside that inputs.d folder I have files with content like this:

- type: log

  enabled: true

  paths:
    - /var/log/myapp/session-fail.log

  encoding: windows-1252

  fields:
    logType: session_fail
    instance.name: dev4

  fields_under_root: true
  #ignore_older: 0

  scan_frequency: 1s


  multiline.pattern: ^\[[\d \-\.\,:]{23}\] ([\d+\.]{4}|unknown)
  multiline.negate: true
  multiline.match: after

  multiline.max_lines: 10000

  # After the defined timeout, an multiline event is sent even if no new pattern was found to start a new event
  # Default is 5s.
  multiline.timeout: 5s

Thanks Andreas

A simple way would be to add a new input config and then look at filebeat log (/var/log/filebeat/filebeat -- log location on Linux) and check if harverster started for the files mentioned in the additional config.

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