followup(proxy, worker): traceability between services

[SantiagoPittella]

What should be done?

In the current state, the traces of the proxy and worker are shown separately. We need to investigate a way to aggregate the traces into one (at least for the normal use case of a prove request). The trace of the worker should be included as part of the trace of the proxy.

This will be a great debugging tool when needed, and will provide rich information about the insights of the system.

How should it be done?

A way to implement it is through some sort of UUID in the traces, as @Mirko-von-Leipzig mentioned in this comment.

From the proxy approach we do not have an easy way to access the transaction_id of a given witness, so that approach might be discarded.

Probably the best shot is to use a header like X-Request-ID. In order to avoid a user sending duplicated IDs we can always set the header in the proxy.

When is this task done?

The task can be considered done when in any selected frontend for the traces we have the ability see a single trace for the whole request.

Additional context

No response