[
https://issues.apache.org/jira/browse/FLUME-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398019#comment-15398019
]
Mike Percy commented on FLUME-2954:
-----------------------------------
Hi [~sati], I skimmed over this report and your analysis looks quite thorough.
I have the following comments:
* On hiding Flume configuration properties: I think it makes sense to just
disable printing those unless a global java -D property is set via the command
line.
* On source logging: I agree that adding a Flume configuration property to each
source that might log data seems reasonable. In addition, logging that data at
TRACE level seems reasonable.
* On logging malformed data: I agree that logging "bad" data should be OK,
especially if it blocks processing, since we need some way to communicate to
administrators that the feed is messed up. This kind of safe data logging is
necessary.
Thanks for putting this together!
Mike
> make raw data appearing in log messages explicit
> ------------------------------------------------
>
> Key: FLUME-2954
> URL: https://issues.apache.org/jira/browse/FLUME-2954
> Project: Flume
> Issue Type: Improvement
> Components: Channel, Configuration, Sinks+Sources
> Affects Versions: v1.6.0
> Reporter: Attila Simon
> Assignee: Attila Simon
> Priority: Critical
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
