Nifi Monitoring for Splunk

Nifi Monitoring centralizes, in Splunk, the operational visibility of your Apache NiFi instances — a single one, several independent ones, or a cluster — so you no longer have to open each NiFi UI to know whether it is healthy. What you get: * Overview: the whole fleet at a glance — healthy instances, ERROR bulletins, worst heap and repository, queued FlowFiles. * Instance: heap, threads, load, GC, repository usage and throughput for one NiFi. * Components: which processor, group or connection is the bottleneck, including connections near backpressure. * Bulletins: NiFi's errors and warnings, traceable to the component that raised them. * Logs (optional, via a Universal Forwarder): app, user, request and deprecation logs — including what to clear before moving to NiFi 2.x. * Cluster: connected nodes, primary and coordinator, heap and queues per node. * Alerts: 8 ready-made alerts (backpressure, disconnected node, ERROR spike, stale instance, repository filling up, sustained high heap, TA HTTP errors, versioned flow sync failure), with per-instance thresholds. * Collection Health: whether data collection itself is working. Data reaches Splunk by polling NiFi's REST API with the Nifi Monitoring TA (pull, recommended), or from a flow inside NiFi that sends to Splunk's HEC (push, for when Splunk cannot reach NiFi). Compatibility: * Splunk Enterprise / Splunk Cloud 9.4 – 10.x * Apache NiFi 1.16 – 1.28.1 and 2.0 – 2.11 Requirements: * Nifi Monitoring TA — https://splunkbase.splunk.com/app/6124 * Lookup File Editor — https://splunkbase.splunk.com/app/1724 Upgrading from 1.x? Status Indicator is no longer needed, and the upgrade guide covers what changed: https://kudawdev.github.io/nifi-monitoring-splunk/upgrading/ Documentation: https://kudawdev.github.io/nifi-monitoring-splunk/ Source and issues: https://github.com/kudawdev/nifi-monitoring-splunk