You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Pierre Villard (Jira)" <ji...@apache.org> on 2025/05/21 17:32:00 UTC

[jira] [Resolved] (NIFI-14586) Expose CPU Time, Garbage Collection Time/Percent, etc. in Status History

     [ https://issues.apache.org/jira/browse/NIFI-14586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre Villard resolved NIFI-14586.
-----------------------------------
    Fix Version/s: 2.5.0
       Resolution: Fixed

> 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
>             Fix For: 2.5.0
>
>          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)