Logs
Server Logs is a tab of the Activity page (/activity/logs) and gives access to system log files organized by category. Both the selected server and the category are in the address (/activity/logs/{category}?server=site-3), so a view can be linked to a colleague and lands on the same relay. The old /logs address still works and redirects here.
Log Tabs
Relay Sync Logs (Core Only)
Per-relay-site log files showing sync operations:
- Heartbeat requests and responses
- Manifest requests and hash comparisons
- Image and driver stream transfers
- Sync completion confirmations
- Errors and retry attempts
Log files follow the naming pattern: logs/sync/relay-{siteName}-{yyyyMMdd}.log
Each relay site gets its own log file, making it easy to troubleshoot sync issues for a specific location.
Image Activity (Core Only)
Audit trail of image-related operations:
- WIM uploads and registrations
- WIM customization job events
- Image deletions
- ISO uploads and removals
Deployment Logs
Deployment log entries from the DeploymentLog database table. Filterable by machine and recipe. Shows:
- Timestamp
- Log level (Info, Warning, Error)
- Machine identifier
- Phase name
- Message
PXE and TFTP: moved to PXE Activity
The PXE and TFTP log is not a category here. It lives on Activity > PXE Activity, on the
PXE / TFTP Log tab next to the live wire events and the TFTP fetch test, so network boot has one
destination instead of two: /activity/pxe/log.
The old address /activity/logs/pxe (and the older /logs/pxe) redirects there, keeping the
selected server: /activity/logs/pxe?server=site-3 lands on that relay's log.
See PXE Boot for what the log contains.
Certificates
The same application log files as the System view, narrowed to certificate lifecycle entries.
Certificate work happens in the background with no screen of its own, so this is usually the only place to see that it happened at all:
- ACME account registration, order, issuance and renewal
- Rotation of this server's own HTTPS certificate - the new certificate is staged, relays acknowledge the new thumbprint, and only then is it activated
- Organization CA activity: root generation, subordinate CA request and import against your enterprise PKI
- Connected Cache node certificate issuance and renewal, per relay site
- Expiry warnings for the server certificate and for cache node certificates
The exception detail underneath a failed entry is kept, so a failed renewal shows why it failed.
Because certificate entries are sparse in a busy log, this view scans much deeper into the file than the System view does before filtering. The search box narrows further within the result - for example, type a site name to see only that cache node's certificates.
Direct link: /activity/logs/certificates. This view reads the local server's own files, so it is not offered
when a relay site is selected in the server dropdown - open that relay's own Logs page instead.
Sync Log (Relay Only)
The relay's perspective on sync operations:
- Heartbeat send/receive
- Manifest downloads and comparisons
- Image and driver downloads with progress
- Sync completion status
Log file: logs/sync/relay-sync-{yyyyMMdd}.log
Log Viewer
All log tabs display entries with:
- Most recent entries first
- Timestamp formatting
- Color-coded log levels
- Text search within displayed entries
Log File Management
Log files use daily rolling - a new file is created each day. The SyncLogService and PxeLogService singletons handle thread-safe writing with automatic file rotation.
Log files are stored relative to the application directory:
| Log Type | Path |
|---|---|
| Sync logs | logs/sync/ |
| PXE logs | logs/pxe/ |
| Application logs | logs/ (via Serilog) |
Relay Log Tabs
Relay servers show only:
- Sync Log - Local sync operations with Core
- System and Certificates - the relay's own application log (a relay receives its Connected Cache node certificate and imports Core's rotated thumbprint, so it has certificate entries of its own)
Core-only tabs (Relay Sync, Image Activity) are hidden on Relay servers. The relay's PXE and TFTP log is on Activity > PXE Activity, the same as on Core.
When a relay site is selected in the server dropdown on Core, the categories are Sync, System and PXE/Imaging Clients (the deployment agent's own lines, streamed up from the relay - client output, not PXE server activity).