You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/01/15 13:29:00 UTC

[jira] [Commented] (NIFI-7017) PrometheusReportingTask does not report nested process group status

    [ https://issues.apache.org/jira/browse/NIFI-7017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17015972#comment-17015972 ] 

ASF subversion and git services commented on NIFI-7017:
-------------------------------------------------------

Commit bb699e749755432837b3a4132372f635d7480be3 in nifi's branch refs/heads/master from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=bb699e7 ]

NIFI-7017: This closes #3988. Fixed PrometheusReportingTask for nested PG status

Signed-off-by: Joe Witt <jo...@apache.org>


> PrometheusReportingTask does not report nested process group status
> -------------------------------------------------------------------
>
>                 Key: NIFI-7017
>                 URL: https://issues.apache.org/jira/browse/NIFI-7017
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Matt Burgess
>            Assignee: Matt Burgess
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The clear() command added in NIFI-6715 causes the registry to be reset on every call to createNiFiMetrics. In the case of nested process groups this method is a recursive call, so the registry keeps getting cleared except for the last visited process group.
> The clear() should only be done when createNiFiMetrics is called on the root process group, in order to clean up the registry before adding all the components' metrics.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)