[
https://issues.apache.org/jira/browse/NIFI-14586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17953215#comment-17953215
]
ASF subversion and git services commented on NIFI-14586:
--------------------------------------------------------
Commit c1403db4f04a47b601073049a1efbddac91274e9 in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=c1403db4f0 ]
NIFI-14586, NIFI-14587: Expose Processors' Performance Metrics in the UI as
part of the Status History; in doing so, I discovered a bug in which the GC
time was not being tracked properly and fixed it. Sorted counter values
lexicographically.
Signed-off-by: Pierre Villard <[email protected]>
This closes #9963.
> Expose CPU Time, Garbage Collection Time/Percent, etc. in Status History
> ------------------------------------------------------------------------
>
> Key: NIFI-14586
> URL: https://issues.apache.org/jira/browse/NIFI-14586
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We keep a bunch of metrics that are exposed only through a Diagnostic Dump
> currently (I.e., bin/nifi.sh diagnostics <filename>).
> These include, for each processor, how much of its time is spent using CPU
> (in nanoseconds and in percentage of time running), how much time is spent
> waiting on garbage collection to run, how much time is spent reading
> from/writing to content repo, how much time is spent on session commit.
> These are all retained within the FlowFileEventRepository. These should be
> exposed in the UI in the Status History. Because these metrics are not always
> gathered, if they are not gathered, we should simply return 0 for these
> metrics and document it as such.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
