Re: FlowFile Logging

ah that sounds perfect for what I need to do. Thank you! On Tue, Aug 8, 2017 at 7:20 PM, Andy LoPresto wrote: > You can add an appender in the conf/logback.xml file which handles > “org.apache.nifi” and anything of ERROR level and writes to a separate log > file, which you

Re: FlowFile Logging

You can add an appender in the conf/logback.xml file which handles “org.apache.nifi” and anything of ERROR level and writes to a separate log file, which you can then monitor/parse/send wherever you like. This will filter out the normal operations logging from the failures you are interested

Re: FlowFile Logging

Hi Andy, I am trying to catch any error that happens from any processor in my flow. So adding a PutFile for each and every processor would not be ideal. And I don't need the data to be transformed into a usable type. I am passing this data to Logstash as a csv file (so raw data is just fine). Any

Re: FlowFile Logging

Hi James, The app log will definitely contain a lot of relevant information about flowfile failure, but you can also make this easier for yourself by routing the failure connection of the relevant processor to a PutFile/PutEmail processor which outputs the flowfile UUID and content claim size