[
https://issues.apache.org/jira/browse/NIFI-14589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuanhao Zhu updated NIFI-14589:
-------------------------------
Summary: Make instance id configurable or constant when running nifi as a
standalone instance (was: Make prometheus metrics instance id configurable
when running as standalone instance)
> Make instance id configurable or constant when running nifi as a standalone
> instance
> ------------------------------------------------------------------------------------
>
> Key: NIFI-14589
> URL: https://issues.apache.org/jira/browse/NIFI-14589
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Yuanhao Zhu
> Priority: Major
> Original Estimate: 20m
> Remaining Estimate: 20m
>
> In 2.x nifi, the prometheus metrics uses the instance id/node id in the
> metrics data, while in nifi 1.x, in the corresponding component
> PrometheusReportingTask, we can actually configure the instance id presented
> in the metrics. It would be great to also align that behavior in the 2.x
> nifi-api prometheus metrics by making the instance id configurable so that
> when getting the metrics, we can have two options, use the instance/node id,
> or use a instance id/name that we assign, which is extremely helpful to
> analyze the metrics in databases.
>
> It is understood that in 2.x we use the instance id when running as a
> standalone instance and node id when running as cluster in the Prometheus
> metrics. However, when running as a standalone instance, the instance id is
> always randomly set, which brings a lot of problem when it comes to analyzing
> the metrics in the database, if making the instance id is not an option, it
> would be also helpful to make the instance id constant when running nifi in
> standalone mode like the node id which is decided by the hostname and port
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
