[
https://issues.apache.org/jira/browse/NIFI-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Gresock updated NIFI-9435:
------------------------------
Fix Version/s: 1.16.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Add Filtering Parameters to Flow Metrics
> ----------------------------------------
>
> Key: NIFI-9435
> URL: https://issues.apache.org/jira/browse/NIFI-9435
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: David Handermann
> Assignee: David Handermann
> Priority: Major
> Fix For: 1.16.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> The NiFi REST API includes support for generating metrics using Prometheus as
> the specified Producer. The current implementation gathers metrics in
> multiple registries, including Process Groups, Connections, Bulletins, and
> Java Virtual Machine status.
> On installations with a large number of components, the metrics resource can
> generate a very large amount of information, resulting in timeouts when
> requesting clients have low timeout settings. In some cases, returning all
> metrics may not be necessary. Adding optional filter parameters to the REST
> API would support returning a smaller amount of information, providing better
> support for NiFi installations with a large number of components. Potential
> filtering parameters could include limiting the selected registry or metrics
> component type.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
