[
https://issues.apache.org/jira/browse/NIFI-11385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17720501#comment-17720501
]
ASF subversion and git services commented on NIFI-11385:
--------------------------------------------------------
Commit e1ddc44b078b17780465c6075e4bdd51ac522c89 in nifi's branch
refs/heads/support/nifi-1.x from Timea Barna
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=e1ddc44b07 ]
NIFI-11385 Added JMX Metrics REST Resource for Diagnostics
This closes #7124
Co-authored-by: David Handermann <[email protected]>
Signed-off-by: David Handermann <[email protected]>
(cherry picked from commit 5811a9c579a11aa8fc8358851df33d0456a5e10c)
> Expose JMX metrics from NiFi JVM
> --------------------------------
>
> Key: NIFI-11385
> URL: https://issues.apache.org/jira/browse/NIFI-11385
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Timea Barna
> Assignee: Timea Barna
> Priority: Major
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Most of the NiFi processors use external libraries which may register JMX
> Beans like Kafka processors. Exposing such metrics can help with problem
> solving.
> The information available depends on the registered Beans and usually related
> to performance indicators such as request/response rate, latency, request
> size, request counts or tool specific ones like commit rate or sync/join time
> for Kafka.
> Goals
> Have an REST endpoint with a list of JMX Bean attributes.
> Expose data in a secure way.
> Have some kind of filtering.
> Non-Goals
> Listing or executing supported operations of JMX Beans.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
