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
On the other hand, v0.14 retruns buffer_queue_length is 20 and there is no buffer_total_queued_size field. We should keep same result because many companies use in_monitor_agent to check buffer status.
% ls buffer/test/
buffer.b533f7d9364192049ec84fd70687246ca.log buffer.q533f7d9363d704d4d13382bd5c03ae4a.log
buffer.b533f7d9364192049ec84fd70687246ca.log.meta buffer.q533f7d9363d704d4d13382bd5c03ae4a.log.meta
I think we can update code of in_monitor_agent to return same result along with new buffer/output plugins, instead of modification of buffer/output side.
Built-in in_monitor_agent are used only with same version of Fluentd itself.
I tested in_monitor_agent with following configuration and got wrong result.
v0.12.24
v0.12 returns correct result. buffer_queue_length is 1.
v0.14.0.rc.3
On the other hand, v0.14 retruns buffer_queue_length is 20 and there is no
buffer_total_queued_size
field. We should keep same result because many companies usein_monitor_agent
to check buffer status.The text was updated successfully, but these errors were encountered: