[jira] [Commented] (NIFI-15508) Add Record Gauge support to Standard Process Session

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

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

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

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

NIFI-15508 Added Record Gauge support to Standard Process Session

- Added ComponentMetricReporter to Framework API
- Added application property for configuring ComponentMetricReporter
- Added getGaugeValues method to TestRunner

This closes #10813.

Signed-off-by: Pierre Villard <pi...@gmail.com>


> Add Record Gauge support to Standard Process Session
> ----------------------------------------------------
>
>                 Key: NIFI-15508
>                 URL: https://issues.apache.org/jira/browse/NIFI-15508
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Core Framework
>            Reporter: David Handermann
>            Assignee: David Handermann
>            Priority: Major
>             Fix For: 2.8.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Building on the addition of the {{recordGauge}} method to the {{ProcessSession}} interface, the standard class should be updated with an initial implementation.
> As an incremental approach to implementation, a new framework-level interface should be created to report Gauge records. This interface should form the basis for subsequent implementation that can support optional persistence of Gauge records in the framework. Naming the interface {{ComponentMetricReporter}} captures the general purpose, and opens the possibility for other types of processing metrics to be reported.
> Following the pattern of other framework interfaces, the implementation should be configurable through an application property. The default value should be empty. Subsequent additions to the framework for persistent storage, similar to Counters, can consider additional application properties if needed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)