Connect/disconnect log levels? #227
Description
Originally posted by @Sjors in bitcoin/bitcoin#33517 (review)
Not directly related to the changes here, but it's a bit odd that clean disconnects are logged at the info level (always visible) while new connections are logged at the debug level (requires -debug=ipc).
Disconnect:
2025-10-08T07:19:16Z [ipc:info] {bitcoin-node-57287/b-capnp-loop-6497836} IPC server destroy N2mp11ProxyServerIN3ipc5capnp8messages6MiningEEE
2025-10-08T07:19:16Z [ipc:info] {bitcoin-node-57287/b-capnp-loop-6497836} IPC server: socket disconnected.
2025-10-08T07:19:16Z [ipc:info] {bitcoin-node-57287/b-capnp-loop-6497836} IPC server destroy N2mp11ProxyServerIN3ipc5capnp8messages4InitEEE
Connect (-debug=ipc):
2025-10-08T07:19:44Z [ipc] {bitcoin-node-57788/b-capnp-loop-6502845} IPC server recv request #1 Init.construct$Params
2025-10-08T07:19:44Z [ipc] {bitcoin-node-57788/b-capnp-loop-6502845} IPC server send response #1 Init.construct$Results
2025-10-08T07:19:44Z [ipc] {bitcoin-node-57788/b-capnp-loop-6502845} IPC server recv request #2 Init.makeMining$Params
2025-10-08T07:19:44Z [ipc] {bitcoin-node-57788/b-capnp-loop-6502845} IPC server post request #2 {bitcoin-node-57788/6502989 (from sv2-tp-57803/6502987)}
2025-10-08T07:19:44Z [ipc] {bitcoin-node-57788/b-capnp-loop-6502845} IPC server send response #2 Init.makeMining$Results
The former seems too chatty, the latter too quiet. Maybe only have the "socket disconnected" message be at the info level and introduce a "socket connected" message.