Skip to Content
ConfigurationDebug Page

Debug Page

Tracearr includes a debug page at /debug for troubleshooting and advanced maintenance. This page is not linked from the main navigation — access it directly at:

http://your-tracearr:3000/debug

The debug page is owner only. The server checks the role on every /debug request, and nothing blocks the route in the browser, so anyone else who opens the URL gets the page with every panel failing to load.

System Information

The debug page displays real-time system stats:

  • Node.js version, platform, and architecture
  • Uptime — how long Tracearr has been running
  • Memory usage — heap and RSS memory consumption
  • Environment variables — sanitized view of configuration

Database Statistics

View database health and size information:

  • Record counts — sessions, violations, users, servers, rules, library items
  • Database size — total storage used
  • Table sizes — breakdown by table and TimescaleDB aggregates

Logs

Where Tracearr’s logs live depends on how you installed it. The retrieval commands for every platform are on Collecting Logs. This page covers what the debug page itself gives you.

LOG_LEVEL is read once when the server starts. Raising it to debug takes an environment edit and a restart, and the restart throws away the docker logs history you were about to collect. Capture your logs first, then raise the level and reproduce.

Standard Docker Logs

The standard latest image runs tracearr, tracearr-db and tracearr-redis as separate containers, and each one keeps its own log. Collecting Logs has the docker logs commands, including the redirect that keeps stderr.

Proxmox VE LXC Logs

In a Proxmox VE LXC the three services run under systemd, but only Tracearr keeps its real log in the journal. PostgreSQL and Redis write theirs to files under /var/log, and Collecting Logs covers both sources.

Supervised Logs

The supervised image runs everything in one container under supervisord, which sends each program’s two streams to its own file in /var/log/supervisor/. The debug page reads those files in a Log Explorer panel.

Log FileWhat it holds
tracearr.logApplication stdout
tracearr-error.logApplication stderr
postgres.logPostgreSQL stdout
postgres-error.logPostgreSQL stderr
redis.logRedis stdout
redis-error.logRedis stderr
supervisord.logSupervisor process manager

Take both halves of a pair. A service picks its own stream, and the file named for errors is regularly the substantive one: supervisord routes stderr to the -error.log file, and PostgreSQL sends its entire server log to stderr. Tracearr runs the other way. On a measured install it wrote 19,110 lines to stdout against 24 to stderr.

Download All packages every file that exists into tracearr-logs-<timestamp>.zip, through GET /debug/logs/download. That zip is what you attach to a bug report.

The Log Explorer returns at most 1000 lines and 256 KiB per file, newest first, and it cannot reach the rotated backups. Read it in the browser, and attach the zip from Download All instead.

The panel is gated on the running image tag containing supervised, not on what is installed in the container. A pinned digest or a retagged image reads Log explorer is only available in Docker environments in the browser, and the endpoints answer Log explorer is only available in supervised mode.

Snapshot Management

View and clean up library snapshots. Useful for removing suspicious or corrupted snapshot data that may affect Library Growth charts.

Maintenance Actions

ActionDescription
Refresh AggregatesManually refresh TimescaleDB continuous aggregates
Clear Stuck JobsReset jobs that show “already running” but aren’t progressing

Use Clear Stuck Jobs when a maintenance job in Settings → Jobs says “already running” but shows no progress. This clears stale job state from a previous crash.

Danger Zone

These actions permanently delete data and cannot be undone. Use with caution.

ActionWhat it deletes
Clear ViolationsAll violation records
Clear RulesAll detection rules and their violations
Clear Termination LogsAll stream termination history
Clear Library CacheAll library metadata and snapshots
Clear SessionsAll session history, violations, and termination logs
Clear UsersAll non-owner users and their associated data
Clear ServersAll servers (cascades to users, sessions, violations, library)
Factory ResetEverything except your owner account — returns Tracearr to initial setup state
Last updated on