ar3diu

Same issue. Any arguments I can use to provide the path to mitre config files?

I've noticed the same thing in Elastic Agent when using integrations for TCP/UDP inputs. Did you manage to find a fix?

So... is it just an error message and the TTL should be applied even if pipelining is enabled? Or the TTL setting is simply not supported in Logstash Output?

> The TTL setting is ignored and does nothing when in async mode. In sync mode it works as described. And how should the async mode be disabled? `pipelining: 0`?

I tried to set the following for the Logstash output in Fleet, but I still get some errors in regards to agent connections to the Logstash hosts. Any idea what...

Interested in this as well. It will be useful for monitoring and detecting abnormal/unauthorized connections.

The TCP router now supports `IPWhiteList` middlewares. Not an expert in this, but I guess that should suffice...? :thinking: