Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

logging: DEBUG level causes too much output #7279

Open
ksedgwic opened this issue Apr 26, 2024 · 0 comments
Open

logging: DEBUG level causes too much output #7279

ksedgwic opened this issue Apr 26, 2024 · 0 comments

Comments

@ksedgwic
Copy link
Collaborator

ksedgwic commented Apr 26, 2024 •
edited
Loading

Issue and Steps to Reproduce

Would be nice if it was possible to run CLN at DEBUG level for long periods of time to observe/debug/validate things which require a bunch of history (ie CLBOSS balancing and swapping).

Related issues:

Some candidates:

rpc_command hook:

lightningd-test   | 2024-04-25T18:47:18.804Z DEBUG   lightningd: Calling rpc_command hook of plugin clboss
lightningd-test   | 2024-04-25T18:47:18.805Z DEBUG   lightningd: Plugin clboss returned from rpc_command hook call

handle_recv_gossip:

lightningd-test   | 2024-04-26T13:07:01.581Z DEBUG   031c64a68e6d1b9e50711336d92b434c584ce668b2fae59ee688bd73713fee1569-gossipd: handle_recv_gossip: WIRE_CHANNEL_UPDATE
lightningd-test   | 2024-04-26T13:07:01.581Z DEBUG   031c64a68e6d1b9e50711336d92b434c584ce668b2fae59ee688bd73713fee1569-gossipd: handle_recv_gossip: WIRE_CHANNEL_UPDATE
lightningd-test   | 2024-04-26T13:07:01.582Z DEBUG   031c64a68e6d1b9e50711336d92b434c584ce668b2fae59ee688bd73713fee1569-gossipd: handle_recv_gossip: WIRE_CHANNEL_UPDATE
lightningd-test   | 2024-04-26T13:07:01.582Z DEBUG   031c64a68e6d1b9e50711336d92b434c584ce668b2fae59ee688bd73713fee1569-gossipd: handle_recv_gossip: WIRE_CHANNEL_UPDATE
lightningd-test   | 2024-04-26T13:07:01.583Z DEBUG   031c64a68e6d1b9e50711336d92b434c584ce668b2fae59ee688bd73713fee1569-gossipd: handle_recv_gossip: WIRE_CHANNEL_UPDATE
lightningd-test   | 2024-04-26T13:07:01.583Z DEBUG   031c64a68e6d1b9e50711336d92b434c584ce668b2fae59ee688bd73713fee1569-gossipd: handle_recv_gossip: WIRE_CHANNEL_UPDATE
lightningd-test   | 2024-04-26T13:07:01.684Z DEBUG   031c64a68e6d1b9e50711336d92b434c584ce668b2fae59ee688bd73713fee1569-gossipd: handle_recv_gossip: WIRE_CHANNEL_UPDATE
lightningd-test   | 2024-04-26T13:07:01.684Z DEBUG   031c64a68e6d1b9e50711336d92b434c584ce668b2fae59ee688bd73713fee1569-gossipd: handle_recv_gossip: WIRE_CHANNEL_UPDATE
lightningd-test   | 2024-04-26T13:07:01.684Z DEBUG   031c64a68e6d1b9e50711336d92b434c584ce668b2fae59ee688bd73713fee1569-gossipd: handle_recv_gossip: WIRE_CHANNEL_UPDATE
ksedgwic added a commit to lightning-signer/c-lightning that referenced this issue Apr 26, 2024
@ksedgwic
logging: add TRACE between DEBUG and IO
ec0671b 
By moving super-noisy debugging logging to new TRACE level we can
make long-term logging at DEBUG possible w/o removing any logging.

