Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Support Questions

Find answers, ask questions, and share your expertise
Announcements
Share your experience with Cloudera on G2 and get a $25 Amazon Gift card.
Hi, I'm CLEO! Something exciting is coming to the Community. Stay Tuned!

Who agreed with this solution

avatar
Master Mentor

@paygb 

 

You are absolutely correct, the Cloudera Manager configuration property within NiFi configurations fro logback.xml does require you to input the entire logbck.xml and then add your modifications.

MattWho_0-1632765059020.png

 

Adding a new logger for the ControllerStatusReportingTask would require adding a logger like this:

<logger name="org.apache.nifi.controller.ControllerStatusReportingTask" level="DEBUG"/>

You can add this logger in line along with other loggers already in the logback.xml

The result would be all logging from this class at a DEBUG level and below would go in to the nifi-app.log.

You could optionally add an additional appender (NiFi has three existing appender now for the nifi-app.log, nifi-user.log and nifi-bootstrap.log files).  You can copy and modify one of those and the your logger would need to look like this:

  <logger name="org.apache.nifi.controller.ControllerStatusReportingTask" level="DEBUG" additivity="false">
    <appender-ref ref="NEW_APPENDER"/>
  </logger>

 

If you found this response assisted with your query, please take a moment to login and click on "Accept as Solution" below this post.

Thank you,

Matt

View solution in original post

Who agreed with this solution