Logging is needed before background import work begins so failures are diagnosable.
## Scope
- PSR-3 compatible logger writing structured lines to stdout for Docker capture
- Configurable level
- Correlation identifier for import jobs so one run can be traced
## Acceptance criteria
- [ ] Logs emitted to stdout and visible via `docker compose logs`
- [ ] Level configurable through environment
- [ ] Job-scoped context included in import log lines
---
Blocked by: #8
keith
added this to the M1 - Docker & Dev Environment milestone 2026-10-10 22:18:20 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Logging is needed before background import work begins so failures are diagnosable.
Scope
Acceptance criteria
docker compose logsBlocked by: #8
Acceptance reconciliation at
c1ef2ee: structured Monolog stdout logging and independent job context are implemented with logging tests. Historical M1 runtime reports cover PHP-FPM log forwarding. Fresh full suite: 291 tests, 1801 assertions, 22 skips; lint passes. Closing this logging foundation issue, not claiming arbitrary exception messages are universally redacted.