consider introducing proper tracing, not sure how ...

# spring

[thanksforallthefish]

consider introducing proper tracing, not sure how it works with coroutines but it would be a better solution imo: https://spring.io/projects/spring-cloud-sleuth

[thanksforallthefish]

once you have this, spring will autogenerate a trace, and you could use that trace to follow a request along its entire journey. to actually monitor times, micrometer (included in the actuator) would help you there, and since you have a trace to correlate you get what you want

[thanksforallthefish]

again, not knowing how any of this interacts with coroutines

[Esa]

This looks interesting, I'll investigate this further

[Esa]

thanks

[corneil]

Maybe @sdeleuze can shed some light

[Saharath Kleips]

We use sleuth in our application with coroutines. I’m not sure if there is a better way, but if I recall we normally have to pass the MDC context manually into the coroutine context.

[Esa]

MDC?

[Saharath Kleips]

Sleuth adds trace ids and span ids to SLF4J MDC and it works really great with other Spring libraries since it will instrument your components for you. You have to do it manually when launching new coroutines so everything stays instrumented, there is a helper library for this: https://github.com/Kotlin/kotlinx.coroutines/tree/master/integration/kotlinx-coroutines-slf4j

[Saharath Kleips]

Chances are that you can just add the sleuth dependency and see most things working, but with coroutines there’s just a little bit more work involved.