Craig MacKenzie

It isn't supported in the output itself, it's not a matter of being able to provide the configuration or not. https://github.com/elastic/beats/blob/8f8f3137f2ed1a78a9db4d48831d6578831619f8/libbeat/outputs/logstash/async.go#L76-L79

The documentation on the TTL option from https://www.elastic.co/guide/en/beats/filebeat/current/logstash-output.html#_ttl: > Time to live for a connection to Logstash after which the connection will be re-established. Useful when Logstash hosts represent load...

The TTL setting is ignored and does nothing when in async mode. In sync mode it works as described.

Yes per https://www.elastic.co/guide/en/beats/filebeat/current/logstash-output.html#_pipelining https://github.com/elastic/beats/blob/a4f576f34928669b821a0243af00b35d8d74918e/libbeat/outputs/logstash/logstash.go#L75-L79

I would update the integration as part of this work. If you can't for some reason, create a separate issue to do it so it isn't lost.

> Now that we can know the queue size in bytes, I'm just wondering if we should make it more clear that the percentage is calculated from the number of...

https://github.com/elastic/beats/tree/main/x-pack/metricbeat/module/activemq seems to be the same, I'm sure there are more of these.

> @cmacknz should we ask the other teams (integration owners) to also run full tests? i imagine they are as part of their 8.14 efforts. Automated tests found this and...

@rdner I am interested to get your opinion on this given the amount of time you are spending trying to migrate and drive consistency between the log, filestream, and container...

If we don't have a conditional we risk duplicated logs. I think if we defaulted to always using both inputs we'd get a small amount of duplicated logs today on...