Andrea Selva
Andrea Selva
No, we could eventually define some configurations that we can use to benchmark Logstash in different uses cases, so that we can spend less time in thinking how to test...
Thanks @karen for all your precious suggestions. I've integrated all because results in more fluent wording without changing the meaning.
run exhaustive test
That would be the right point, but verifying at least the 1 minute average flow metric would be that the test need to sleep and wait for 1 minute so...
@hylkevds do you know when this happen in production? For example is this a valid case that manifest the problem? 1. `client_1` is connected with name `session_1` 2. another instance...
> do you have a specific reason for switching? Log4j 1.x is more than outdated, also if use reload4j. However with log4j2 we could employ MDC to simplify the moving...
This is a good point!
Implement BufferedTokenizer to return an iterable that can verify size limit for every token emitted
Hi @yaauie with the latest changes to this PR, now the `append` method actively checks if the accumulator is accumulating fragments passed the `sizeLimit`(if `sizeLimit` is set). However, the sizeLimit...
A couple of thoughts on this: > In https://github.com/elastic/logstash/pull/17229 changes to the buffered tokenizer introduce an edge-case where an oversized sequence of bytes that do not include a delimiter can...
Looking at the code, the replacement of substitution variables with environment ones or the one from secret store happens at: https://github.com/elastic/logstash/blob/2cf6675f538247be091df9d31cc455538f029a07/logstash-core/lib/logstash/util/substitution_variables.rb#L69-L73 Those replacement sources (ENV and SecretStores) are global for...