fix(wireguard): emit UTC log timestamps#47
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
This pull request changes WireGuard log timestamps to use explicit UTC timestamps with a
Zsuffix.The previous WireGuard log timestamp format used local time without timezone information. That made logs harder to compare with panel events, API events, and external monitoring systems.
WireGuard Logging
backend/wireguard/log.go.backend/wireguard/wireguard_lifecycle_test.go.Why This Is Better
Node logs are often compared with panel-side events when debugging traffic accounting, sync behavior, or node restarts. Local timestamps without timezone information make that comparison ambiguous.
Using UTC with
Zmakes ordering clear across machines, timezones, containers, and log collectors.