Dependency upgrade (OTEL v1.28.0) and migration to native Float64Gauge
#22
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mstoykov
approved these changes
Aug 24, 2024
This was referenced Aug 26, 2024
joanlopez
approved these changes
Sep 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
This RP updates extension to the latest k6 (I can exclude this from the PR) v0.53 and OTEL dependencies
v1.28.0, where the new synchronous gauge is available (open-telemetry/opentelemetry-go#5304), and we migrate to it.It also migrates resources to shemaless to make dependency upgrades easier (open-telemetry/opentelemetry-go#2341)
Why?
It reduces the number of custom-tailored logic