User guideWayseer 0.28.3Contents

Installing on Windows

Wayseer runs on Windows 10 and 11, on x86-64 PCs. It comes two ways, each holding one program, wayseer.exe, with every data source built in (SQL and Kubernetes among them), and SDL3 3.4.16, the library that opens the window and draws:

Installer

Download wayseer-<version>-windows-x86_64.msi from wayseer.app, from 0.28.0 on; it is served beside the zip, at https://wayseer.app/v1/app/<version>/. Open the .msi. It asks for an administrator's approval, installs into C:\Program Files\Wayseer\, and adds Wayseer to the Start menu. Opening a newer installer replaces the older version. To remove it, go to Settings → Apps → Installed apps, find Wayseer, and choose Uninstall.

To check the installer, compare its SHA-256, from Get-FileHash wayseer-<version>-windows-x86_64.msi in PowerShell, with its line in the SHA256SUMS file served beside it, at https://wayseer.app/v1/app/<version>/SHA256SUMS.

Portable zip

Extract the zip anywhere, and open wayseer.exe in the folder it makes. Keep the files together: wayseer.exe finds SDL3.dll beside it. To remove it, delete the folder.

Both packages keep the config and state in the same place, %APPDATA%\Wayseer\ and %LOCALAPPDATA%\Wayseer\ (where files are kept).

The first time you open it

A package without a code-signing certificate, which is how the build script makes them, shows Windows protected your PC the first time it is opened. Choose More info, then Run anyway. It does not ask again for that file.

What it shows

From 0.28.0, a first run opens on this PC: its CPUs, memory, drives, network interfaces, processes and services (this machine). A config written by 0.27 has the kind: localhost entry commented out, since the module didn't run on Windows then; remove the # before its two lines to show the PC.

From a terminal

wayseer.exe is a windowed program, so opening it opens no console. Run from a terminal, it still prints there, for --help, --print-config and its log:

& "C:\Program Files\Wayseer\wayseer.exe" --help

Because it is windowed, the terminal does not wait for it: the prompt comes back at once, and its output follows. PowerShell does not redirect a windowed program's output, so to keep it in a file, or to read its exit code, go through cmd.exe or Start-Process:

cmd /c '"C:\Program Files\Wayseer\wayseer.exe" --print-config > config.yaml'
(Start-Process "C:\Program Files\Wayseer\wayseer.exe" -ArgumentList --help -Wait -PassThru).ExitCode

Modules

SQL, Kubernetes and every other module in this guide are built into wayseer.exe. A module of your own runs once it is a signed package, installed with >modules.install into the state directory, and runs without a console window of its own (external modules).