GoogleCloudPlatform/testgrid

Track a 'more' metric for the Updater

Open

#1,101 opened on Dec 19, 2022

View on GitHub
 (3 comments) (0 reactions) (1 assignee)Go (72 forks)auto 404
good first issuehelp wanted

Repository metrics

Stars
 (205 stars)
PR merge metrics
 (PR metrics pending)

Description

The Updater logs when it has more work to do after updating a test group (with 'more = true' in the log line), but it'd be nice to have a metric that allows us to track if there are spikes in groups that don't update, or a consistent line of groups that can't catch up on repeated updates. (This is expected in small numbers because some group updates, especially for new groups, take a long time, but it's a bad sign if this climbs or stays high).

Contributor guide

Research direction
Find the log statement for 'more=true' in the Updater code and add a counter metric (e.g., with Prometheus or OpenTelemetry) to track spikes. Place the metric increment where the log is written, and ensure it is exposed appropriately.
Tech stack
go
Domain
backendobservability
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
Gobasic understanding of metrics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65