Reduce log verbosity

[Melraidin]

Why?

Currently cardano-wallet logs every wallet it's tracking for at least some requests. This causes a great deal of noise in the logs when recording at the "info" level.

Over a one minute span cardano-wallet was hit with 976 requests to get transactions for various wallets. Each of those requests caused 114 lines to logged recording each wallet that cardano-wallet is tracking, plus two lines for recording the request itself. This made 62 887 lines recording wallets' existence of the total 64 700 lines logged over that one minute. For every two lines recording a request (the start and end of the request) we're seeing 114 lines that don't provide useful information, or 13 MB of noise for every 450 KB of data. This ratio is only expected to get worse as the number of wallets being tracked increases.

What?

Can logging which wallets were found, and any other information mainly of interest to cardano-wallet developers, be moved to the "debug" log level? In general I don't think this information is useful to operators simply running cardano-wallet.

How?

No response

[abailly]

As mentioned by @paolino while it's pretty easy to change the level of the logs, it's unclear what's the right level for everything.
For the case of Found existing wallet: messages we are toning it down to Debug level which should already significantly reduce the volume of logs.

As an aside, got some questions: Are you using JSON formatted logs? How do you consume/store/process those logs?

[abailly]

We have a section on monitoring in the documentation but no section about logging AFAICT. Something we could add @paolino