Monitoring

Run as a block:

# 1. Backend
curl -s http://localhost:8000/health

# 2. Scheduler
curl -s http://localhost:8001/health

# 3. Frontend (HTTP 200)
curl -s -o /dev/null -w '%{http_code}' http://localhost

# 4. Redis
docker exec trinity-redis redis-cli ping

# 5. MCP Server
curl -s http://localhost:8080/health

# 6. Vector (log aggregation)
docker exec trinity-vector wget -q -O - http://localhost:8686/health

Check disk and Docker space:

df -h /
docker system df

Container log rotation

Docker's default JSON log driver has no size limit, and an unbounded container log will eventually fill the Docker data root and wedge the whole fleet at once. Trinity therefore caps every container it controls — platform services and agent containers alike — at 10 MB per file, 3 files, by default.

Both are validated in both directions: a malformed value and an absurd-but-well-formed one (over 1 GB, or more than 10 files) fall back to the bounded default and log a warning. There is no way to configure an unbounded log.

These apply at container creation, so platform services adopt a change on the next docker compose up, and existing agents on recreate— not on a plain restart.

This only shortens the history available to docker logs. Vector's aggregate at /data/logs is the primary queryable record and keeps its own LOG_RETENTION_DAYS; live log streaming in the UI is unaffected by rotation.

Check trinity.db size:

# Development (named volume)
docker run --rm -v trinity_trinity-data:/data alpine ls -lh /data/trinity.db

# Production / hosted (bind mount)
ls -lh /srv/trinity-data/trinity.db

Backups and retention

The database backs itself up nightly at 03:30 UTC and before every migration. Check it without a shell — the block reports the last run's status, the age of the newest success, artifact count and bytes:

curl -s -H "Authorization: Bearer <token>" http://localhost:8000/api/settings/retention | jq .backup

A failed or skipped backup raises an item in Operations → Needs Response; a “backups are stale” alarm repeats weekly while the newest success is older than three days. The same endpoint reports every retention window in force — each is an explicit per-install setting (written at the values already in effect the first time a release boots without them), so an upgrade never changes what your instance keeps. Windows, the blast-radius guard and admin approval of large prunes: Operations → Monitoring. Backup details: Backup and Restore.

Structured logs (via Vector)

# Platform logs (backend, scheduler, MCP server)
docker exec trinity-vector sh -c "tail -50 /data/logs/platform.json" | jq .

# Agent logs
docker exec trinity-vector sh -c "tail -50 /data/logs/agents.json" | jq .

# Filter for errors
docker exec trinity-vector sh -c "cat /data/logs/platform.json" | jq 'select(.level == "ERROR")'

On Docker Desktop, start.sh switches Vector to an on-disk log source and the local files land at /data/logs/local-*.json instead.

Container logs (Docker directly)

docker compose logs -f backend
docker compose logs -f frontend
docker compose logs -f scheduler
docker logs trinity-backend --tail 100