[
https://issues.apache.org/jira/browse/NIFI-9498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17461533#comment-17461533
]
Mark Payne commented on NIFI-9498:
----------------------------------
[~otto] though not a NiFi feature per se - if helpful, you can easily determine
this from command-line given
{{zgrep "<artifact>" conf/flow.xml.gz | cut -d">" -f2 | cut -d"<" -f1 | sort |
uniq}}
> Ability to report what components a flow is actually using
> ----------------------------------------------------------
>
> Key: NIFI-9498
> URL: https://issues.apache.org/jira/browse/NIFI-9498
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Otto Fowler
> Priority: Major
>
> Nifi may have 100s of NARS and their components loaded, but for any flow the
> actual working set of NARS and components is a subset.
> We often recommend that people remove NARS that aren't used from the nifi
> working set for various reasons, but there is no concrete way to identify
> what NARs you can remove.
> NIFI should provide some set of features around allowing visibility into what
> the working set of NARS and components are for a given flow.
> There are different levels of feature around this idea to be explored:
> * a cli command that produces a report document from a live instance or from
> flow definition file
> * a ui component that visualizes the graph and can export a report
> * Actions from these things, to remove or restrict what is loaded in a
> cluster ( imagine a cluster whitelist for NARS that is share in the cluster )
> * ???
> * profit!!!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
