Monitoring the platform
When something goes wrong, the panel already wrote down what happened. This page maps the common questions to the page that answers them.
What it is
Section titled “What it is”VirtConsole keeps its own activity records. Every background operation, every recurring job, every admin action, every outgoing email and every IP address change is written somewhere you can read. This page maps a question to the page that answers it; the pages themselves are one click away in the sidebar.
Where to look
Section titled “Where to look”| Question | Page | What it shows |
|---|---|---|
| Why did this deploy fail? | Tasks at Tasks | Every background operation with live progress and a step-by-step log. |
| Is the daily backup actually running? | Scheduler at System > Scheduler | Every recurring job with its last run, 7-day health and run history. |
| Who deleted this user? | Admin Audit Log at Logs > Audit log | Every admin action with the actor, the resource and the changed values. |
| Did the suspension email go out? | Email Log at Logs > Email log | Every outgoing email with recipient, subject and delivery status. |
| Where was this IP assigned? | IP Log at Logs > IP log | Every IP address assignment, revocation and transfer. |
| Did the cluster react to a dead hypervisor? | HA Events at Logs > HA events | Fencing, evacuation and NAT failover events. |
| Which devices are signed in right now? | Sessions at System > Sessions | Every active panel session with IP and user agent. |
| What did the gateways tell us? | Webhook Log at Billing > Webhook log | Every payment webhook received, with signature status. |
How to use it
Section titled “How to use it”Start from the symptom:
- A customer-visible operation failed. Find it in Tasks and read the task log. The last line tells you whether the panel, the queue or the hypervisor’s agent stopped answering.
- Something that should run on a schedule did not. Open System > Scheduler, find the job and check its Health (7d). If every job’s last run is stale, the scheduler on the management server is not running at all.
- A change happened that nobody admits to. Filter the Admin Audit Log by actor, action or resource type and open the entry to see the old and new values.
- A customer says they never got an email. Search the Email Log for their address. A missing row means the panel never sent one; a failed row shows why.
Key rules
Section titled “Key rules”- These pages are read-only records. Nothing you do on them changes platform state.
- The audit log records panel actions. Changes made directly on the management server’s command line do not appear in it.
- Customers never see these pages. They see only their own tasks and their own resource metrics in the user panel.
Traffic direction
Section titled “Traffic direction”Network charts, alert metrics (network_rx, network_tx) and bandwidth figures use the guest’s point of view: receive is download and transmit is upload, for KVM and Proxmox instances alike. When 3.3.1 moved KVM to this view, existing alert rules on KVM resources were migrated by exchanging the two metrics, so each rule still watches the same traffic. Account-wide rules over a fleet that mixes KVM and Proxmox resources were not changed; review them. Alert history written before the update still names the old metric.
Common problems
Section titled “Common problems”- Every log page is empty on a fresh install. That is expected. Records appear as soon as the first actions happen.
- The audit log is missing an action an admin swears they did. They ran it on the command line instead of the panel, or a different admin account did it. Filter by the other account.
- The same internal IP appears on every session and log entry. A reverse proxy in front of the panel is not forwarding the real client IP. Check your proxy configuration on the management server.