NiFi
Pulse monitors the NiFi service and provides the following observability capabilities:
- NiFi service monitoring: issues with the service, nonresponse, shutdown/startup view, etc.
- NiFi performance metrics when dealing with the NiFi connections to import or export flows via registry.
Monitoring the NiFi Alerts
You can enable the following NiFi alerts on the Alerts page. This helps you debug and fix any failures encountered in the pipeline.
| Alert | Description | Configuration |
|---|---|---|
PROCESSOR_STATUS_CHECK | This alert gets triggered when a processor stops or goes into an invalid state by sending the Processor name and NiFi node in the alert body. This relies on ProcessorStatus as a metric that has been added to the new NAR file. | Severity: "High", Execution Interval: "30" |
NODE_CONNECTION_CHECK | This alert gets triggered when a NiFi Node gets disconnected from the NiFi Cluster. This is important to note that this is different from the EndPoint check as the NiFi process might still be up and running, however, it might have stopped sending heartbeats to the other nodes marking it as disconnected.
This relies on the | Severity: "High", Execution Interval: "30" |
For the complete list of stock and predefined alerts, see Stock and Predefined Alerts.
For details about customizing and creating alerts, see Creating Alerts.
You can use the below pages for details about the NiFi JVM, Process Groups, Flow Files, and Registry.