romanz
Feature: Better logging to stdout/stderr on first startup
Is your feature request related to a problem? Please describe.
There is very little feedback when starting electrs for the first time even when -v is used.
Describe the solution you'd like I would like electrs to at least tell me that it's working e.g. able to contact bitcoind and get blocks etc.
Additional context
Currently when starting electrs for the first time the only output you get to stdout/stderr is a Debug dump of the Config data. I can see from top that stuff is happening between it and bitcoind but nothing whatsoever is logged.
So I think the two things that got me were:
-
This eprintln: https://github.com/romanz/electrs/blob/master/src/config.rs#L284 confused me. Since I was getting something to stderr I thought that I was actually getting logs.
-
https://github.com/romanz/electrs/blob/5ef12d407520e22f46aaa726716424fcf233b94f/doc/config_example.toml#L35 should be "verbose = 3" not verbosity (for it to work).
I would consider using a default logging level of INFO when -v isn't specified, increase it to DEBUG with one -v and to VERBOSE with two. I did something similar in bwt.
@shesek this is currently not supported by configure_me. I will try to look into it, should be quite easy. It will just take some time.
Meanwhile fixed config example should help.
@shesek ah, I misunderstood what you said. This is possiible, I believe, but I'd also introduce -q option to make it quieter.
In a way this is a breaking change as it'll suddenly behave differently. I'm not sure what to do about it.
It seems to be a breaking change with very slim chances of actually breaking something. Like if someone was not using -v and relied on having no STDERR output for some scripting, which doesn't seem likely. But then again, you never know....
I'm more concerned about users having -vv which is now info if I remember correctly and then it'd become trace and fill the logs.