Update prometheus exporter package (fixes issues with build info gauge when using OTEL) #92
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.
Finally, our build info metric should work as expected with the open-telemetry prometheus exporter!
There is some funkiness with the versioning (also mentioned in a comment below).
It looks like we downgraded the opentelemetry-exporter-prometheus pacakge from a
1.x
to a0.41
... however! This is because the packaged changed how they were doing versioning about a year ago.So, the "latest" on pypi is a 1.12 release candidate (what we've been using up until now), but that's not actually the latest release. All of the latest releases are
0.x
....... it's confusing.So, the
0.41b0
release from 4 September, 2023 is actually the latest