[
https://issues.apache.org/jira/browse/NIFI-8536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17344043#comment-17344043
]
ASF subversion and git services commented on NIFI-8536:
-------------------------------------------------------
Commit 73a2283c279390a8d31d67eec8d0d190a2115131 in nifi's branch
refs/heads/main from Mohammed Nadeem
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=73a2283 ]
NIFI-8536: PrometheusReportingTask and PrometheusRecordSink do not support
variable registry for port property
Signed-off-by: Matthew Burgess <mattyb...@apache.org>
This closes #5075
> PrometheusReportingTask and PrometheusRecordSink do not support variable
> registry for port
> ------------------------------------------------------------------------------------------
>
> Key: NIFI-8536
> URL: https://issues.apache.org/jira/browse/NIFI-8536
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions, Variable Registry
> Affects Versions: 1.12.1, 1.13.2
> Reporter: Matthew Clarke
> Assignee: Nadeem
> Priority: Minor
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The documentation for both PrometheusReportingTask [1] (reporting task) and
> PrometheusRecordSink [2] (controller service) state that NiFi Variable
> Registry can be used to define the port. However, configuring NiFi EL in the
> port property results in:
> java.lang.NumberFormatException: For input string: "${<variable registry
> property name>}"
> Support variable registry here would allow user to set a unique port on each
> host in a NiFi cluster.
> [1]
> http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-prometheus-nar/1.13.2/org.apache.nifi.reporting.prometheus.PrometheusReportingTask/index.html
> [2]
> http://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-prometheus-nar/1.13.2/org.apache.nifi.reporting.prometheus.PrometheusRecordSink/index.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
