Ron Milne created NIFI-9646:
-------------------------------
Summary: Failure Routes to include App-log *new* unique identifier
for root cause analysis?
Key: NIFI-9646
URL: https://issues.apache.org/jira/browse/NIFI-9646
Project: Apache NiFi
Issue Type: Improvement
Reporter: Ron Milne
At present the way processors convey errors is inconsistent, some attach
attributes; e.g., *ExecuteSQL* executesql.error.message; {*}InvokeHTTP
invokehttp.java.exception.message, etc{*}, others *ConvertJsonToSQL* and
*ValidateRecord* do not add any indication of the failure at all - as a small
sample.
The latter makes for additional effort in finding the root cause as one has to
ensure that the app-log file is being tailed and shipped somewhere else (e.g.,
fluent bit), and the UUID extracted and indexed within another system e.g.,
ElasticSearch.
Could we consider simply adding a unique identifier (UUID) to the ERROR log
line as then attach this as an attribute to the flowfile in failure queues (or
simply adding the actual app-log entry); This at least gives a single mechanism
for error reporting across processors.
Regards,
Ron.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
