ProxTrace
GitHubPublic repository coming soon Open console

Demo · sample data

This morning, erp-db stopped responding. Find what changed.

The ProxTrace console, read-only, on fictional organisations including cluster pve-prod. Everything is computed in your browser: no real data, nothing is saved.

Open the demo full screenOpen the demo console

Scopepve-prod3 nodes · Administrator

Collector connected

Sample data

Events

pve-prod

Week of 5 Octoberpve-prod
Events for the week (example)
WhenEventResourceAuthor
Thu 14:32:07qemu:104 - erp-dbadmin@pve
Thu 14:05:51qemu:112 - gitlabroot@pam
Thu 13:58:20lxc:201 - dns-introot@pam
Thu 13:41:02qemu:118 - win-rdsci@pve!deploy
Thu 13:12:44node:pve-02admin@pve
Thu 11:20:36lxc:203 - proxy-introot@pam
Thu 10:02:15qemu:112 - gitlabadmin@pve
Wed 15:03:48qemu:104 - erp-dbadmin@pve
Tue 22:51:37node:pve-01root@pam
Tue 02:00:11lxc:201 - dns-introot@pam
Mon 16:40:05lxc:201 - dns-introot@pam
Mon 09:14:22qemu:104 - erp-dbadmin@pve

Simple view · correlated steps grouped together12 events

Change · qmconfig

Configuration changed

When
2026-10-08 14:32:07 CEST
Resource
qemu:104 - erp-db
Node
pve-02
Author
admin@pve
Source IP
10.20.0.31
Result
Succeeded
Category
Change
Before / after
ParameterBeforeAfter
cores48
balloon08192
EvidenceUPID:pve-02:0003A1F2:0B5C3D21:6705F1A7:qmconfig:104:admin@pve:

Machines

pve-prod

Machines6 guests
Machine inventory (example)
MachineNodeStateLatest backup
pve-02 Running Succeeded · 08/10 02:04
pve-03 Running Succeeded · 08/10 02:11
pve-03 Stopped None observed
pve-01 Running Succeeded · 08/10 02:20
pve-02 Running Failed · 08/10 13:58
pve-01 Running Succeeded · 08/10 02:26
QEMU VM

qemu:104 - erp-db

Node
pve-02
State
Running
Resources
8 vCPU · 16 GiB
Guest agent
Enabled, responding
Observed IP
10.20.30.14
Latest backup
Succeeded · 08/10 02:04

History for the week

  1. Thu 08/10 14:32qmconfig
  2. Wed 07/10 15:03api.firewall
  3. Mon 05/10 09:14qmconfig

Security & compliance

pve-prod

Check registerreport from 08/10, 14:35
Check register (example)
Ref.CheckVerdict
14.1 Fail
5.3 Fail
17.5 Not assessable
2.3-04 Out of scope
2.1 Pass
3.1 Pass
Check 14.1

Backups and retention

Fail

lxc:201 - dns-int: two consecutive failures (06/10 02:00, 08/10 13:58), no successful backup since 05/10.

Values by node

pve-01
2 guests · successful backups
pve-02
lxc:201 failed · qemu:104 succeeded
pve-03
qemu:112 succeeded · none observed for qemu:118
Suggested action
Free up space on pbs-01 storage or review its retention, then run the backup for 201 again.
Sources
vzdump tasks, storage state
Evidence limitation
Backup contents have not been verified: a restore has not been tested.

Attention

pve-prod

Attention4 items
Attention queue (example)
SeverityItemFollow-upActions
HighBackup failed, 2 occurrences
Backups · lxc:201 - dns-int
Attention
Mediumroot@pam login outside business hours
Proxmox access · node:pve-01
Attention
Mediumpbs-01 storage at 91%
Storage · storage:pbs-01
In progress
LowNo backup observed
Backups · qemu:118 - win-rds
Deferred

Demo: follow-up stays on this page; nothing is saved.

Coverage

pve-prod

Sources by host collector connected · outbound queue 0
Source freshness by host (example)
HostAPISSH readerLogs
pve-01 Up to date Up to date Up to date
pve-02 Up to date Up to date Up to date
pve-03 Up to date Delayed · 47 min Up to date

Checks that use the SSH reader on pve-03 remain “Not assessable” while the source is delayed.

Sample data, read-only: actions are disabled and the AI assistant is not simulated, as its answers depend on your data and the model you configure.

The same views, on your cluster: