Debug Logging
Settings > System & Monitoring > Debug Logging: master toggle, log level, outputs (file/console/database), context options, and sensitive-field redaction.
Debug Logging
Configure verbose logging for troubleshooting and debugging system issues.
Use this page to raise verbosity for support investigations, choose where logs go, and protect sensitive fields. Disable or lower verbosity when troubleshooting ends.
Where to find everything: Administration Settings.
Related: Audit Logs for user-facing activity history.
Actions
- Reset to defaults
- Save settings
Debug logging toggle
- Enable comprehensive logging — when on, diagnostic detail (timestamps, request identifiers, stack traces where applicable) is collected per your deployment.
- Turn off after the issue is captured to reduce noise and overhead.
Log level
- Log level — dropdown (for example Info — errors, warnings, and info messages).
- Help text explains that higher levels include all lower-level messages.
Typical scale (exact names vary):
| Level | Use |
|---|---|
| Error | Failures only — closest to production default |
| Warning | Failures plus likely problems |
| Info | Operational lifecycle events |
| Debug | Verbose troubleshooting (high volume) |
Output configuration
Checkboxes for destinations (availability depends on deployment):
- Log to file — persistent files for sharing with support.
- Log to console — real-time viewing.
- Log to database — queryable storage when enabled.
Context configuration
- Include timestamp in log entries
- Include user context in log entries
Enable only what you need—user context can increase sensitivity of log content.
Sensitive data configuration
A security notice explains that values matching configured patterns are redacted automatically.
- Sensitive field patterns (comma-separated) — name-like tokens for headers or fields to mask (for example authorization, password, token).
Never rely on redaction alone: avoid logging secrets at the source.
Older or alternate UIs
Some builds also show log files with Refresh and Download for on-disk logs. If your screen matches that pattern, use Download to attach logs to support tickets.
Best practices
- Enable verbose logging only during reproduction, then revert.
- Capture time window, user, and steps alongside the log file.
- Combine with audit logs to correlate who changed what before failures.
Related articles
Related articles
- Administration Settings · Product documentation
- Server Connection · Product documentation
- Proxy Settings · Product documentation
- License Management · Product documentation
- User Management · Product documentation
- Role Permissions · Product documentation
Next steps
- Getting started · Install + connect your spec
- Configuration fundamentals · Stabilize runs
- Initial configuration · Users, licensing, projects
- Release notes · Updates and fixes
Still stuck?
Tell us what you’re trying to accomplish and we’ll point you to the right setup—installation, auth, or CI/CD wiring.