chore: setting dialing canceled log to trace (#1153)

We are trying to reduce the logs load in our fleets, and one of the most
recurrent one is

```
Dialing canceled                           topics="libp2p dialer" tid=1 file=dialer.nim:67 err="Future operation cancelled!" peerId=16U*XAFJX3
```

which is quite spammy and doesn't give much info. 

In addition to that, its corresponding `Dialing address` log is in
trace.

So adjusting the log level of `Dialing canceled` to trace :)
This commit is contained in:
gabrielmer 2024-07-23 15:14:18 +03:00 committed by GitHub
parent b5fb7b3a97
commit f8d4da6421
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions

View File

@ -62,7 +62,7 @@ proc dialAndUpgrade(
libp2p_total_dial_attempts.inc() libp2p_total_dial_attempts.inc()
await transport.dial(hostname, address, peerId) await transport.dial(hostname, address, peerId)
except CancelledError as exc: except CancelledError as exc:
debug "Dialing canceled", err = exc.msg, peerId = peerId.get(default(PeerId)) trace "Dialing canceled", err = exc.msg, peerId = peerId.get(default(PeerId))
raise exc raise exc
except CatchableError as exc: except CatchableError as exc:
debug "Dialing failed", err = exc.msg, peerId = peerId.get(default(PeerId)) debug "Dialing failed", err = exc.msg, peerId = peerId.get(default(PeerId))