[
https://issues.apache.org/jira/browse/CAMEL-20045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17928708#comment-17928708
]
Claus Ibsen commented on CAMEL-20045:
-------------------------------------
The dev console is only for development and to quickly be able to see what
happens when you code/design a prototype. So having it in-memory in the same
process for a single camel app is fine. Its for a single Camel app only, and
something to make it quick/easy for a developer to type /q/trace or whatever in
a web browser to see traces (in just some text format) and similar in a camel
jbang command.
So with the new telemetry-dev component it fits there.
No its not intended for 3rd party tool integration or whatever, but for a easy
all-in-a-box tool for building low-code prototypes
Users that want to push to a seperate collector and all of that can surely do
that, but this ticket is about to do all from camel during prototyping
> camel-opentelemetry - Add dev console
> -------------------------------------
>
> Key: CAMEL-20045
> URL: https://issues.apache.org/jira/browse/CAMEL-20045
> Project: Camel
> Issue Type: New Feature
> Components: camel-opentelemetry
> Reporter: Claus Ibsen
> Assignee: Pasquale Congiusti
> Priority: Major
> Fix For: 4.x
>
>
> A dev console that can give insight into opentelemtry, that can benefit
> during development and trouble shooting.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
