Skip to content

webrtc: reduce loglevel for pion logs#2915

Merged
sukunrt merged 2 commits intomasterfrom
disable-pion-logging
Aug 15, 2024
Merged

webrtc: reduce loglevel for pion logs#2915
sukunrt merged 2 commits intomasterfrom
disable-pion-logging

Conversation

@sukunrt
Copy link
Member

@sukunrt sukunrt commented Aug 8, 2024

closes #2909

@sukunrt sukunrt changed the title webrtc: reduce pion logs loglevel webrtc: reduce loglevel for pion logs Aug 8, 2024
@sukunrt sukunrt requested a review from MarcoPolo August 8, 2024 11:06
Copy link
Collaborator

@MarcoPolo MarcoPolo left a comment

Choose a reason for hiding this comment

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

Hopefully we can revert this someday

@sukunrt sukunrt force-pushed the disable-pion-logging branch from 53c0798 to d6ab77f Compare August 15, 2024 15:53
@sukunrt sukunrt merged commit 285123a into master Aug 15, 2024
@Stebalien Stebalien deleted the disable-pion-logging branch August 15, 2024 17:09
sukunrt added a commit that referenced this pull request Sep 9, 2024
lidel added a commit that referenced this pull request Nov 11, 2025
Pre-v0.44 (Working State):
PR #2915 deliberately downgraded all pion logs to Debug level because
"Pion logs are too noisy and have invalid log levels". This worked
correctly for ~1 year without issues.

v0.44.0 (Regression):
PR #3364 migrated from go-log/v2 to log/slog but accidentally reverted
the pion log level downgrade. The migration kept the comment claiming
logs were downgraded but changed the implementation to log Error/Warn/Info
at their face values, causing routine connection events to spam error logs.

Similar to PR #3413 which fixed this issue for websocket transport,
WebRTC transport needs the same treatment. Pion logs client disconnects,
protocol mismatches, and state races as ERROR/WARN, but these are normal
operational noise from a service perspective, not actual errors requiring
operator attention.

This restores PR #2915 behavior: downgrade all pion logs to Debug level.

Fixes ipfs/kubo#11053
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.

The new WebRTC transport is very noisy

2 participants