You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not sure if I should discuss here or in the fluentd project.
I have a fluentd instance receiving (via forward) from fluent-bit instances and I've noticed that once the fluent-bit instance has been killed (no influx of new records), the fluentd_output_status_buffer_oldest_timekey keeps some value and the same seems to happen with fluentd_output_status_buffer_newest_timekey the end result is that subtracting one from the other will always give a difference.
maybe the stored values are the ones pre the last flush? I am not sure how this should work.
The text was updated successfully, but these errors were encountered:
flaker
changed the title
fluentd_output_status_buffer_oldest_timekey and fluentd_output_status_buffer_oldest_timekey when queue is empty
fluentd_output_status_buffer_oldest_timekey and fluentd_output_status_buffer_newest_timekey when queue is empty
Oct 28, 2020
Hi,
I am not sure if I should discuss here or in the fluentd project.
I have a fluentd instance receiving (via forward) from fluent-bit instances and I've noticed that once the fluent-bit instance has been killed (no influx of new records), the
fluentd_output_status_buffer_oldest_timekey
keeps some value and the same seems to happen withfluentd_output_status_buffer_newest_timekey
the end result is that subtracting one from the other will always give a difference.fluentd_output_status_buffer_queue_length == 0
but
(fluentd_output_status_buffer_newest_timekey - fluentd_output_status_buffer_oldest_timekey) > 0
maybe the stored values are the ones pre the last flush? I am not sure how this should work.
The text was updated successfully, but these errors were encountered: