[CAMEL-15386] Camel-Opentelemetry and Camel-opentracing: Semantic conventions are going to diverge

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.5.0
• Component/s: camel-opentelemetry, camel-opentracing
• Estimated Complexity: Unknown
• Assignee: Unassigned
• Reporter: Andrea Cosentino
• Created: 07/Aug/20 14:28
• Updated: 12/Aug/20 11:29
• Resolved: 12/Aug/20 11:29

Description

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

 

Issue Links

• links to: GitHub Pull Request #4083