Alexander Bij created NIFI-16298:
------------------------------------

             Summary: Expose Primary Node and Cluster Coordinator role as 
Prometheus metrics
                 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


h2. Summary

The Prometheus flow metrics endpoint (\{{/nifi-api/flow/metrics/prometheus}}) 
exposes cluster membership/connectivity metrics (\{{cluster_is_clustered}}, 
\{{cluster_is_connected_to_cluster}}, \{{cluster_connected_node_count}}, 
\{{cluster_total_node_count}}, all in \{{ClusterMetricsRegistry}}), 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.

h2. Why this is useful

To be able to build a Grafana dashboard showing the Primary Node and Cluster 
Coordinator directly from the same Prometheus scrape.



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

Reply via email to