aboutsummaryrefslogtreecommitdiff
path: root/doc/README_windows.txt
diff options
context:
space:
mode:
authorJon Atack <jon@atack.com>2022-06-01 13:44:59 +0200
committerJon Atack <jon@atack.com>2022-08-20 11:55:17 +0200
commit45f92821621a60891044f57c7a7bc4ab4c7d8a01 (patch)
treebf88cecd3bfd10339019bc3f0af92bf29eaab394 /doc/README_windows.txt
parent2a8712db4fb5d06f1a525a79bb0f793cb733aaa6 (diff)
Create BCLog::Level::Trace log severity level
for verbose log messages for development or debugging only, as bitcoind may run more slowly, that are more granular/frequent than the Debug log level, i.e. for very high-frequency, low-level messages to be logged distinctly from higher-level, less-frequent debug logging that could still be usable in production. An example would be to log higher-level peer events (connection, disconnection, misbehavior, eviction) as Debug, versus Trace for low-level, high-volume p2p messages in the BCLog::NET category. This will enable the user to log only the former without the latter, in order to focus on high-level peer management events. With respect to the name, "trace" is suggested as the most granular level in resources like the following: - https://sematext.com/blog/logging-levels - https://howtodoinjava.com/log4j2/logging-levels Update the test framework and add test coverage.
Diffstat (limited to 'doc/README_windows.txt')
0 files changed, 0 insertions, 0 deletions