[
https://issues.apache.org/jira/browse/NIFI-16298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18119195#comment-18119195
]
ASF subversion and git services commented on NIFI-16298:
--------------------------------------------------------
Commit 6d5d007b951587aa044beeb9019d9fa82b563a77 in nifi's branch
refs/heads/main from Alexander
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=6d5d007b951 ]
NIFI-16298 Expose Primary Node and Cluster Coordinator role as Prometheus
metrics (#11628)
> 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: 2h 10m
> 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)
