NIFI-16123 Add Connection Status reporting to Process Session#11441
Merged
Conversation
- Added ConnectionStatusEvent interface to framework-api - Updated StandardProcessSession with optional recording of Connection Status
pvillard31
approved these changes
Jul 20, 2026
pvillard31
left a comment
pvillard31
left a comment
Contributor
There was a problem hiding this comment.
Changes are looking straightforward, thanks @exceptionfactory
boguszj
reviewed
Jul 20, 2026
| // Check enabled status to avoid building objects and calling methods when not used | ||
| if (context.isRecordConnectionStatusEventEnabled()) { | ||
| for (final Connection connection : checkpoint.processedConnections.values()) { | ||
| final ComponentMetricContext connectionMetricContext = checkpoint.connectionMetricContexts.get(connection.getIdentifier()); |
Contributor
There was a problem hiding this comment.
I feel like for connection events destination/source id & name could be useful metadata - connections are often nameless, so adding these to attributes in ComponentMetricContext at cacheConnectionMetricContext would provide a way to differentiate them easily. Wdyt?
Contributor
Author
There was a problem hiding this comment.
Thanks for the feedback @boguszj. I considered adding the source and destination information as well, I will take a look at this in a subsequent issue.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
NIFI-16123 Updates the framework
ComponentMetricReporterinterface with new methods for recordingConnectionStatusEventswhen theStandardProcessSessioncommits transactions.The implementation of the
ConnectionStatusEventfollows the interface definition and builder pattern of theProcessSessionEventcurrently implemented inComponentMetricReporter.The new methods on
ComponentMetricReporterinclude an enabled status indicator, allowing theStandardProcessSessionto avoid unnecessary operations when theComponentMetricReporterimplementation does not support recording Connection Status Events.The Connection Status Event recording enables exporting queued FlowFile information without depending on the
StatusHistoryRepositoryfor persistence and subsequent reporting.Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking
Pull Request Tracking
NIFI-00000NIFI-00000VerifiedstatusPull Request Formatting
mainbranchVerification
Please indicate the verification steps performed prior to pull request creation.
Build
./mvnw clean install -P contrib-checkLicensing
LICENSEandNOTICEfilesDocumentation