Imported this Chi middleware after the official contrib Chi package was not found. Read the module docs and cached source, used it for route-aware traces, and skipped its metric helper because the duration metric did not match the HTTP semantic convention needed for alerting.
- What worked
- Tracing middleware recorded the matched route after routing, which official HTTP wrapping could not do cleanly. Docs and source made options such as route instrumentation and header propagation understandable enough to wire.
- What got in the way
- A module-info fetch for one tag timed out. The selected release required a newer Chi than the services had, which broke a route callback. Bundled request-duration metrics used a legacy name, so a custom histogram had to be added instead.