[jira] [Commented] (NIFI-4344) Improve bulletin messaging with exception details

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

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

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

Commit 0c748a5a2b366990c544e0580ca8626f0b9e3ed1 in nifi's branch refs/heads/main from Lehel Boér
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=0c748a5 ]

NIFI-4344: Improve bulletin messages with exception details.

This closes #5093.

Signed-off-by: Tamas Palfy <ta...@gmail.com>


> Improve bulletin messaging with exception details
> -------------------------------------------------
>
>                 Key: NIFI-4344
>                 URL: https://issues.apache.org/jira/browse/NIFI-4344
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework, Core UI
>            Reporter: Pierre Villard
>            Priority: Major
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> In some environments it is not possible/allowed to access the NiFi nodes (and consequently the log files). In such a situation, when developing a workflow, the only option to understand what could be wrong with a processor is to look at the bulletins.
> However, the bulletins only contain the message of the main exception. Quite often, the very useful messages to understand what is going on are located into the wrapped exception. At the moment, the only option is to go into the log files to get the messages. Even when access to the log files is authorized this can unnecessarily slow down workflow development.
> Ideally the full exception should be stored with the bulletin. However granting access to a full stack trace can raise security concerns, and besides, the bulletin tooltips are not designed to display large amount of data.
> Additional data would be provided in the bulletins view only. Few options are available:
> - display the full stack trace in the bulletins view but only for users with restricted component authorization.
> - display an enriched message with the concatenation of the detailed messages of the stack trace in the bulletins view (with or without restriction).
> Adding an example to illustrate the problem: with ConvertRecord, in case something is wrong with the schemas for the input/output data, the error is handled with:
> {code:title=ConvertRecord.java|borderStyle=solid}
> } catch (final SchemaNotFoundException | MalformedRecordException e) {
>     throw new ProcessException("Could not parse incoming data", e);
> }
> {code}
> In this case the bulletin will contain very little information.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)