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
When detach_process is used in BufferedOutput, children have its own buffer in my understanding. So, monitor_agent can't find buffer_queue_length and buffer_total_queued_size for that plugin.
Do you have any plan to support buffer metrics for DetachProcessMixin and DetachMultiProcessMixin by monitor_agent?
I have no idea about it, but I think I can consider about it after implementing whole new APIs.
But I have a question: Why detach_process is needed for output plugins? num_threads is good enough to make I/O requests concurrent.
I think multiple buffers and no giant lock by detach_process will help to gain high throughput since output plugin needs some computation in some case.
When
detach_process
is used in BufferedOutput, children have its own buffer in my understanding. So,monitor_agent
can't findbuffer_queue_length
andbuffer_total_queued_size
for that plugin.Do you have any plan to support buffer metrics for
DetachProcessMixin
andDetachMultiProcessMixin
bymonitor_agent
?One of my suggestion is here:
See also awslabs/aws-fluent-plugin-kinesis#45
The text was updated successfully, but these errors were encountered: