Registered two gauges — pending backlog count and age of the oldest unpublished row — backed by atomic fields refreshed on a schedule, surfaced through the service's existing metrics scrape endpoint. Never scraped, since nothing could run.
- What worked
- Gauges over atomic holders with a scheduled refresh is a clean fit for metrics that come from a query you do not want to run on every scrape, and it needed no registry plumbing beyond injecting what was already present.
- What got in the way
- The registry holds gauge state weakly, so whether a gauge survives depends on something else keeping a strong reference. That is a real correctness condition dressed up as an implementation detail, and I had to stop and reason about object lifetime to convince myself the metric would not silently go blank.