Hiroshi Hatake

It seems that record accessor is not compiled correctly. Did you install bison and flex via homebrew?

FYI: we use [flog](https://github.com/chronosphereio/calyptia-flog) to generate arbitrary length of logs. In this case, we use `flog -b 1024000 -n 1` to create too huge line to consume by out_rdkafka2 plugin.

Hi, I tried to write another candidates to fix this issue: https://github.com/fluent/fluent-bit/pull/9236 The formerly proposed solution does not covered for (failure, success, success, **failure**) case. We needn't to eliminate success...

I'm trying to reproduce with the minimal case. I created a minimal creating histogram taking tool: ```go package main import ( "net/http" "time" "github.com/prometheus/client_golang/prometheus" "github.com/prometheus/client_golang/prometheus/promhttp" ) var ( my_duration =...

@sdmichelini Is there any further requirements to break consistency of histogram? passing-through an instance of Prometheus is needed? How to create the broken histogram which uses a custom bucket? Is...

I tried to use this Prometheus text format file: ```prometheus % cat problematic_prom/histgram.prom [Fail] # HELP my_tracing_duration_seconds tracing duration in seconds # TYPE my_tracing_duration_seconds histogram my_tracing_duration_seconds_bucket{le="0"} 0 my_tracing_duration_seconds_bucket{le="0.001"} 4 my_tracing_duration_seconds_bucket{le="0.01"}...

It could be useful for reducing bandwidth of requesting to AWS. Do you have an ETA for finishing up to mark as ready for review?

Oh, just conflicted after merging es responses testing PR. I'll fix it.

> @cosmo0920 should we be making these changes in the upstream project then consuming them here? Yes. We should handle similar changes in upstream not here.

> @cosmo0920 is this something that is safe to add from a functionality perspective that don't break existing users ? This doesn't break existing users. Just operates permissive behavior for...