diff options
author | Jon Atack <jon@atack.com> | 2022-06-01 13:44:59 +0200 |
---|---|---|
committer | Jon Atack <jon@atack.com> | 2022-08-20 11:55:17 +0200 |
commit | 45f92821621a60891044f57c7a7bc4ab4c7d8a01 (patch) | |
tree | bf88cecd3bfd10339019bc3f0af92bf29eaab394 /src/test/util | |
parent | 2a8712db4fb5d06f1a525a79bb0f793cb733aaa6 (diff) | |
download | bitcoin-45f92821621a60891044f57c7a7bc4ab4c7d8a01.tar.xz |
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 'src/test/util')
-rw-r--r-- | src/test/util/setup_common.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/test/util/setup_common.cpp b/src/test/util/setup_common.cpp index 872310f1ca..e8e96b9051 100644 --- a/src/test/util/setup_common.cpp +++ b/src/test/util/setup_common.cpp @@ -108,7 +108,7 @@ BasicTestingSetup::BasicTestingSetup(const std::string& chainName, const std::ve "-logsourcelocations", "-logtimemicros", "-logthreadnames", - "-loglevel=debug", + "-loglevel=trace", "-debug", "-debugexclude=libevent", "-debugexclude=leveldb", |