Is there a way to capture error messages that appear in Bulletin for more than 5 minutes ? After an error, I want to log detail error message from Bulletin in a permanent log, so I can look up error later. Currently Bulletin error messages provide most amount of detail on error (including detail logs) but they rollover every 5 minutes.
Is there another way of capturing detail error messages ?
Bulletins are intended to be short lived within the UI. The same error messages are also being reported to the nifi-app.log where the length of time they are preserved is based your configuration of the NiFi instance's logback.xml file. There should be no difference between the detail in the bulletin and the detail in the nifi-app.log.
Even though nifi-app.log contains every log, the bulletin message is small and precise. The idea is to capture the error message from bulletin and store it in table/file for auditing purposes. We have new versions since a year, hoping we have some way for this. Please share if there is any way to capture the error messages from the bulletin.
My suggestion here would be to handle this via the "SiteToSiteBulletinReportingTask".
You can build a dataflow to receive these bulletin events, manipulate them as you want and store them in a location of your choice for your auditing needs.
If you found this answer addressed your question, please take a moment to login in and click the "ACCEPT" link.
To add to this - a better way to act on important errors is to configure the logging subsystem to additionally send specific error categories to your destination of choice (e.g. active notification vs passive parsing of logs). NiFi is leveraging a very flexible logback system (an evolution of log4j). The best part - changes to the $NIFI_HOME/conf/logback.xml configuration file do not require an instance restart, will be picked up within 30 seconds or less.
@ibrahimadiattara I cannot upload your template dues to version issue . It gives me this error message
org.apache.nifi.processors.attributes.UpdateAttribute is not known to this NiFi instance.