[JuliusHenke]

Requested by ju · project thread

Summary

/actuator/logfile only serves the current log file. That file used to roll over daily, so the weekly import health check could only see the logs since midnight. Archived logs were also never deleted.

• The file now rolls over weekly, so the endpoint shows up to a week of logs. It still rolls early at 10 MB, as before.
• The pattern uses YYYY-ww (week-based year). I checked this with logback 1.5.38: yyyy-ww would name the files for 2026-12-27 to 12-31 2026-01 and collide with January 2026.
• Archived logs are kept for maxHistory 13 (logback counts this in rollover periods, here weeks, so about 90 days), capped at 1 GB with totalSizeCap.

Weeks start on the JVM locale's first day of the week (Sunday for en_US). At the start of a week the current file only holds a day or two.

Testing

• RollingCalendar detects YYYY-ww as TOP_OF_WEEK. Across the 2026/2027 year boundary, files are named 2026-52, then 2027-01, then 2027-02.
• I loaded the config with JoranConfigurator. It logs without warnings or errors, and the status output confirms totalSizeCap 1 GB.

Deployment notes

No action required. The old daily archives (logs/archived/spring-boot-logger-YYYY-MM-DD.N.log) don't match the new pattern, so logback won't delete them and they don't count towards the 1 GB cap. Delete them by hand if you want the space back.

---

Generated by Claude Code