While the Websites and Servers tabs allow you to view downtime logs for individual assets, the global Incidents tab (accessed via the main left-hand sidebar) serves as your command center. It aggregates every historical outage, resource breach, and connection drop across your entire Veyon workspace into a single, unified view.
This macro-level dashboard is essential for managing fleet-wide stability, auditing long-term reliability, and exporting comprehensive Service Level Agreement (SLA) reports.
1. Global Management Controls & Data Export
At the top right of the dashboard, a centralized toolkit allows you to organize, filter, and extract your historical logs:
Create New Incident (Blue
NewButton): Unlike automated monitor alerts, this button allows you to manually generate an incident. This is heavily utilized for logging planned maintenance windows, scheduling anticipated downtime, or documenting manual server reboots for your clients to see on public Status Pages.Search Input: Instantly query your entire infrastructure history by typing a specific monitor name (e.g.,
WatchWavezorMicrosoft), an error code, or a date string.Filter Utility (funnel icon): Refine the massive global list to isolate specific incident severities, or filter to view only active, unresolved network drops.
Display Toggle (list icon): Adjusts the visual density and layout spacing of the incident grid to your preference.
Export Utility (download icon): Generates a downloadable CSV or PDF file of your fleet's downtime history based on your active filters—perfect for executive reporting or client SLA reviews.
2. The Fleet-Wide Triage Table
The core grid compiles every workspace incident into a highly scannable, standardized format, utilizing pagination at the bottom (e.g., Showing 1-10 of 78) to manage massive historical logs efficiently.
| Column | Description |
| Status Icon | A visual indicator of the alert's lifecycle. A red exclamation mark (❗) signifies an active, ongoing outage. A green checkmark (🟢) confirms the disruption has been resolved and the asset is healthy. |
| Monitor | Identifies the specific asset that failed. The blue title (e.g., WatchWavez or bhavanijewels.com) is a direct hyperlink; clicking it will jump you straight to that monitor's specific dashboard. Directly underneath the title, the table prints the sanitized root cause of the failure (e.g., No data or cURL error 28: Connection timed out). |
| Duration | The cumulative downtime window. For prolonged outages or maintenance events, this scales dynamically from minutes and seconds up to days and months (e.g., 1 mo and 3 w or 22 m and 21 s). |
| Started at | The exact timestamp (yyyy-mm-dd hh:mm:ss) when the monitoring agent registered the initial connection failure. |
| Ended at | The precise timestamp the monitor recovered. If the node is currently offline and actively failing checks, this column prominently displays a red Ongoing badge. |
Action Menu (...) | The contextual menu allowing you to acknowledge the alert, append internal engineering notes, or permanently delete the log entry. |