Have fluentd logs sent to local file logging instead of fluentd
In a recent bug tracking, we found that fluentd was logging some warnings by outputing the contents of the problematic message. That content was, in turn, logged, and caused a recursion with very quick amplification, thus crashing fluentd altogether, and other services in the process.
Loading
Please register or sign in to comment