lightningdevkit
Log available liquidity on each channel when starting routefinding
One of the most common first-steps in troubleshooting routefinding issues is we ask for the local channel state to determine what the available HTLC bounds are. Thus, we really should be logging the bounds instead, which we do here.
Isn't this more or less redundant since we already log next_outbound_htlc_limit_msat for any first-hops we ignore?:
https://github.com/lightningdevkit/rust-lightning/blob/f5ee8c23a1a52bc51c00eb8a62b0b5226acee80b/lightning/src/routing/router.rs#L2178-L2183
That won't tell us if the channel is disabled or otherwise missing, but, fair point, it does answer it in some cases.
Rebased and updated a bit, I think this this is worth doing, and also took the opportunity to log the limit that is violated any time we log that we're not using a channel, rather than only when its a first-hop.