Skip to content

Diagnostic logs

What it's for

When a device misbehaves, you can get its Valenius logs without remote access, screen sharing, or asking the user to dig through folders. The client collects a small, redacted bundle — Valenius-related logs only, with keys and secrets stripped on the device before anything is uploaded — and sends it to your backend.

How to use it

Pull (admin-initiated):

  1. Open the client's Details → Diagnostics tab.
  2. Click Request logs. The device picks the request up on its next check-in and uploads a bundle.
  3. Download it from the same tab once it arrives; delete bundles you no longer need. The newest ten per client are kept.

Push (user-initiated): every client has a Send logs action the user can trigger themselves — see For users. The bundle lands in the same Diagnostics tab.

What's inside depends on the platform: the Valenius service/daemon logs, the updater's install log, and the WireGuard® log on desktop; the app's own event log on mobile. Always Valenius-scoped — never general system logs, browser history, or personal files — and always with API keys, VPN keys, and codes redacted.

Pitfalls

  • An offline device can't upload. The request waits for its next check-in — if the machine's problem is "no network," you won't get logs until it's back.
  • Only the newest ten bundles per client are kept — download anything you want to preserve before it rotates out.
  • The redaction is deliberate. If a support case seems to need more than the bundle contains, that's a signal to look at the backend's own logs alongside, not to widen collection on the device.