You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by GitBox <gi...@apache.org> on 2019/09/06 19:29:03 UTC

[GitHub] [nifi] markap14 commented on issue #3698: WIP: NIFI-6628: Separate out logging of extensions vs. nifi framework

markap14 commented on issue #3698: WIP: NIFI-6628: Separate out logging of extensions vs. nifi framework 
URL: https://github.com/apache/nifi/pull/3698#issuecomment-528984869
 
 
   @adarmiento Thanks for the PR! I went back & forth in my mind over what made sense here as far as configuring different elements. This PR goes the route of making the framework file the default, and then selectively choosing what goes into the app-log. But I think we have to go the other way. The app-log should be default, and then be selective about which packages we put into the framework log. This is because we processors/controller services/etc. do not just belong to the package "org.apache.nifi.processors". We have some that are just in "org.apache.nifi", some in "org.apache.nifi.json", etc., etc. And users can have their own custom processors, in a package of say "com.mycompany" and we don't want that going to the framework log. So we will need the default to remain the app-log and then select specific packages to put into the framework.log file. Does that make sense?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services