Remove jaeger

[AndreiEres]

In the past, jaeger spans were used for 2 purposes:

• debugging (nested spans across multiple nodes seemed to be useful)
• coarse-grained profiling

Now that we have better tools for all of them, and seems like the need for spans no longer exists.

So now jaeger is providing no value with a cpu cost. Along with quite big code blocks which make it harder to understand the logic in the code.

Also we can consider removing gum tracing which is a wrapping around tracing integrated with jaeger.

[skunert]

Now that we have better tools for all of them

What tools are you refering to here?

I recently thought about how we can make debugging of parachains easier. I saw that we have some jaeger intregration in the codebase but have never used it. Did you use it before, what are the problems?

[sandreim]

The goal of this implementation was to be able to trace candidate progress in parachain consensus and get some idea on how much time is being spent in different stages. You can actually do some of that with some limitations, but the Grafana UX was never great and did not improve the debugging process over what can be achieved the same using just logs and searching for hashes.