Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Kamon looses context when http4s client raises an exception #56

Open
matwojcik opened this issue Sep 1, 2023 · 0 comments
Open

Kamon looses context when http4s client raises an exception #56

matwojcik opened this issue Sep 1, 2023 · 0 comments

Comments

@matwojcik
Copy link

If the http4s client raises an exception - e.g. when e.g. java.util.concurrent.TimeoutException is raised after setting connection timeout:

BlazeClientBuilder[F]
      .withRequestTimeout(100.millis)

then it seems that kamon context is lost, and e.g. traceId is not propagated to MDC for logging.

If there is not any exception but a request ending with e.g. 500, then it seems to be working fine.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@matwojcik