-
Notifications
You must be signed in to change notification settings - Fork 0
Logs
root edited this page May 30, 2026
·
1 revision
Recollectium writes structured JSON logs for diagnostics while keeping CLI stdout reserved for command output. CLI output is human-readable by default and can be switched to JSON with cli_output or --json; logs still stay out of stdout.
Logs use the XDG state path by default:
~/.local/state/recollectium/logs/
You can override the logs directory with directories.logs in config.
Defaults:
{
"logging": {
"level": "info",
"format": "json",
"max_bytes": 10485760,
"backup_count": 5
}
}Update log level:
recollectium config set logging.level debugOverride for one command:
recollectium --log-level debug listManaged services redirect stdout and stderr to service log files in the configured logs directory.
Common files include:
service-api.logservice-mcp.log- Rotated backups based on
logging.max_bytesandlogging.backup_count
Use logs to diagnose:
- Config loading and validation problems.
- Database and migration issues.
- Service startup and shutdown behavior.
- Service discovery cleanup.
- Embedding readiness and re-embedding jobs.
- Runtime failures that are hard to see from CLI output alone.
Logs should not include:
- Memory content.
- Full metadata payloads.
- Credentials, tokens, passwords, API keys, or private keys.
- Sensitive local secrets.
If you share logs in an issue, review them first and replace anything sensitive with [REDACTED].
FAQ
- Is Recollectium cloud-hosted?
- Does Recollectium encrypt the database?
- Does the API have authentication?
- Does the WebUI have authentication?
- Which embedding model does it use?
- Should agents search by type first?
- What is the difference between
dev serveandservice start api? - Can I run Core on one machine and an agent on another?
- Is the OpenCode plugin available?