nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [nifi] adarmiento commented on issue #3698: WIP: NIFI-6628: Separate out logging of extensions vs. nifi framework
Date Sun, 08 Sep 2019 20:45:04 GMT
adarmiento commented on issue #3698: WIP: NIFI-6628: Separate out logging of extensions vs.
nifi framework 
URL: https://github.com/apache/nifi/pull/3698#issuecomment-529240027
 
 
   @markap14 as a quick job, I just reverted `APP_FILE `to be the main log file, and this
time I selected the `FRAMEWORK_FILE` for all the currently existing non-app related loggers:

   ```
    <logger name="org.apache.nifi" level="INFO">...</logger>
   <logger name="org.apache.zookeeper.ClientCnxn" level="ERROR">...</logger>
   <logger name="org.apache.zookeeper.server.NIOServerCnxn" level="ERROR">...</logger>
   <logger name="org.apache.zookeeper.server.NIOServerCnxnFactory" level="ERROR">...</logger>
   <logger name="org.apache.zookeeper.server.quorum" level="ERROR">...</logger>
   <logger name="org.apache.zookeeper.ZooKeeper" level="ERROR">...</logger>
   <logger name="org.apache.zookeeper.server.PrepRequestProcessor" level="ERROR">...</logger>
   <logger name="org.apache.calcite.runtime.CalciteException" level="OFF">...</logger>
   <logger name="org.apache.curator.framework.recipes.leader.LeaderSelector" level="OFF">...</logger>
   <logger name="org.apache.curator.ConnectionState" level="OFF">...</logger>
   <logger name="org.apache.nifi.cluster" level="INFO">...</logger>
   <logger name="org.apache.nifi.server.JettyServer" level="INFO">...</logger>
   <logger name="org.eclipse.jetty" level="INFO">...</logger>
   <logger name="org.springframework" level="ERROR">...</logger>
   <logger name="org.glassfish.jersey.internal.Errors" level="ERROR">...</logger>
   <logger name="org.eclipse.jetty.annotations.AnnotationParser" level="ERROR">...</logger>
   ```
   
   As you mentioned, there are Processors and Controller Services widespread among various
packages which may not be encompassed by those existing loggers. Only editing those loggers
would make those processors log lines end up in the `FRAMEWORK`. 
   
   Do you think it will be the correct choice to fathom the codebase in search of those Processor/Services
and creating additional dedicated loggers in `logback.xml` file?

----------------------------------------------------------------
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

Mime
View raw message