Enumerate log level subsystem commands

[RichardLitt]

See #2305

License: MIT
Signed-off-by: Richard Littauer [email protected]

[Kubuxu]

There are more subsystems and even more sub-subsystems.

[RichardLitt]

Cool. What are they? Can you log subsubsystems?

[Kubuxu]

I always have to search the code when looking for logger that is handling given system. I have no idea if there is some general solution.

Example of subsubsystem logger: https://github.com/ipfs/go-ipfs/blob/master/core/corehttp/corehttp.go#L20

[RichardLitt]

So, that's less than ideal, because someone may not know they can search for them. How do you know if something is a subsystem? How does the system know?

[Kubuxu]

Here are all logger modules: https://gist.github.com/Kubuxu/ff5c472713a3f058049f

[RichardLitt]

Hmm. That is a lot. Maybe we can mention that in the mans? Not all of them, but a way to find them all? Maybe even just that grep command. cc @whyrusleeping

[whyrusleeping]

we could have a log subcommand that lists all registered logger subsystems

[RichardLitt]

I would like that.

[dignifiedquire]

@whyrusleeping I just found this interesting log event: github.com/ipfs/go-libp2p/p2p/net/swarm/addr which is probably not meant like this

[whyrusleeping]

@RichardLitt what do we want to do here? There are too many subsystems to enumerate in the argument description.

[RichardLitt]

@whyrusleeping: "we could have a log subcommand that lists all registered logger subsystems"

We should do this. It should be called ipfs log ls. Basically, just build a go-process to create the list Kubuxu pasted above.

[whyrusleeping]

@RichardLitt cool, i'll file an issue describing that command, and then close this PR