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 2021/01/19 06:52:40 UTC

[GitHub] [nifi] ChrisSamo632 commented on pull request #4761: NIFI-7753 enable INFO logging for ExecuteGroovyScript by default

ChrisSamo632 commented on pull request #4761:
URL: https://github.com/apache/nifi/pull/4761#issuecomment-762640426


   > If we're doing this, shouldn't we do it for all the "scripted" components?
   
   I did wonder that myself after committing this change (I only really use the ExecuteGroovyScript, which is why I thought about the change). If it's thought worthwhile, then I'm happy to add more entries into the config for other scripted components.
   
   My motivation for the change comes from using this processor and wanting to log some details when the component is triggered, but only realising after some time that it was logging config (within the docker container in my case) that needed to change in order to see any output that wasn't at warning/error levels. If the other scripted components don't include info logs in their base code already, then the same change might 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