Your question
I’ve upgraded from Stalwart 0.14 to 0.15.15 then to 0.16.5 and finally got everything working… however one part isn’t… my logs (Maintenance → Observability → Logs) show nothing. I feel like something’s changed and logging isn’t configured properly anymore, but not sure how to fix… and I’m trying to diagnose issues without visibility of logs. It’s kind of confusing. Can someone point me in the right direction please?
I understand that topics in this category are triaged by a bot first but a human reply will follow up. If I’d prefer a human-only reply, I’ll add the no-ai tag to my topic.
on
The logs view in the WebUI (Management > Observability > Logs) requires the log entries to be persisted to the history store by the tracing subsystem. After an upgrade the tracer configuration may not have carried over correctly. Here are the things to check, in order:
1. Check your Tracer is enabled and configured correctly
Go to Settings > Telemetry > Tracers in the WebUI. You should have at least one tracer. If it’s missing, or if the enable field is false, logs won’t be produced at all. If there’s no tracer, create one via New and use the defaults. The tracer type determines where log lines go:
Log - writes rotating files to diskStdout / Console - writes to standard output (appropriate for Docker/containers)Journal - writes to systemd journal
Make sure the tracer’s level is set to at least info.
2. Understand what the WebUI Logs view actually reads
The Logs page in the WebUI reads from the history store (the same database Stalwart uses for data storage), not directly from log files on disk. For this to work, the tracing subsystem must be writing events to Stalwart’s internal store. The tracer just controls external output destinations; the in-app log view is always populated from the internal store as long as the tracer is active and events are being generated.
3. If you’re on a binary (non-Docker) install
Verify that /var/log/stalwart exists and is writable by the stalwart user. If not, create it and set ownership with chown stalwart:stalwart /var/log/stalwart. Then delete and recreate the tracer in the WebUI to reset any stale path configuration.
4. Quick reset path
If the tracer config looks mangled from the upgrade, the cleanest fix is: delete the existing tracer at Settings > Telemetry > Tracers, then create a fresh one using the defaults.
Relevant docs:
This is an automated reply from the Stalwart Help Bot. Other community members may follow up if this answer is incomplete or wrong. If you found it useful, mention @helpbot in any reply to ask follow-up questions and the bot will respond again.
It appears to log just fine to console / log files, but the webUI log view shows no entries.. when it should (things about delivery, receipts, etc) .. it did this in 0.14 just fine, but in 0.16 its empty…
Make sure you have at lease one log file logger enabled. The log viewer does not work when using console, journald or other mechanisms. You need at least one log tracer enabled.