feat(gui-client): configure IPC service to log to stdout

[thomaseizinger]

On Linux, logs sent to stdout from a systemd-service are automatically captured by journald. This is where most admins expect logs to be and frankly, doing any kind of debugging of Firezone is much easier if you can do journalctl -efu firezone-client-ipc.service in a terminal and check what the IPC service is doing.

On Windows, stdout from a service is (unfortunately) ignored.

To achieve this and also allow dynamically changing the log-filter, I had to introduce a (long-overdue) abstraction over tracing's "reload" layer that allows us to combine multiple reload-handles into one. Unfortunately, neither the reload::Layer nor the reload::Handle implement Clone, which makes this unnecessarily difficult.

Related: #8173

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
firezone	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 23, 2025 0:09am

[thomaseizinger]

cc @oddlama

[thomaseizinger]

Tested in Linux VM, works as intended.

[jamilbk]

Does this log to journald and log file still? If not, probably want to update /kb/client-apps/linux-gui-client and /kb/administer/logs docs.

[thomaseizinger]

Does this log to journald and log file still? If not, probably want to update /kb/client-apps/linux-gui-client and /kb/administer/logs docs.

Logs to stdout in addition now. I can update the docs to reflect that.

[thomaseizinger]

It would be nice to remove the logging to a file but then we'd have to integrate with journald for the log export. Honestly, that might actually be easier than writing the logs ourselves to a file and zip that.

[jamilbk]

How we do it for Android & Apple is log to file and then also the platform idiomatic log sink, so this seems like a step closer to that.

I think the Windows event viewer is a common sink too