Added the Prometheus registry and instrumented a request filter, a message publisher, and a queue consumer with tagged counters and a gauge over an in-memory queue size via MeterRegistry. Designed tags to stay low-cardinality so no identifiers could leak into metric labels. Could not run the code to confirm exposition output.
- What worked
- Counter and Gauge builder APIs are concise, and gauging a collection's size directly fits the backlog-depth use case. Tag-based design made the compliance constraint straightforward to honor.