Logging improvements

[dknopik]

Collection of logging improvements all over the code base.

These changes especially aim to allow debuggability using logfiles sent in by a user, while maintaining a nice overview on the console output without unnecessary detail.

[diegomrsantos]

I was considering tackling areas of the codebase where we log and return an error, like in

anchor/anchor/eth/src/event_processor.rs

Line 193 in 0f74f32

debug!(

. In cases like this, we should only return an error with the proper message. This error should be kept as the source, in full, if the caller wishes to wrap it with another error for context. In this way, we avoid log duplication. Perhaps, we could do this in this PR.

[dknopik]

In cases like this, we should only return an error with the proper message.

Well, ideally we return errors with structured data as long as possible and only turn into a String when we want to output it somewhere. But maybe you mean that.

On the other hand, logging where the error originates gives us more information due to active spans that might not be active where they are caught. 🤔

[diegomrsantos]

In cases like this, we should only return an error with the proper message.

Well, ideally we return errors with structured data as long as possible and only turn into a String when we want to output it somewhere. But maybe you mean that.

On the other hand, logging where the error originates gives us more information due to active spans that might not be active where they are caught. 🤔

We need to capture the backtrace https://docs.rs/anyhow/latest/anyhow/struct.Error.html

[cla-assistant]

All committers have signed the CLA.

[diegomrsantos]

LGTM, thanks for the work on this