[
https://issues.apache.org/jira/browse/NIFI-8385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17435039#comment-17435039
]
ASF subversion and git services commented on NIFI-8385:
-------------------------------------------------------
Commit 059f14fd62508cd44e2c724f81256d37f90aa2e2 in nifi's branch
refs/heads/main from Lehel Boér
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=059f14f ]
NIFI-8385: Add FlowFiles from logging to bulletins (#4952)
> Add the possibility to reference flow file UUID in bulletins
> ------------------------------------------------------------
>
> Key: NIFI-8385
> URL: https://issues.apache.org/jira/browse/NIFI-8385
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Lehel Boér
> Assignee: Lehel Boér
> Priority: Major
> Time Spent: 4h
> Remaining Estimate: 0h
>
> When emitting a bulletin, it's possible to reference the flow file uuid via
> the log message. Example:
> {code:java}
> logger.error("Failed to send " + flowFile + " to Kafka", exception);
> {code}
> However it can make things hard to map the bulletins with the provenance
> events.
> This improvement is about adding an optional field for the FlowFile object in
> the log statement that would be caught by the LogObserver and added into
> bulletins via the BulletinFactory. Everything should be updated around
> bulletin to make this data available (UI, reporting tasks, etc).
> Use case:
> * we have the provenance data sent to a Kafka topic
> * we have the bulletins data sent to a Kafka topic
> * we case use Flink/SSB to join the data from the two topics based on the
> flow file UUID so that alerting is much more complete when there is something
> wrong happening.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
