Logs: debug your project and agents
The Architect (and the box's ops token). The detailed log (/razadmin/logs, GET /api/v2/logs) is noisy by design: every request (method, address, project, who, status, time taken), every flow's start and end, everything the audit log records or leaves out (test and demo activity), the server's warnings, errors and stack traces, and logs uploaded by clients such as the Obsidian plugin. Read it one day at a time, filtered by level, kind, project and text. Every request has an id, shown in its answer, that finds its lines here.
Retention
- Kept on each server: 14 days, one file per day (gzipped after a day), then deleted. There is no archive: what you need from it, take within 14 days.
- Each server has its own: the page and
GET /api/v2/logsread the log of the server that answers. - When a disk is critical, self-healing may delete the oldest log files first.
Reading the logs
Read one day at a time, filtered by level, kind, project and text.
- "Why did this request fail?" Every answer carries a request id. Put it in the text filter to get all the lines for that request, from start to error.
- "What errors did my project have today?" Pick today, level error, and your project.
- "Is the Obsidian plugin syncing?" Filter the kind to the clients' uploaded logs.
- Searching: each field lists the records whose value contains the text, ignoring case, and every field you fill in has to match. Password and token hashes and session ids are never shown.
- Audit page: Records older than the kept days (Settings:System) move to each project's files, in
_archive/, a whole UTC day at a time; unlike the detailed log, audit records are archived.