[
https://issues.apache.org/jira/browse/NIFI-9183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17410762#comment-17410762
]
Lehel Boér commented on NIFI-9183:
----------------------------------
[~exceptionfactory] Thank you for your ideas! This feature is similar to
diagnostics, which is also included in nifi.sh. I followed the pattern and
added a new command to it. What benefits can we gain by wrapping it in another
bash script? Regarding user experience it is easier to remember few scripts, I
believe we should keep the number of them to a minimum. For the time being, a
coarse granularity interval is sufficient.
> Add a command-line option to save status history
> ------------------------------------------------
>
> Key: NIFI-9183
> URL: https://issues.apache.org/jira/browse/NIFI-9183
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Lehel Boér
> Assignee: Lehel Boér
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The status history can only be accessed via the nifi-api REST endpoint. Given
> that these API calls are replicated across cluster nodes, we should add a
> command-line option to save the status history of only one node.
> {{./bin/nifi.sh status-history <days> <dumpFile>}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
