aljaz/lightning
1
0
Fork 0
mirror of https://github.com/aljazceru/lightning.git synced 2026-01-04 14:54:26 +01:00
Code Issues Packages Projects Releases Wiki Activity

options: let log-level subsystem filter also cover nodeid.

Browse Source 
That's useful for "tell me everything about this node" debugging.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Fixes: #5348
Changelog-Added: lightningd: `log-level=debug:<partial-nodeid>` supported to get debug-level logs for everything about a peer.
This commit is contained in:
Rusty Russell
2022-07-08 19:23:11 +09:30
parent 32af92145b
commit f6f1844e15
7 changed files with 25 additions and 13 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/lightningd-config.5.md
View File

@@ -124,7 +124,7 @@ Specify pid file to write to.
**log-level**=*LEVEL*\[:*SUBSYSTEM*\]
What log level to print out: options are io, debug, info, unusual,
broken. If *SUBSYSTEM* is supplied, this sets the logging level
for any subsystem containing that string. This option may be specified multiple times.
for any subsystem (or *nodeid*) containing that string. This option may be specified multiple times.
Subsystems include:
* *lightningd*: The main lightning daemon
@@ -148,7 +148,9 @@ internal integer id assigned for the lifetime of the channel:
So, **log-level=debug:plugin** would set debug level logging on all
plugins and the plugin manager. **log-level=io:chan#55** would set
IO logging on channel number 55 (or 550, for that matter).
IO logging on channel number 55 (or 550, for that matter).
**log-level=debug:024b9a1fa8** would set debug logging for that channel
(or any node id containing that string).
**log-prefix**=*PREFIX*
Prefix for log lines: this can be customized if you want to merge logs