[signal] adjust signal log levels 2

[pascal-fischer]

Describe your changes

Issue ticket number and link

Stack

Checklist

• Is it a bug fix
• Is a typo/documentation fix
• Is a feature enhancement
• It is a refactor
• Created tests that fail without the change (if possible)
• Extended the README / documentation, if necessary

[Copilot]

Pull Request Overview

This PR adjusts the log levels for signal operations to reduce verbosity in production logs.

• Changed the log level in message forwarding from Warn to Trace
• Changed the log level in peer registration from Debug to Trace

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
signal/server/signal.go	Downgraded error log level when forwarding messages
signal/peer/peer.go	Downgraded log level when a peer is already registered

Comments suppressed due to low confidence (2)

signal/peer/peer.go:82

• Lowering the log level from Debug to Trace for duplicate peer registration may reduce the visibility of potential conflicts; please ensure that this change aligns with the overall logging strategy for peer management.

log.Tracef("peer [%s] is already registered [new streamID %d, previous StreamID %d]. Will override stream.", peer.Id, peer.StreamID, pp.StreamID)

signal/server/signal.go:172

• Changing the error log level from Warn to Trace may hide important error details in production; consider verifying that less severe logging is acceptable for error reporting in this context.

log.Tracef("error while forwarding message from peer [%s] to peer [%s] %v", msg.Key, msg.RemoteKey, err)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud