[
https://issues.apache.org/jira/browse/NIFI-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16395695#comment-16395695
]
ASF GitHub Bot commented on NIFI-4849:
--------------------------------------
Github user markap14 commented on the issue:
https://github.com/apache/nifi/pull/2468
I think at this point, after looking at the data model for
JVMDiagnosticsSnapshotDTO we can probably just break this into 3 distinct
fields: JVMSystemDiagnosticsSnapshotDTO, JVMControllerDiagnosticsDTO,
JVMFlowDiagnosticsDTO. Then, it makes the filtering and the permissions (and
likely the merging) a lot cleaner. Will head down that path and see if that
cleans things up. Thanks for the review so far @mcgilman!
> Add REST Endpoint for gathering Processor Diagnostics information
> -----------------------------------------------------------------
>
> Key: NIFI-4849
> URL: https://issues.apache.org/jira/browse/NIFI-4849
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Fix For: 1.6.0
>
>
> We need to add a REST endpoint that will use the appropriate resources to
> gather the Processor Diagnostics information. Information to return should
> include things like:
> * Processor config
> * Processor status
> * Garbage Collection info
> * Repo Sizes
> * Connection info for connections whose source or destination is the
> processor
> * Controller Services that the processor is referencing
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
