Skip to content

[signal] adjust log levels #3813

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 12, 2025
Merged

[signal] adjust log levels #3813

merged 1 commit into from
May 12, 2025

Conversation

pascal-fischer
Copy link
Collaborator

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 Copilot AI review requested due to automatic review settings May 12, 2025 15:01
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adjusts log levels in the signal service to reduce log verbosity and better align with production requirements. The changes include reordering the dispatcher import for improved clarity, switching log levels in the server from Debugf to Tracef, and downgrading warning messages in the peer package from Warnf to Debugf.

Reviewed Changes

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

File Description
signal/server/signal.go Reordered dispatcher import; log level changed from Debugf to Tracef.
signal/peer/peer.go Log level changes: duplicate registration and removal logs updated from Warnf to Debugf.
Comments suppressed due to low confidence (3)

signal/peer/peer.go:82

  • Ensure that lowering the log level from Warnf to Debugf for duplicate peer registration does not hide critical warnings during runtime.
log.Debugf("peer [%s] is already registered [new streamID %d, previous StreamID %d]. Will override stream.", peer.Id, peer.StreamID, pp.StreamID)

signal/peer/peer.go:107

  • Confirm that reducing the log severity for ignoring newer stream removal is intentional and won't mask potential issues.
log.Debugf("attempted to remove newer registered stream of a peer [%s] [newer streamID %d, previous StreamID %d]. Ignoring.", peer.Id, pp.StreamID, peer.StreamID)

signal/server/signal.go:73

  • Verify that adjusting the log level from Debugf to Tracef meets the intended verbosity requirements. If needed, document the rationale for this change.
log.Tracef("received a new message to send from peer [%s] to peer [%s]", msg.Key, msg.RemoteKey)

Copy link

@pascal-fischer pascal-fischer merged commit 20f59dd into main May 12, 2025
32 checks passed
@pascal-fischer pascal-fischer deleted the chore/log-level-on-signal branch May 12, 2025 17:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants