When using live reloading, why doesn't filebeat trigger live reloading immediately on first start?

Elastic Stack Beats
1

In the example below, "reload.period" specifies that the file is checked for changes once every 30 seconds. however, the first time you start filebeat you still have to wait 30 seconds for the configuration file to load, rather than loading it immediately

# filebeat.yml

filebeat.config.inputs:
  enabled: true
  path: configs/*.yml
  reload.enabled: true
  reload.period: 30s

# configs/input.yml
- type: tcp
  max_message_size: 10MiB
  host: "localhost:9000"

{"log.level":"info","@timestamp":"2021-11-18T01:13:57.665+0800","log.logger":"crawler","log.origin":{"file.name":"beater/crawler.go","file.line":71},"message":"Loading Inputs: 0","service.name":"filebeat","ecs.version":"1.6.0"}
.......
{"log.level":"info","@timestamp":"2021-11-18T01:14:27.673+0800","log.logger":"tcp","log.origin":{"file.name":"streaming/listener.go","file.line":120},"message":"Started listening for TCP connection","service.name":"filebeat","address":"localhost:9000","ecs.version":"1.6.0"}

I want to load the external configuration files immediately on first start and then check for changes every 30 seconds, is there any way to do this?

English is not my native language; please excuse typing errors.

Thanks

2

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