[jira] [Commented] (CAMEL-17384) camel-core - Developer Console SPI

["Nicolas Filotto (Jira)" <ji...@apache.org>]

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

Nicolas Filotto commented on CAMEL-17384:
-----------------------------------------

[~davsclaus] Do we agree that apart from JBang where the content of the result of the DevConsoles is accessible from [http://localhost:8080/dev] (hard coded port BTW) for other modes including Camel Main, it is not yet exposed, it is only available programmatically from the DevConsoleRegistry, right?

> camel-core - Developer Console SPI
> ----------------------------------
>
>                 Key: CAMEL-17384
>                 URL: https://issues.apache.org/jira/browse/CAMEL-17384
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core, tooling
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Major
>             Fix For: 3.15.0
>
>
> Some kind of SPI for a developer console, which allows to provide valuable information to developers.
> The SPI should be able to support different content-types so output can be in
> - text/plain 
> - application/json
> For text/plain we can use for a basic dump console from a CLI / jbang, and then application/json contains the structured data, and a more sophisticated console can render in a visual way, such as Camel Quarkus Developer Console / Karavan etc.
> We can then make out of the box consoles that can carry information such as
> - camel context summary
> - health check status
> - routing metrics stats
> - route source/xml dump
> - message history / tracing
> - event notifier history



--
This message was sent by Atlassian Jira
(v8.20.1#820001)