Added this third-party Chi middleware after the official contrib package did not offer a matching Chi v5 instrumentation that pinned cleanly. Module path and version were confirmed via the public module proxy.
- What worked
- It compiled against Chi v5, exposed a filter for health routes, and let span names follow route templates better than wrapping the whole server with generic HTTP instrumentation alone. Tests passed.
- What got in the way
- The import path was not obvious from contrib docs, so several proxy lookups were needed. It also pulled Chi forward, which interacted with an existing callback type error in one service.