Ling Huang

Could someone help review this proposal to see it makes sense? This has caused some excessive memory usage in Ruby. We have some short-term mitigation in place, but it's still...

apolcyn@ - Cool cool. Thanks for initiating the conversation. That should be fine. We don't have an urgent need for this feature. Just wanna make sure it's still on the...

+1

There is a similar report at https://github.com/open-telemetry/opentelemetry-collector/issues/3004.

Looks like this remains an issue. Based on some investigation done by @[franciscovalentecastro](https://github.com/franciscovalentecastro), it affects Windows users that uses a parser with `time_format` expecting a timezone different from UTC. We...

Thanks for taking a look @cosmo0920 . Do I understand it correctly that if we use the [winevtlog](https://github.com/fluent/fluent-bit/tree/master/plugins/in_winevtlog) input plugin instead of [in_winlog](https://github.com/fluent/fluent-bit/tree/master/plugins/in_winlog), the problem is solved? Is `in_winevtlog` expected...

@edsiper can confirm this, but I think this was fixed by https://github.com/fluent/fluent-bit/commit/476a3e2c8262036dc36abcb06aefe1329ba8daa6 that was part of Fluent Bit 1.8.9. However 1.8.9 has a separate issue (https://github.com/fluent/fluent-bit/issues/4262 Spamming errors in the...

Is the issue reproducible after the fix https://github.com/fluent/fluent-bit/pull/5266 was merged? We had some similar issues, but seems resolved after this fix.

The `bad` (can be flushed to destination at a later time) entries here are not due to client error, but some temporary server side errors. We would like to retry...

@repeatedly - Yes! Our problem is `Temporary failure` but with `ready-to-go` and `failed-but-need-to-be-retried` entries in the same buffer chunk. By throwing an exception, we can retry everything. But instead we...