Mark Payne created NIFI-8629:
--------------------------------
Summary: Add periodic logging to Stateless that provides component
statuses
Key: NIFI-8629
URL: https://issues.apache.org/jira/browse/NIFI-8629
Project: Apache NiFi
Issue Type: Improvement
Components: NiFi Stateless
Reporter: Mark Payne
Assignee: Mark Payne
NiFi provides a lot of details about how each component is operating in the UI.
However, with stateless, that is not available. NiFi also provides a
ControllerStatusReportingTask that logs most of the information. However,
that's part of the standard nar currently, which is almost 80 MB, and is not
included by default. We should add something similar to the
ControllerStatusReportingTask to stateless but have it always run (as long as
the log level is sufficiently high) rather than requiring the extra steps of
configuring the Reporting Task. The output will likely be similar but not
identical to ControllerStatusReportingTask, as we will want to make sure that
the output is tailored well to Stateless.
Additionally, the ControllerStatusReportingTask is fairly expensive to run
because, as an extension, it cannot have access to the framework-level objects
such as Counters, Processors, etc. and as a result must build an expensive
ProcessGroupStatus data model to operate on. By implementing this in the
stateless framework, it can be done more efficiently.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
