[
https://issues.apache.org/jira/browse/NIFI-7753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Sampson reassigned NIFI-7753:
-----------------------------------
Assignee: (was: Chris Sampson)
> ExecuteGroovyScript INFO logs filtered out by default logback.xml
> -----------------------------------------------------------------
>
> Key: NIFI-7753
> URL: https://issues.apache.org/jira/browse/NIFI-7753
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.11.4
> Reporter: Chris Sampson
> Priority: Minor
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> The default logback.xml included with NiFi (at least the apache/nifi Docker
> image for 1.11.4) includes the following config:
> {code:xml}
> <logger name="org.apache.nifi" level="INFO"/>
> <logger name="org.apache.nifi.processors" level="WARN"/>
> <logger name="org.apache.nifi.processors.standard.LogAttribute"
> level="INFO"/>
> <logger name="org.apache.nifi.processors.standard.LogMessage"
> level="INFO"/>
> {code}
> This means that calls to `log.info` within an ExecuteGroovyScript are
> filtered out of the logs by default, which is confusing if one wants to write
> a script that includes some informational logging (seems a sensible
> expectation).
> I'd imagine including the following in the `logback.xml` would resolve this:
> {code:xml}
> <logger name="org.apache.nifi.processors.groovyx.ExecuteGroovyScript"
> level="INFO"/>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
