Flume has built in functionality to log out data flowing through
mainly for debugging purposes. This functionality appears in several
places of the codebase. I think such functionality rise security
concerns in production environments where sensitive information might
be ingested so it is crucial that enabling such functionality has to
be as explicit as possible (avoid implicit side effect setup).
Eg: setting the level of root logger to debug/trace cause that every
other logger will start logging at debug/trace including the ones
logging raw data.
In this jira I would like to provide a patch capturing how I imagined solving this issue. It can be refined iteratively or used as a basis for a broader discussion.