[
https://issues.apache.org/jira/browse/NIP-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18017104#comment-18017104
]
Mark Bean edited comment on NIP-10 at 8/29/25 6:48 PM:
-------------------------------------------------------
Talking concept more than complexity of implementation, I envision the bulletin
board functioning the same as today except that messages with a stack trace can
be expanded by the user to display the stack trace when needed, e.g. a dropdown
arrow on the left or right side. Ideally, the stack trace details would only be
retrieved when the user takes this action. However, the complexity of
implementation may make this option impractical, if not impossible.
Alternatively, the bulletin board may have a dropdown or radio button option to
select "condensed" or "full" option which is applied globally. Based on this
selection, all bulletins would be displayed with or without stack traces, as
appropriate.
Both these options may require the separate API call as [~mattyb149] suggests
was (Author: markbean):
Talking concept more than complexity of implementation, I envision the bulletin
board functioning the same as today except that messages with a stack trace can
be expanded by the user to display the stack trace when needed, e.g. a dropdown
arrow on the left or right side. Ideally, the stack trace details would only be
retrieved when the user takes this action. However, the complexity of
implementation may make this option impractical, if not impossible.
Alternatively, the bulletin board may have a dropdown or radio button option to
select "condensed" or "full" option which is applied globally. Based on this
selection, all bulletins would be displayed with or without stack traces, as
appropriate.
> Add stackTrace to Bulletin
> --------------------------
>
> Key: NIP-10
> URL: https://issues.apache.org/jira/browse/NIP-10
> Project: NiFi Improvement Proposal
> Issue Type: Improvement
> Reporter: Pierre Villard
> Priority: Major
>
> As a NiFi user, it is not always easy to quickly access the logs. Bulletins
> are a good way to surface potential errors when data is being processed in
> the flow but in case this requires deeper debugging, the information
> currently provided in a bulletin is not always enough.
> In such a case the NiFi user may not have permissions or easy access to the
> logs of the NiFi instance and would need to get in touch with a NiFi admin
> able to retrieve the underlying log message for the bulletin and provide the
> full stack trace. This can make the overall troubleshooting process longer.
> It could be useful to add a stackTrace String to the Bulletin object in
> nifi-api and provide the option to expand a bulletin in the Bulletin Board
> view in order to see and easy copy in the clipboard the potential stack trace
> associated to the bulletin.
> We want to use a String instead of a Throwable to make sure we do not have
> serialisation issues across the NiFi nodes but we want to make we retain the
> proper format of the stacktrace for proper rendering in the UI.
> Additionally, it may be good to evaluate if we should specifically remove the
> value of this new field when being called via APIs that are not for the
> bulletin board. This may not be necessary though as we never retrieve a large
> number of bulletins anyway.
> Expected changes:
> * The API change would be to add a stackTrace String field to the Bulletin
> object in nifi-api
> * In the implementations of LogObserver, convert the throwable into the
> string representing the stack trace and add it to the bulletin
> * In the UI, improve the bulletin board to properly render the stack trace
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
