Andrea Selva
Andrea Selva
> My main concern here is to not add any dependencies on any metrics libraries. ~~I generally agree, but some dependencies are needed. Dropwizard Metrics (or Micrometer) are an API...
Good! @hylkevds if you could resolve the conflicts then we are good to merge :-)
Thanks a lot @hylkevds for all this hard work! :-D
It happens also with TCP input, using the following pipeline, with testing data originated from https://github.com/logstash-plugins/logstash-codec-json_lines/pull/43 ``` input { tcp { port => 1234 codec => json_lines { decode_size_limit_bytes =>...
**Final decision** Given that the OOM can happen in the file input, the plan is to apply #17293 on top of #17229 once it's merged.
## Key points of the problem Given that we want to collect the size of the batch in terms of documents count and byte size of all documents, in a...
> dig a bit more into the storing strategy: the HdrHistogram mention without context or alternative begs more details. For example: could or should we measure per pipeline worker and...
> I was just considering if we could decouple the metric computation... My fault, I gave for granted too much. When using HdrHistogram, we just pass the raw measurements to...
> we could use this size as an approximation of the event size (how precise would it be, can we estimate it?) . That serialisation format is CBOR, so I'll...
Hi @jsvd in issue #17736 and study PR #17758 were posed some questions about accuracy vs performance of 3 different size computation techniques: 1. using CBOR serialization. 2. using the...