Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fluentd_output_status_buffer_oldest_timekey and fluentd_output_status_buffer_newest_timekey when queue is empty #178

Open
flaker opened this issue Oct 28, 2020 · 0 comments

Comments

@flaker
Copy link

flaker commented 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 with fluentd_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.

@flaker 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant