[
https://issues.apache.org/jira/browse/CAMEL-20045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17928704#comment-17928704
]
Pasquale Congiusti commented on CAMEL-20045:
--------------------------------------------
I had a look at this. So, here the outcome of a first analysis.
*Related to Opentelemetry*
The availability of traces would be available on the same JVM running the
process (ie, the Camel application) via an ["in memory"
exporter|https://opentelemetry.io/docs/specs/otel/metrics/sdk_exporters/in-memory/].
This is clearly an implementation though exclusively for unit test as it
requires the "inspector" to be on the same process running the application.
Also, for performance and consistency reason we cannot think to have traces
collected inmemory.
*Related to TelemetryDev*
The new telemetry component is a kind of toy used to validate the telemetry
abstraction more than anything else. It could only be used for simple tracing
or for debugging purposes, but definitely not on more complex applications. The
technology rely on logging traces with the same logging mechanism available in
the application. If it makes sense, a separate appender can be created for the
purpose so the user can later ingest the feed to some third party observability
tool. If we want to collect the traces here, we'd need to parse the specific
logging configuration (which can vary based on the logging technology) in order
to figure it out where the file database is. We should also play with log
rotation and any other implementation detail.
In general I think it's not a good idea to have any telemetry collection
directly in the application as it creates a high coupling with the telemetry
technology used. IMO the telemetry collection should be a separate specialized
process with its specific logic and tooling (possibly asynchronously) as it
already happens with the agents which are taking care to push traces to a
collector which is later used to analyze and render the traces for
observability purposes.
> 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)
