Open mark54g opened 4 years ago
Pinging @elastic/integrations (Team:Integrations)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
@mark54g , @kaiyan-sheng . This is still a problem and I'm hoping this ticket gets reopened by a human.
I was the person that worked with elastic support initially to report this
Hi @PresGas, could you post with more info on this issue please? Thanks!!
I opened a case that created this ticket.
It is still impacting filebeat version 7.10.x and likely newer since this was auto closed without any human interaction. Thanks for reopening!
Please let me know if I can provide anything. The key bits for reproducing the issue is generally to have the filebeat.yml configed with this snippet:
filebeat.config.modules:
# Glob pattern for configuration loading
path: ${path.config}/modules.d/*.yml
reload.enabled: true
reload.period: 30m
And then you should see some delays either going to logstash/kibana or putting filebeat to debug mode and watching the logs there.
What's the use case for a 30m
reload interval? Normally I've seen this in the range of seconds to a minute. In that case the initial delay is less obvious.
The code does appear to wait the full reload interval before triggering the initial load.
@andrewkroh - I have since switched roles and not longer on the elastic related project prompting this issue.
IIRC - one of those was likely a default? I honestly have slept since then.
Nevertheless, an initial start should not wait that long to load those settings. An initial start should load the settings immediately.
@andrewkroh
The same issue still occurs on metricbeat 8.5.3 Our use case is set at
reload.period: 300s
If the behaviour of waiting the same time before the initial loading is correct. This should be noted in the doco?
Hi! We just realized that we haven't looked into this issue in a while. We're sorry!
We're labeling this issue as Stale
to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1
.
Thank you for your contribution!
👍 This issue burned my team today! Would be nice if, at a minimum, the docs reflected that live reload
will delay the initial log shipping by reload.period
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)
Various beats seem to have an issue where
reload.enabled
being set to true will cause a delay that is roughly equal to thereload.period
Confirmed with master branch of metricbeat per @kaiyan-sheng