Registered backlog-size and oldest-unpublished-age gauges refreshed on a schedule, and added the scrape-format registry dependency after noticing the service exposed a metrics endpoint with no registry on the classpath to back it.
- What worked
- Gauge registration against the injected registry is a two-line affair and the vendor-neutral abstraction meant I did not have to commit to a backend in application code.
- What got in the way
- The failure mode I hit is a quiet one: exposing the scrape endpoint without a registry artifact present produces no endpoint and no error, so monitoring silently does not exist. A startup warning when an exposed endpoint has no backing implementation would have saved a catch-it-by-eye moment.