[
https://issues.apache.org/jira/browse/CAMEL-25435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-25435.
---------------------------------
Fix Version/s: 4.23.0
Resolution: Fixed
Fixed by https://github.com/apache/camel/pull/27533: a node label cut to 50
characters by the backlog tracer and debugger now ends with an ellipsis.
> camel-core - backlog tracer and debugger cut node labels at 50 characters
> without an ellipsis
> ---------------------------------------------------------------------------------------------
>
> Key: CAMEL-25435
> URL: https://issues.apache.org/jira/browse/CAMEL-25435
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 4.23.0
>
>
> The backlog tracer, the backlog debugger and the tracer cut the label of a
> node to 50 characters with StringHelper.limitLength(label, 50)
> (BacklogTracer, DefaultBacklogDebugger, CamelInternalProcessor,
> DefaultTracer). The cut has no ellipsis, so a tool showing the label cannot
> tell it is cut, and shows it as if it were whole, e.g. in the route history
> of the camel-jbang monitor (Inspect tab):
> {noformat}
> unmarshal[org.apache.camel.model.dataformat.JsonDa
> choice[when[simple{${body[orderId]} == 'ORD-1002'
> {noformat}
> Suggestion: end a cut label with an ellipsis (… or ...), and/or include the
> full label (it is in the route model) so a tool can cut it to the room it
> has. The 50 characters may also be too few for an unmarshal label, which
> spends most of them on the class name of the data format.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
