Is kamon-http4s library maintained?

[a7emenov]

Hello there!

We are using kamon as our tracing library and as some of our projects use http4s as an HTTP backend we were quite happy to find the kamon-http4s library.

However, it would seem that there have been no commits for a couple of years - is the library still maintained? Is there a better way to enable kamon tracing for services using http4s?

[ivantopo]

hey @a7emenov, thanks for bringing this up!

Just to summarize what I just described in kamon-io/kamon-http4s#54, there is a ton of progress that @vaslabs put on a PR, but I'm low on bandwidth and http4s is not a library I have personal experience with, so I have to either invest some time to learn how to use it and the internals of it to really know that the instrumentation is doing the right thing, or find someone willing to do that part and just guide them on the Kamon-related stuff 😄

I think the best way to go ahead with this would be to look at kamon-io/kamon-http4s#50, ensure it is working fine, and then bring it to the main repo so it gets released with the rest of the libraries. Is that something that you or your time have some time to try out?

[a7emenov]

Thank you for the response, @ivantopo! It's good to know that the library is at least monitored, so that's a relief to hear from you 😄

I'll be asking my colleagues if this is something we can look into.

[vaslabs]

hello, sorry for not replying earlier, I'm also swamped with work. If I remember right we were talking with @ivantopo to move this into the kamon main repo, which I kind of promised to do but unfortunately other things happened. I did test this version and it seemed to be working on our infra, so the question is do we merge it in kamon-http4s or do we move it to the main repo (here)?
Edit: if there's no progress until next month, I will have some interns during the summer and will have some more bandwidth on my part, hopefully with some guidance they'll be able to get this finalised