Kevin, Thanks for proposing these improvements to support observability at the Connector level.
Providing status tracking and attribution at the Connector level makes sense, and provides a very useful way of tracking behavior. On initial review, I'm concerned about introducing the generic Logging Attributes concept at the public API level on the Connector Initialization Context. As it exists now at the framework level, there are a different set of concerns around exposing it in the public API. With that background, I'm not ready to vote for or against the proposal right now. Given the concern, I believe this needs to become a 72 hour vote. I plan to review the proposal in more detail and follow up soon. Regards, David Handermann On Wed, May 27, 2026 at 2:35 PM Kevin Doran <[email protected]> wrote: > > Team, > > I'd like to start a vote thread for NIP-30 [1] which aims to extend > existing observability features to the new Connectors feature. Mainly, > it will allow Connectors to have custom MDC logging attributes and > have their statuses included in the interfaces used by reporting > tasks. > > This is a small change, so using the updated NIP process recently > adopted, this will be a 24-hour lazy consensus vote [2]. > > I already have a draft PR up for these changes [3] for those that want > a feel for what the changes will look like. > > Cheers, > Kevin > > [1] https://issues.apache.org/jira/browse/NIP-30 > [2] https://apache.org/foundation/voting.html#LazyConsensus > [3] https://github.com/apache/nifi-api/pull/89
