The Checks tab serves as an exhaustive, chronological ledger tracking every independent communication handshake between Veyon and your server. While the Overview tab summarizes these events, the Checks view exposes the raw networking data of every single cron or daemon check execution, making it an invaluable tool for analyzing micro-outages or tracking intermittent packet loss.
Log Controls & Filtering
At the top right of the logs window, you can use two precise management tools to navigate your history:
- Search Bar: Quickly look up specific execution data or narrow down logs to a highly specific window by typing a date string or timestamp.
- Filter Utility (funnel icon): Click to isolate entries by operational status, allowing you to quickly filter out all successful handshakes and view only the checks that encountered connection drops or system errors.
The Historical Telemetry Table
The checks table translates every connection check into seven distinct data fields:
Column | Description |
Status | A color-coded indicator providing an instant look at the check's success. A green dot (🟢) indicates a fully successful transmission, while a red dot (🔴) marks a failed communication attempt. |
Code | The explicit HTTP response status code returned by the server interaction. A green |
Time | The exact network execution speed or latency measured in milliseconds (ms) for the transmission block to finalize (e.g., |
Size | The total payload data size of the transmission box. For internal server monitoring agent metrics, this will typically display a dash ( |
Location | The specific monitoring node or interface endpoint executing the validation script. If the agent communicates directly from your private infrastructure pipeline, it may log as |
Error | If a check fails, this field becomes your first line of diagnostics. It will display a dash ( |
Checked at | Provides high-precision timestamping. It displays a relative time tracker (e.g., |