Expand description
Constants for categorizing the logging type
To help stabilize logging targets, avoid typos and improve consistency, it’s preferable for logging statements use static target constants, that we define in this module.
Core + server side components should use global namespace,
while client should generally be prefixed with client::.
This makes it easier to filter interesting calls when
running e.g. devimint, that will run both server and client
side.
Structs§
- Tracing
Setup - Consolidates the setup of server tracing into a helper
Constants§
- LOG_
BITCOIND - LOG_
BITCOIND_ CORE - LOG_
BITCOIND_ ESPLORA - LOG_
CLIENT - LOG_
CLIENT_ BACKUP - LOG_
CLIENT_ DB - LOG_
CLIENT_ EVENT_ LOG - LOG_
CLIENT_ MODULE_ LN - LOG_
CLIENT_ MODULE_ LNV2 - LOG_
CLIENT_ MODULE_ META - LOG_
CLIENT_ MODULE_ MINT - LOG_
CLIENT_ MODULE_ WALLET - LOG_
CLIENT_ NET_ API - LOG_
CLIENT_ REACTOR - LOG_
CLIENT_ RECOVERY - LOG_
CLIENT_ RECOVERY_ MINT - LOG_
CONSENSUS - LOG_
CORE - LOG_DB
- LOG_
DEVIMINT - LOG_
GATEWAY - LOG_
MODULE_ LN - LOG_
MODULE_ LNV2 - LOG_
MODULE_ META - LOG_
MODULE_ MINT - LOG_
MODULE_ WALLET - LOG_NET
- LOG_
NET_ API - LOG_
NET_ AUTH - LOG_
NET_ PEER - LOG_
NET_ PEER_ DKG - LOG_
RUNTIME - LOG_
TASK - LOG_
TEST - LOG_
TIMING