Monitoring NiFi

Hi, guys. Welcome back. In this video, we will see how to monitor your instance using the various options available in Nifi. Nefi is a powerful tool and it can do multiple tasks in parallel. So it's essential to have a proper way to monitor an instance. This is where Apache Nephi's rich set of monitoring capabilities comes in handy. Let's go ahead and see these capabilities one by one. The first and the foremost statistics are available in the top status bar of the. Here we can see a few vital statistics about the current health of Nifi. For example, the active thread stats shows the number of active threads currently running across the Nifi instance and depict how hard Nifi is working for us. The total queued data specifies how many flow files are presently queued across the entire flow, and it also represents the total size of those flow files. Yeah, we can also have stats of the total number of running processes, stop processes and processes which are invalid due to some configuration issues. If the knife, for instance, is in a cluster mode or it is connected to an registry for version control, we will see more statistics like how many nodes are in the cluster and how many components are up to date or out of sync with the component version available in the registry. We will see more about clustering and registry in the later videos where you will get a better understanding of what am talking here now. Knife also provide starts at individual component level. Each processor and process group on the canvas provides much more info about how much data has been processed by the component in the past five minutes. It also allows us to see the number of flow files that has been consumed by a processor, as well as the number of flow files that has been produced by the processor in the last five minutes. By default, Knife will take a snapshot of these five minute statistics every minute for 24 hours and keep it in a separate repository called the Status Repository. You can view these detailed statistics by right clicking the component and choose the View Status History option. Please be noted. The default configuration of the status repository snapshot can be changed by updating the following properties in Nifi dot properties file. In addition to the statistics provided by each components, will also notify when any issues of type, warning or error occurred in our flow. This is called bulletin. It looks like a sticky note and it will show all the issues produced by a processor in the past five minutes. To demonstrate this, I have created a simple flow with get file processor and configured it to point to an invalid folder path. Now let's go ahead and start the flow. Did you see that? We got an error here which is notified by the bulletin indicator. Let's mouse over the bulletin to see the details of the error or warning message. Bulletin message comes handy for the user and saves a lot of time, which usually takes to filtering through a log file to find errors. In cluster mode. The bulletin will also indicate which node in the cluster emitted the error event. You can change the log level of the bulletins by configuring the bulletin level of the processor configuration available in the settings tab. We can also use the bulletin board option available in the top right global menu to see all the bulletins that has occurred so far in the instance. Yo. We can also filter the bulletin based on the component name, message and so on. That's it for this video, guys. Hope you have got a fair understanding on how to monitor your Wi-Fi instance using the various options available in Wi-Fi. Thank you. See you in the next video.