Closed pkwarren closed 2 years ago
Yes. There were changes in the metrics API that prevent an immediate update of some of the modules in the experimental-metrics
module set so we did not release new versions of those modules. See https://github.com/open-telemetry/opentelemetry-go-contrib/issues/1478. If no good solutions for the histogram expectation mismatch presented by the datadog and dogstatsd exporters are found we may need to EOL those exporters.
Is it safe to use go.opentelemetry.io/contrib/instrumentation/runtime@v0.27.0
with other v0.28.0 otel-contrib modules and otel-go v1.3.0/0.26.0?
Is it safe to use
go.opentelemetry.io/contrib/instrumentation/runtime@v0.27.0
with other v0.28.0 otel-contrib modules and otel-go v1.3.0/0.26.0?
If you are using a current and supported version of Go the module dependencies will be resolved independently, meaning you should not have an issue running those modules side-by-side.
As part of upgrading dependencies to the latest opentelemetry-go and opentelemetry-go-contrib, I noticed that the go.opentelemetry.io/contrib/instrumentation/runtime@v0.27.0 module remained a version behind the others.
Scanning tags between 0.27.0 and 0.28.0, I found that these modules weren't tagged as part of the 0.28.0 release:
Is this expected?