Hiroshi Hatake

fluent-bit go plugin interface does not have frequency control feature. And fluent-bit v1.6 will support s3 built-in plugin. You should evaluate early access of built-in s3 plugin.

OK. Let's close this PR then.

No. I followed the time behavior for fluent-plugin-s3. It uses time.Now() equivalent value for timestamp: https://github.com/fluent/fluent-plugin-s3/blob/master/lib/fluent/plugin/out_s3.rb

This fluent-bit-go-loki plugin is merged into loki upstream. Could you test it instead? https://github.com/grafana/loki/tree/master/cmd/fluent-bit

I reproduce your issue and I found a workaround for this case: ```yaml pipeline: inputs: - name: winevtlog tag: some-tag alias: WIndows alias channels: application interval_sec: 5 read_existing_events: true db:...

> If the `channels` are accepting multiple inputs, fluent bit should ideally have each stanza for query per channel in the configuration file. Is that correct understanding? Ideally, it's correct....

Ah, Buildroot is one of the embedded Linux! I actually worked for Yocto Linux which is another Embedded Linux distribution some time ago. Thanks for the addition into Fluent Bit...

> @cosmo0920 I see the metrics generated have an `_` as a prefix, e.g: > > ``` > 2024-04-17T05:13:34.937000000Z _fluentbit_uptime{__name__="fluentbit_uptime",hostname="cosmo-desktop2"} = 1 > ``` > > maybe is something around...

I got it. > > @cosmo0920 I see the metrics generated have an `_` as a prefix, e.g: > > ``` > > 2024-04-17T05:13:34.937000000Z _fluentbit_uptime{__name__="fluentbit_uptime",hostname="cosmo-desktop2"} = 1 > > ```...

I also confirmed with prometheus' remote write settings and node_exporter: ```console $ bin/fluent-bit -i prometheus_remote_write -pport=8080 -puri=/api/prom/push -phttp2=off -o stdout -v ``` ```console $ cat prometheus_remote_write.yml # prometheus global config...