[
https://issues.apache.org/jira/browse/NIFI-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086468#comment-15086468
]
Joseph Witt commented on NIFI-1283:
-----------------------------------
James that is a great catch and great point. [~markap14] any reason why we
need to stay with the existing model? It def sounds like a bug.
> Documentation wrong for ControllerStatusReportingTask
> -----------------------------------------------------
>
> Key: NIFI-1283
> URL: https://issues.apache.org/jira/browse/NIFI-1283
> Project: Apache NiFi
> Issue Type: Bug
> Components: Documentation & Website
> Affects Versions: 0.4.0
> Reporter: Matthew Clarke
> Priority: Minor
> Labels: beginner, newbie
>
> The documentation explains how to separate the processor and connection
> logging out to a new log file. The logger names provided do not work.
> Original:
> If may be convenient to redirect the logging output of this ReportingTask to
> a separate log file than the typical application log. This can be
> accomplished by modified the logback.xml file in the NiFi conf/ directory
> such that a logger with the name
> org.apache.nifi.controller.ControllerStatusReportingTask is configured to
> write to a separate log.
> Additionally, it may be convenient to disable logging for Processors or for
> Connections or to split them into separate log files. This can be
> accomplished by using the loggers named
> org.apache.nifi.controller.ControllerStatusReportingTask.Processors and
> org.apache.nifi.controller.ControllerStatusReportingTask.Connections,
> respectively.
> The correct loggers to use would be:
> ControllerStatusReportingTask
> ControllerStatusReportingTask.Processors
> ControllerStatusReportingTask.Connections
> If you include the org.apache.nifi.controller protion the logger will not
> work.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
