Skip to content

docs: backend logging convention #100

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AquiGorka merged 1 commit into from
May 31, 2026
+406 −0
Merged

docs: backend logging convention #100

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -232,6 +232,8 @@ cd e2e && docker compose up --abort-on-container-exit

## Debugging test failures with traces

Backend logs follow the convention in [logging.md](logging.md): five-method Logger (`info` / `event` / `debug` / `error` / `scope`), service-injection, and `handle<X>(deps)` route factories. Logger and OTEL run side-by-side, not merged.

Every test suite exports OTEL traces to Jaeger, and Jaeger persists them to disk at `.traces/<suite>/`. After a test run (pass or fail), you can inspect the traces by starting a Jaeger instance against the persisted data:

```bash
Expand Down
Loading
Loading