[nudgebee-dev]

Description

In pkg/ws/client.go within the Client.Run reconnection loop, session termination errors returned by c.connectAndServe(ctx) are logged at Error severity (c.logger.Error("websocket session ended", "err", err)). During transient disconnects or routine connection renegotiation with the relay, the client automatically recovers via exponential backoff reconnects. However, logging at Error severity increments container_log_messages_total{level="error"} and triggers benign ForagerServiceLogErrors Prometheus alerts.

This change demotes the log severity from Error to Warn (c.logger.Warn("websocket session ended", "err", err)), avoiding triggering benign alerts while preserving visibility into session terminations.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Enhancement (non-breaking change which improves existing functionality)
• Refactor (non-breaking change which improves code structure)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation
• CI/CD

Original Error/Logs

Click to expand the original error that triggered this fix

Change log severity for websocket session ended from Error to Warn in Client.Run reconnection loop. PR #172 in nudgebee/forager already implements this fix.

Files located during the investigation: pkg/ws/client.go

The investigation already read this code:
**Code examined**

- `pkg/ws/client.go`:120-123 — Logs websocket session termination at Error level during Client.Run reconnect loop

err := c.connectAndServe(ctx)
if err != nil {
c.logger.Error("websocket session ended", "err", err)
}

If part of the requested change is already present in the code above, do not repeat it: implement the part that is missing. If the whole request is already satisfied, make no change and report that, citing the code that satisfies it.

How Has This Been Tested?

• Unit tests
• Manual testing

Checklist

• CLA signed (the CLA bot will prompt on your first PR)
• make validate passes (fmt + lint + test)
• Docs updated if the wire shape, config surface, or proxy module behavior changed

---

🤖 This PR was automatically generated by NudgeBee AI coding agent

Powered by AI-driven code analysis and automated fix generation

🔍 View Original Investigation

Click the link above to see the full investigation and analysis that led to this fix

View Detailed Nubi Conversation

---

✅ Verification

Build verification passed for the affected modules.

Commands run

PASSED (cd . && go build ./...) exit=0