[
https://issues.apache.org/jira/browse/CAMEL-15386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17173323#comment-17173323
]
Ruben Vargas edited comment on CAMEL-15386 at 8/7/20, 5:10 PM:
---------------------------------------------------------------
I'll take a look at this, I will see what are our options
was (Author: rubensvp):
I'll take a look at this, I will see what options we have.
> Camel-Opentelemetry and Camel-opentracing: Semantic conventions are going to
> diverge
> ------------------------------------------------------------------------------------
>
> Key: CAMEL-15386
> URL: https://issues.apache.org/jira/browse/CAMEL-15386
> Project: Camel
> Issue Type: New Feature
> Components: camel-opentelemetry, camel-opentracing
> Reporter: Andrea Cosentino
> Priority: Major
> Fix For: 3.x
>
>
> I was trying to update to opentelemetry 0.7 and noticed some breaking
> changes. It seems the semantic conventions are going change between
> opentracing and opentelemetry
> [https://github.com/opentracing/specification/blob/1.1/semantic_conventions.md]
> [https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/trace/semantic_conventions/database.md#notes-and-well-known-identifiers-for-dbsystem]
> The problem we have is the fact that we are sharing stuff between opentracing
> and opentelemetry through the camel-tracing component and since they removed
> the DB_TYPE and DB_INSTANCE, we need to find a different way or a workaround
> [https://github.com/open-telemetry/opentelemetry-java/commit/8525405239173cb8cb6eb4e72cc421b37a8ab2fb]
> [~rubensvp]
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
