Integration / Apache NiFi Interview Questions
What are Reporting Tasks in NiFi and what are common use cases?
Reporting Tasks are NiFi extension components that run on a scheduled basis to collect and report metrics, bulletin events, and operational data from the NiFi instance itself — not from FlowFiles. They operate at the NiFi system level rather than the data flow level, making them the primary tool for NiFi self-monitoring and integration with external observability platforms.
Reporting Tasks have their own scheduling (time-driven or CRON) and run independently of any flow. They are configured via Controller Settings → Reporting Tasks in the NiFi UI.
Common built-in Reporting Tasks:
SiteToSiteProvenanceReportingTask: Streams provenance events via Site-to-Site to a remote NiFi instance. Used for SIEM integration and long-term provenance archival outside the local provenance repository.
SiteToSiteBulletinReportingTask: Sends NiFi bulletin (warning and error) events via S2S to a remote NiFi for centralized alerting.
ControllerStatusReportingTask: Logs NiFi instance metrics (active threads, FlowFile counts, queue depths) to the NiFi log file.
PrometheusReportingTask: Exposes NiFi metrics as a Prometheus scrape endpoint, enabling Grafana dashboards for NiFi operational monitoring.
More Related questions...