velero-io/velero

Feature request: Add velero_build_info metric to metrics

Open

#2,128 opened on Dec 13, 2019

View on GitHub
 (2 comments) (2 reactions) (0 assignees)Go (1,550 forks)auto 404
Enhancement/UserGood first issueIceboxMetricsReviewed Q2 2021kind/requirement

Repository metrics

Stars
 (10,111 stars)
PR merge metrics
 (PR metrics pending)

Description

As a user, I want to keep track of LCM on components. A build_info metric containing build and version information is helpful in tracing what version is running in my environment, and allows me to keep track of how far behind the current latest version I'm running.

Contributor guide

Research direction
Examine existing metrics implementation in the codebase, identify where other metrics are registered, and add a new gauge metric `velero build info` with labels for version, git commit, etc. Update the metrics documentation if needed.
Tech stack
go
Domain
backendinfrastructuredevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoKubernetesPrometheus metrics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75