Addresses ([ElementsProject#7279])

Related Issues:
ElementsProject#6927
chrisguida/smaug#34
ZmnSCPxj/clboss#194
ksedgwic added a commit to lightning-signer/c-lightning that referenced this issue Apr 26, 2024
@ksedgwic
logging: add TRACE between DEBUG and IO
25a33ae 
By moving super-noisy debugging logging to new TRACE level we can
make long-term logging at DEBUG possible w/o removing any logging.

Addresses ([ElementsProject#7279])

Related Issues:
ElementsProject#6927
chrisguida/smaug#34
ZmnSCPxj/clboss#194
@ksedgwic ksedgwic mentioned this issue Apr 26, 2024
Merged
ksedgwic added a commit to lightning-signer/c-lightning that referenced this issue Apr 26, 2024
@ksedgwic
logging: add TRACE between DEBUG and IO
8cd05cd 
By moving super-noisy debugging logging to new TRACE level we can
make long-term logging at DEBUG possible w/o removing any logging.

Addresses ([ElementsProject#7279])

Related Issues:
ElementsProject#6927
chrisguida/smaug#34
ZmnSCPxj/clboss#194
ksedgwic added a commit to lightning-signer/c-lightning that referenced this issue Apr 26, 2024
@ksedgwic
logging: add TRACE between DEBUG and IO
6daf4c9 
By moving super-noisy debugging logging to new TRACE level we can
make long-term logging at DEBUG possible w/o removing any logging.

Addresses ([ElementsProject#7279])

Related Issues:
ElementsProject#6927
chrisguida/smaug#34
ZmnSCPxj/clboss#194
ksedgwic added a commit to lightning-signer/c-lightning that referenced this issue Apr 27, 2024
@ksedgwic
logging: add TRACE between DEBUG and IO
d90859c 
By moving super-noisy debugging logging to new TRACE level we can
make long-term logging at DEBUG possible w/o removing any logging.

Addresses ([ElementsProject#7279])

Related Issues:
ElementsProject#6927
chrisguida/smaug#34
ZmnSCPxj/clboss#194
ksedgwic added a commit to lightning-signer/c-lightning that referenced this issue Apr 27, 2024
@ksedgwic
logging: add TRACE between DEBUG and IO
3f05ef1 
By moving super-noisy debugging logging to new TRACE level we can
make long-term logging at DEBUG possible w/o removing any logging.

Addresses ([ElementsProject#7279])

Related Issues:
ElementsProject#6927
chrisguida/smaug#34
ZmnSCPxj/clboss#194
ksedgwic added a commit to lightning-signer/c-lightning that referenced this issue Apr 27, 2024
@ksedgwic
logging: add TRACE between DEBUG and IO
3befc8b 
By moving super-noisy debugging logging to new TRACE level we can
make long-term logging at DEBUG possible w/o removing any logging.

Addresses ([ElementsProject#7279])

Related Issues:
ElementsProject#6927
chrisguida/smaug#34
ZmnSCPxj/clboss#194
ksedgwic added a commit to lightning-signer/c-lightning that referenced this issue Apr 27, 2024
@ksedgwic
logging: add TRACE between DEBUG and IO
f3526ed 
By moving super-noisy debugging logging to new TRACE level we can
make long-term logging at DEBUG possible w/o removing any logging.

Addresses ([ElementsProject#7279])

Related Issues:
ElementsProject#6927
chrisguida/smaug#34
ZmnSCPxj/clboss#194
ksedgwic added a commit to lightning-signer/c-lightning that referenced this issue Apr 27, 2024
@ksedgwic
logging: add TRACE between DEBUG and IO
63305a9 
By moving super-noisy debugging logging to new TRACE level we can
make long-term logging at DEBUG possible w/o removing any logging.

Addresses ([ElementsProject#7279])

Related Issues:
ElementsProject#6927
chrisguida/smaug#34
ZmnSCPxj/clboss#194
rustyrussell pushed a commit that referenced this issue May 9, 2024
@ksedgwic @rustyrussell
logging: add TRACE between DEBUG and IO
e3c600b 
By moving super-noisy debugging logging to new TRACE level we can
make long-term logging at DEBUG possible w/o removing any logging.

Addresses ([#7279])

Related Issues:
#6927
chrisguida/smaug#34
ZmnSCPxj/clboss#194
rustyrussell pushed a commit to rustyrussell/lightning that referenced this issue May 14, 2024
@ksedgwic @rustyrussell
logging: add TRACE between DEBUG and IO
2ef8f76 
By moving super-noisy debugging logging to new TRACE level we can
make long-term logging at DEBUG possible w/o removing any logging.

Addresses ([ElementsProject#7279])

Related Issues:
ElementsProject#6927
chrisguida/smaug#34
ZmnSCPxj/clboss#194
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ksedgwic