Craig MacKenzie

Looks like we are still seeing this in some of our own scale tests on VMs: https://github.com/elastic/elastic-agent/issues/1790#issuecomment-1329177230

> a bit of a wild thought, I haven't any data to support it, but could it be related to the panic: close of closed channel... we've seen, but so...

Closing, we have removed use of these lock files when Beats are run under agent in 8.7.

Manually deleting the lock files before Filebeat starts should be the work around here. Wrapping agent or filebeat in a script that unconditionally deletes them is one way, they aren't...

Closing this, please reopen if you want to continue development. Also note that Functionbeat will reach End of Support on October 18, 2023, and is being replaced by the Elastic...

The documentation might be out of sync with the code here, since our code has the default for Logstash set to `LoadBalance: false`: https://github.com/elastic/beats/blob/e322104a8cc25b420f7764a50a9f801e7cba6aa0/libbeat/outputs/logstash/config.go#L53-L55 > As of [8.10, the default](https://www.elastic.co/guide/en/beats/filebeat/8.10/logstash-output.html#loadbalance)...

Stumbled on this through the linked linter PR: Cool! I am excited to see this implemented. I have used CEL in the past for configurable processing and have been wondering...

> Testing is a nightmare and can't be easily performed. We can't run elastic-agent locally Best solution to this is a VM, I like https://multipass.run/ especially if you are a...

Taking a closer look at this, the APM configuration is being received in libbeat but it is not exposed in any way. The APMConfig we need is attached to each...

Hooking into the existing libbeat configuration reload API makes sense to me as a way to expose this. Our team could do this, answering when we could do it I'll...