ChrisSamo632 commented on pull request #4761: URL: https://github.com/apache/nifi/pull/4761#issuecomment-763068680
> Currently the only exceptions to the WARN level for processors are the ones that only log information (LogAttribute and LogMessage). Not sure why the scripting processors should default to INFO though. Is there something currently logged as INFO but should be WARN instead (i.e. any error/degraded conditions)? As described above, enabling INFO for the `ScriptedTransformRecord` would bring its defualt output more inline with `SplitRecord` (logging how many records have been transformed/dropped, etc.). `ExecuteGroovyScript` (by default in the included NiFi code) only logs stuff at WARN/ERROR currently, so that's fair enough. Enabling INFO was something I raised because we included non-exception logging in some of our scripts then took a while to realise why INFO statements weren't being included in our logs. If this isn't wanted behaviour, then fair enough, it can be left for individuals to enable INFO logging for the included processors that don't otherwise have it enabled by default (but the included logback.xml means some processors/controllers don't output INFO while others do - this PR doesn't necessarily rationalise all of them, but would for the scripted components at least). ---------------------------------------------------------------- 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: [email protected]
