From 45f92821621a60891044f57c7a7bc4ab4c7d8a01 Mon Sep 17 00:00:00 2001 From: Jon Atack Date: Wed, 1 Jun 2022 13:44:59 +0200 Subject: 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. --- src/logging.h | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'src/logging.h') diff --git a/src/logging.h b/src/logging.h index 1288efa0fe..fe91ee43a5 100644 --- a/src/logging.h +++ b/src/logging.h @@ -69,7 +69,8 @@ namespace BCLog { ALL = ~(uint32_t)0, }; enum class Level { - Debug = 0, // High-volume or detailed logging for development/debugging + Trace = 0, // High-volume or detailed logging for development/debugging + Debug, // Reasonably noisy logging, but still usable in production Info, // Default Warning, Error, -- cgit v1.2.3