Optimize logging to reduce verbosity while preserving critical network events (#432)

- Remove excessive verbose logging (DISCOVERY, INCOMING, PEER-UPDATE, etc.)
- Preserve critical network state logs (RESTORE, handshake failures, security events)
- Change routine key operations from info to debug level
- Add successful peer connection log after handshake completion
- Fix compiler warnings for unused variables
- Achieve ~95% reduction in log volume while maintaining debugging capability

Co-authored-by: jack <jackjackbits@users.noreply.github.com>
This commit is contained in:
jack
2025-08-11 23:45:59 +02:00
committed by GitHub
co-authored by jack
parent 04c2b0caa6
commit 3226b9cd14
8 changed files with 31 additions and 152 deletions
+1 -7
View File
@@ -190,8 +190,6 @@ class NostrRelayManager: ObservableObject {
if error == nil {
// Successfully connected to Nostr relay
self?.updateRelayStatus(urlString, isConnected: true)
SecureLogger.log("Successfully connected to Nostr relay \(urlString)",
category: SecureLogger.session, level: .info)
} else {
SecureLogger.log("Failed to connect to Nostr relay \(urlString): \(error?.localizedDescription ?? "Unknown error")",
category: SecureLogger.session, level: .error)
@@ -293,9 +291,7 @@ class NostrRelayManager: ObservableObject {
case "NOTICE":
if array.count >= 2,
let notice = array[1] as? String {
SecureLogger.log("📢 Relay notice: \(notice)",
category: SecureLogger.session, level: .info)
let _ = array[1] as? String {
}
default:
@@ -397,8 +393,6 @@ class NostrRelayManager: ObservableObject {
let nextReconnectTime = Date().addingTimeInterval(backoffInterval)
relays[index].nextReconnectTime = nextReconnectTime
SecureLogger.log("Scheduling reconnection to \(relayUrl) in \(Int(backoffInterval))s (attempt \(relays[index].reconnectAttempts))",
category: SecureLogger.session, level: .info)
// Schedule reconnection with exponential backoff
DispatchQueue.main.asyncAfter(deadline: .now() + backoffInterval) { [weak self] in