You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2018/12/28 05:56:14 UTC

[GitHub] sijie commented on issue #3259: [Question]How to configure log level for pulsar functions

sijie commented on issue #3259: [Question]How to configure log level for pulsar functions
URL: https://github.com/apache/pulsar/issues/3259#issuecomment-450295608
 
 
   Currently there is no programming way to configure debug level on per function basis. If you are using Process runtime, it is no simple way to change the log level. because the log4j settings is controlled by this log4j2.yml file (https://github.com/apache/pulsar/blob/master/pulsar-functions/runtime/src/main/resources/java_instance_log4j2.yml) which is packaged into the java instance runner. 
   
   For production usage, I would suggest logging important information at info level. For development purpose, you can use local-run to run your function to debug things. local-run will use `conf/log4j2.yml` file for logging configuration.
   
   If you indeed have use cases to change log level per function basis, we can think of how to improve it.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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