You can use the following metrics to assess the general health of your NiFi cluster.
|JVM INFO||JVM Heap Usage||Displays the amount of memory being used by the JVM process. For NiFi, the default configuration is 512 MB.|
|JVM File Descriptor Usage||Shows the number of connections to the operating system. You can monitor this metric to ensure that your JVM file descriptors, or connections, are opening and closing as tasks complete.|
|JVM Uptime||Displays how long a Java process has been running. You can use this metric to monitor Java process longevity, and any unexpected restarts.|
|THREAD INFO||Active Threads||
NiFi has two user configurable thread pools:
This metric displays the number of active threads from these two pools.
|Thread Count||Displays the total number of threads for the JVM process that is running NiFi. This value is larger than the two pools above, because NiFi uses more than just the timer and event driven threads.|
|Daemon Thread Count||Displays the number of daemon threads that are running. A daemon thread is a thread that does not prevent the JVM from exiting when the program finishes, even if the thread is still running.|
|FLOWFILE INFO||FlowFiles Received||Displays the number of FlowFiles received into NiFi from an external system in the last 5 minutes.|
|FlowFiles Sent||Displays the number of FlowFiles sent from NiFi to an external system in the last 5 minutes.|
|FlowFiles Queued||Displays the number of FlowFiles queued in a NiFi processor connection.|
|BYTE INFO||Bytes Received||Displays the number of bytes of FlowFile data received into NiFi from an external system, in the last 5 minutes.|
|Bytes Sent||Displays the number of bytes of FlowFile data sent from NiFi to an external system, in the last 5 minutes.|
|Bytes Queued||Displays the number of bytes of FlowFile data queued in a NiFi processor connection.|