Repository navigation
Add github_repo_releases metric - #143
Open
hairyhenderson wants to merge 1 commit into
Open
hairyhenderson wants to merge 1 commit into
hairyhenderson wants to merge 1 commit into
Conversation
Report the number of releases per repository. Releases are already fetched for github_repo_release_downloads, but that metric is per asset, so releases without downloadable assets aren't visible at all. The metric is only emitted when FETCH_REPO_RELEASES_ENABLED is true, so a disabled fetch isn't reported as zero releases.
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
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.
The exporter reports each release for each repository, but only through
github_repo_release_downloads, which has one series per release asset. A release without downloadable assets produces no series at all.This adds a
github_repo_releasesgauge that reports how many releases each repository has.Related to #1, which asked for a releases metric (among others). This covers releases only however, so this doesn't fix that issue.