I have been using gochi/chi router in my go project, and while moving to opentelemetry (OTEL), I noticed that it has weak support for chi router.
Although chi routers are widely used now across highly scalable go applications, but this lack of support causes being dependent on weird (static) scope names, with not much support from otel's own library for golang.
Since the OTEL library is not building new features for such support, I created a new library on the top of OTEL's base project.
Go-chi-otel is an adaption of OTEL go lib, allowing go chi users to now control their traces as they like.
I will be maintaing this project now to support any feature requests, as the library supports instrumentation right now.
You can star the repository if you like to support my initiative :)
Although chi routers are widely used now across highly scalable go applications, but this lack of support causes being dependent on weird (static) scope names, with not much support from otel's own library for golang.
Since the OTEL library is not building new features for such support, I created a new library on the top of OTEL's base project.
Go-chi-otel is an adaption of OTEL go lib, allowing go chi users to now control their traces as they like.
I will be maintaing this project now to support any feature requests, as the library supports instrumentation right now.
You can star the repository if you like to support my initiative :)