You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Alexander Bij (Jira)" <ji...@apache.org> on 2026/09/25 12:48:00 UTC

[jira] [Assigned] (NIFI-16298) Adds Prometheus metrics for the Primary Node and Cluster Coordinator roles

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

Alexander Bij reassigned NIFI-16298:
------------------------------------

    Assignee: Alexander Bij

> Adds Prometheus metrics for the Primary Node and Cluster Coordinator roles
> --------------------------------------------------------------------------
>
>                 Key: NIFI-16298
>                 URL: https://issues.apache.org/jira/browse/NIFI-16298
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>    Affects Versions: 2.11.0
>            Reporter: Alexander Bij
>            Assignee: Alexander Bij
>            Priority: Minor
>              Labels: metric-collector, metrics, prometheus
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> Improvement to be able to build a Grafana dashboard showing the Primary Node and Cluster Coordinator based on the prometheus scrape.
> The Prometheus flow metrics endpoint ({{{}/nifi-api/flow/metrics/prometheus{}}}) exposes cluster membership/connectivity metrics, but nothing indicates which node currently holds the Primary Node or Cluster Coordinator role. Building a "nodes in this cluster" dashboard/table (one row per node, with its key stats) currently has no way to mark which row is the Primary Node or the Cluster Coordinator without querying NiFi's REST API separately and joining the data out-of-band.
> Suggestion to add to Prometheus cluster metrics:
>  * {{cluster_is_primary_node [0,1]}}
>  * {{cluster_is_cluster_coordinator [0,1]}}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)