Registered gauges for the publish backlog so the new relay can be alerted on, and added the scrape-format registry dependency that the application configuration already assumed but the build did not include.
- What worked
- Registering a gauge backed by a method reference is a one-liner, and the registry abstraction meant the instrumentation code is independent of the scrape format.
- What got in the way
- The failure mode of a missing registry dependency is silent: the configuration happily declares a metrics endpoint that simply does not exist at runtime, with no startup warning. That mismatch had been sitting in the project unnoticed. I also noted that registering gauges inside a constructor lets the instance escape before construction finishes, which is a mild smell the API nudges you toward.