Export prometheus client_golang's Go build_info metric #8482
Conversation
This file contains hidden or 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
We have our own version metric already, but supporting client_golang's build_info means we can be more compatible with other Golang programs we run which export this metric. We can consider deprecating and removing our own metric in the future, but we have dashboards and alerts using it, so there's no rush to do that.
jprenken
approved these changes
Nov 6, 2025
jprenken
requested review from
a team and
jsha
and removed request for
a team
jsha
approved these changes
Nov 6, 2025
mcpherrinm
changed the title
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.
We have our own version metric already, but supporting client_golang's build_info means we can be more compatible with other Golang programs we run which export this metric.
We can consider deprecating and removing our own metric in the future, but we have dashboards and alerts using it, so there's no rush to do that.