[NIFI-1283] Documentation wrong for ControllerStatusReportingTask

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.4.0
• Fix Version/s: 0.5.0
• Component/s: Documentation & Website
• Labels: beginner newbie
• Assignee: Unassigned
• Reporter: Matthew Clarke
• Created: 15/Dec/15 14:11
• Updated: 07/Apr/16 11:18
• Resolved: 12/Jan/16 16:00

Description

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.

Issue Links

• breaks: NIFI-1738 Incorrect logger name for ControllerStatusReportingTask