[jira] [Commented] (NIFI-9435) Add Filtering Parameters to Flow Metrics

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-9435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17475741#comment-17475741 ] 

ASF subversion and git services commented on NIFI-9435:
-------------------------------------------------------

Commit dd7131b257113581a8485b2c59184c7eecc96ce6 in nifi's branch refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=dd7131b ]

NIFI-9435 Added registries and names include parameters to Flow Metrics

- Added optional includedRegistries query parameter to Flow Metrics Resource method supporting one or more registries
- Added optional includedNames query parameter to Flow Metrics Resource method supporting one or more metric family names
- Added sampleName and sampleLabelValue optional pattern parameters
- Added FilteringMetricFamilySamplesEnumeration to support streamed filtering
- Added PrometheusMetricsWriter and TextFormat implementation

Signed-off-by: Joe Gresock <jg...@gmail.com>

This closes #5571.


> 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
>          Time Spent: 1h 50m
>  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)