[
https://issues.apache.org/jira/browse/NIFI-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Witt updated NIFI-634:
-----------------------------
Fix Version/s: 0.2.0
> Review Logback default log levels
> ---------------------------------
>
> Key: NIFI-634
> URL: https://issues.apache.org/jira/browse/NIFI-634
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Configuration
> Reporter: Adam Taft
> Priority: Minor
> Labels: logging
> Fix For: 0.2.0
>
>
> Evaluate the default log levels of the logback.xml configuration. Consider
> reducing the verbosity of general framework logging events, primarily
> originating from the org.apache.nifi.* logger.
> Rationale: the existing log level defaults have historically benefitted NIFI
> data flow managers needing to inspect and trace the lifecycle of an
> individual flowfile. However, given the capabilities of the provenance
> repository engine, the preferred mechanism for tracing a flowfile would now
> be performed through provenance inquiries.
> Thus, the necessity for logging standard processor and framework subsystem
> events at the INFO level is reduced. The logging configuration could default
> to allow only WARN or greater output from common framework components in
> order to isolate and identify flow management issues.
> Recommendation: change the default log levels of the org.apache.nifi.*
> loggers from INFO to WARN, with exception for component functionality which
> does not readily have a reciprocal provenance equivalent.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
