Server Logs Settings
Server Logs Settings controls journald retention and maximum storage for operating-system and SDM service history.
Where to find it: Cluster Settings > Server Logs, or the root Server Logs Settings page.
Available to: root.
What this page does
The page shows configured and effective journal limits, current use, oldest/newest coverage, and whether the installation needs the standard policy upgrade. Prune/rotate applies the policy immediately.
Before you start
Check incident and compliance requirements before reducing history. Export logs needed for an open investigation and confirm available disk capacity.
Journal policy
- Retention: minimum 30 days and maximum 3,650 days.
- Storage: minimum 5 GB and maximum 1,024 GB.
- Save: writes the journald policy; stored history may remain larger until rotation/prune runs.
- Prune now: rotates journals and removes archived data outside the current time/storage policy.
- Coverage: reports the oldest/newest available messages and the effective limit, not a promise that every service emitted logs continuously.
Controls and fields
| Control, Field, Or Section | What It Does | What It Affects | Recommended Usage |
|---|---|---|---|
| Logs history coverage | Shows how many days of server logs are represented and the policy coverage limit. | Tells support whether logs cover the troubleshooting window. | Check before investigating older incidents. |
| Events stored since / Most recent log | Shows oldest and latest server log timestamps. | Verifies continuity of log history. | Missing recent logs can indicate logging/service problems. |
| Storage usage | Shows used log storage against allocated storage. | Reveals whether log storage is close to the configured budget. | Increase allocation on busy clusters or noisy services. |
| Server Log Retention Minimum | Minimum days of server logs to keep. | Controls how far back log-based troubleshooting can go. | Keep at least 30 days for production support. |
| Server Log Storage Allocation | GB budget for server log storage. | Controls log storage pressure and cleanup policy. | Use enough capacity for expected query/service volume. |
| Last prune run | Shows the last manual/automated log prune time. | Indicates cleanup recency. | Review before running another prune. |
| Save Policy | Saves log retention and storage allocation. | Changes future log storage behavior. | Save after adjusting capacity or retention; confirm warning notice clears. |
| Prune Now | Rotates journald and removes archived logs outside policy after hostname confirmation. | Permanently removes old server log files. | Export evidence before pruning and avoid during incident response. |
Safety notes
- Too little retention can remove evidence needed to diagnose intermittent DNS, cluster, or login problems.
How to use it
- Read configured/effective days, storage, current use, and coverage.
- Set values within the documented limits and save.
- Confirm the effective policy.
- Prune only when immediate enforcement is intentional.
- Open Logs and verify recent messages plus the oldest expected window.
Result and next check
Journald enforces the intended time and storage policy and the Logs page can retrieve the expected history. Older archived messages removed by pruning are not restored by increasing the limit later.
Theme color