Updated LOG Logging (markdown)

LOG-Logging.md

@@ -47,15 +47,77 @@ 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”.
 
-    "connection_*"
+    critical
-    "dht_*"
+    error
-    "peer_*"
+    warn
-    "rpc_*"
+    notice
-    "storage_*"
+    info
-    "thread_*"
+    debug
-    "tracker_*"
+    dht_critical
-    "torrent_*"
+    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
     
-All sub-groups have events from “critical” to “debug” defined.
+    connection
-
+    connection_bind
-___This documentation is out of date, to be updated___
+    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