Details
-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
-
1
-
SDK04: Scope Search
Description
Release notes: The metrics-opentelemetry package is now aligned with the same OpenTelemetry version as tracing-opentelemetry.
When making the releases notes for 3.5.2, I copied and verified the release notes for 3.5.1 that has the table below.
.Optional Artifact Version Compatibility
|
[options="header"]
|
|=======================
|
| Artifact | Couchbase Version | Built Against | API Stability
|
| `tracing-opentelemetry` | 1.3.2 | OpenTelemetry 1.31.0 | Committed
|
| `tracing-opentracing` | 1.3.2 | OpenTracing 0.33.0 | Committed
|
| `metrics-opentelemetry` | 0.5.2 | OpenTelemetry 1.31.0 | Volatile
|
However -
1) metrics-opentelemetry has this property which it uses:
<opentelemetry.version>1.19.0</opentelemetry.version>
|
2) (this is ok) tracing-opentelemetry uses
<version>${opentelemetry.version}</version>
which is defined in couchbase-jvm-clients/pom.xml as
<opentelemetry.version>1.31.0</opentelemetry.version>
|
( tracing-opentelemetry uses 1.31.0-alpha for opentelemetry-instrumentation-api-semconv)
3) note to self - the tracing-opentelemetry.version and metrics-opentelemetry.version defined in couchbase-jvm-clients/pom.xml are the versions for those modules (not versions of dependencies).