Hi, Can you answer this question please How to do Dynamic property naming in NIfi? - Cloudera Community - 369374 ... View more

The file can be found within your NiFi logs folder, where you have your other logs as well. ... View more

@databoi  I see from your images that you are using Apache NiFi 1.11.4 which is around the time that the Load Balanced connection capability was introduced.  There were many bugs subsequently identified in load balanced connection and addressed in future releases. I strongly encourage you to upgrade to the latest NiFi release and see if your issue persists.    If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. Thank you, Matt ... View more

hi @ushasri,   The file you are looking for is called flow.xml.gz and can be found on each NiFi node, within the conf folder.   More information can be found here: https://nifi.apache.org/docs/nifi-docs/html/user-guide.html flow.xml.gz: Everything the DFM puts onto the NiFi User Interface canvas is written, in real time, to one file called the flow.xml.gz. This file is located in the nifi/conf directory by default. Any change made on the canvas is automatically saved to this file, without the user needing to click a "Save" button. In addition, NiFi automatically creates a backup copy of this file in the archive directory when it is updated. You can use these archived files to rollback flow configuration. To do so, stop NiFi, replace flow.xml.gz with a desired backup copy, then restart NiFi. In a clustered environment, stop the entire NiFi cluster, replace the flow.xml.gz of one of nodes, and restart the node. Remove flow.xml.gz from other nodes. Once you confirmed the node starts up as a one-node cluster, start the other nodes. The replaced flow configuration will be synchronized across the cluster. The name and location of flow.xml.gz, and auto archive behavior are configurable. See the System Administrator’s Guide for further details. ... View more

thanks for the reply cotopaul.  I'm still very new to NiFi clusters and was thinking, from a purely cloud architecture perspective, that it typically makes sense to abstract the specific endpoints from the end user.  I'll review the url you provided.  Thanks again for your reply. ... View more

Hi @ushasri, There are plenty of ways to perform such a thing, but here are three ways I have already implemented the alert in my flows so far: You can have an PutEmail at the end of each failure Queue and in that why, when a message gets rejected you will get notified by email. This can be done strictly in NiFi. You can create a monitoring system which will interrogate your Bulletin Board using NiFi's REST API and send you whatever alerts you want. This can be done either directly inside NiFi or with a shell/python script on your server. You tail the nifi-app.logs on each server and extract only the errors you are interested in. This solution can be implemented both in NiFi and on your local server. ... View more

hi @ushasri, What processor are you using to save the data within your DB and how do you build up the query? If you want to add the filename to the record which gets inserted within your table, you should use an UpdateRecord Processor to generate a new column and populate it using the ${filename}. Next, the generated record should go further down your line up until it gets inserted in your database. ... View more