From 92b24c0add18342aafe051ed6e52a5faeb4d7815 Mon Sep 17 00:00:00 2001
From: Jari Sundell <sundell.software@gmail.com>
Date: Fri, 24 Oct 2025 22:41:09 +0900
Subject: [PATCH] Updated LOG Logging (markdown)

---
 LOG-Logging.md | 169 +++++++++++++++++++++++++++----------------------
 1 file changed, 93 insertions(+), 76 deletions(-)

diff --git a/LOG-Logging.md b/LOG-Logging.md
index 99e4a06..c66e95b 100644
--- a/LOG-Logging.md
+++ b/LOG-Logging.md
@@ -21,8 +21,9 @@ Adding outputs to events
 
     log.add_output = "info", "rtorrent.log"
 
-    log.add_output = "dht_debug", "tracker.log"
-    log.add_output = "tracker_debug", "tracker.log"
+    log.add_output = "dht_all", "tracker.log"
+    log.add_output = "tracker_events", "tracker.log"
+    log.add_output = "tracker_requests", "tracker.log"
 ```
 
 Each log handle can be added to multiple different logging events.
@@ -47,77 +48,93 @@ Thus some high-volume sub-group events such as “tracker\_debug” are not
 part of “debug” and every “warn” event will receive events from “error”,
 “critical”.
 
-    critical
-    error
-    warn
-    notice
-    info
-    debug
-    dht_critical
-    dht_error
-    dht_warn
-    dht_notice
-    dht_info
-    dht_debug
-    peer_critical
-    peer_error
-    peer_warn
-    peer_notice
-    peer_info
-    peer_debug
-    socket_critical
-    socket_error
-    socket_warn
-    socket_notice
-    socket_info
-    socket_debug
-    storage_critical
-    storage_error
-    storage_warn
-    storage_notice
-    storage_info
-    storage_debug
-    thread_critical
-    thread_error
-    thread_warn
-    thread_notice
-    thread_info
-    thread_debug
-    tracker_critical
-    tracker_error
-    tracker_warn
-    tracker_notice
-    tracker_info
-    tracker_debug
-    torrent_critical
-    torrent_error
-    torrent_warn
-    torrent_notice
-    torrent_info
-    torrent_debug
-    
-    connection
-    connection_bind
-    connection_fd
-    connection_filter
-    connection_hanshake
-    connection_listen
-    dht_all
-    dht_manager
-    dht_node
-    dht_router
-    dht_server
-    instrumentation_memory
-    instrumentation_mincore
-    instrumentation_choke
-    instrumentation_polling
-    instrumentation_transfers
-    peer_list_events
-    protocol_piece_events
-    protocol_metadata_events
-    protocol_network_errors
-    protocol_storage_errors
-    resume_data
-    rpc_events
-    rpc_dump
-    ui_events
+```
+  critical
+  error
+  warn
+  notice
+  info
+  debug
+
+  peer_critical
+  peer_error
+  peer_warn
+  peer_notice
+  peer_info
+  peer_debug
+
+  socket_critical
+  socket_error
+  socket_warn
+  socket_notice
+  socket_info
+  socket_debug
+
+  storage_critical
+  storage_error
+  storage_warn
+  storage_notice
+  storage_info
+  storage_debug
+
+  thread_critical
+  thread_error
+  thread_warn
+  thread_notice
+  thread_info
+  thread_debug
+
+  torrent_critical
+  torrent_error
+  torrent_warn
+  torrent_notice
+  torrent_info
+  torrent_debug
+
+  connection
+  connection_bind
+  connection_fd
+  connection_filter
+  connection_hanshake
+  connection_listen
+
+  dht
+  dht_all
+  dht_error
+  dht_controller
+  dht_node
+  dht_router
+  dht_server
+
+  instrumentation_memory
+  instrumentation_mincore
+  instrumentation_choke
+  instrumentation_polling
+  instrumentation_transfers
+
+  mock_calls
+
+  net_dns
+
+  peer_list_events
+  peer_list_address
+
+  protocol_piece_events
+  protocol_metadata_events
+  protocol_network_errors
+  protocol_storage_errors
+
+  resume_data
+
+  rpc_events
+  rpc_dump
+
+  storage
+  system
+
+  tracker_dump
+  tracker_events
+  tracker_requests
+
+  ui_events
+```