Streamlogia agent

One binary that ships a host’s system logs and host metrics — CPU, memory, disk, network — to your Streamlogia project. Linux, macOS and Windows. No runtime, no collector, no config file to write.

Install on Linux or macOS

curl -fsSL https://get.streamlogia.com/install.sh | sudo sh -s -- --key ls_src_live_…
Replace the key with the one shown when you created the source.

Install on Windows

iwr -useb https://get.streamlogia.com/install.ps1 | iex
From an Administrator PowerShell. It asks for the key.

Within a minute the host’s journal lines appear in the project under the Infra toggle, and the host appears on the source’s Host tab with its gauges updating every ten seconds.

What it does

LogsThe systemd journal, a syslog file, the Windows event log, or macOS unified logging — whichever this host has. Severity is mapped to ERROR/WARN/INFO/DEBUG. It resumes from where it stopped after a restart, and starts at “now” on a fresh install rather than replaying history.
MetricsEvery ten seconds: CPU, load and steal, memory and swap, every real filesystem, disk and network throughput, uptime and process count.
ServiceRegisters with systemd, OpenRC, launchd or the Windows service manager, whichever the host runs, and starts at boot.
IdentityThe key decides the project. The agent never chooses where data lands.

Manage it

streamlogia-agent status            # is it running?
streamlogia-agent sample            # print one sample and exit
journalctl -u streamlogia-agent -f  # what it is doing
sudo streamlogia-agent uninstall    # stop, disable, remove

Options

Anything after -- is passed to the installer:

--keythe source’s ingest key (required)
--hostreported host name (default: the kernel’s)
--intervalmetrics cadence, default 10s
--logsship the host’s logs; on by default except on macOS, where unified logging is too noisy to ship unasked
--no-logshost metrics only
--no-metricslogs only
--apiAPI base URL, for a self-hosted install

Requirements

Linux with systemd or OpenRC, macOS 10.11 or later, or Windows Server 2016 and Windows 10 or later; amd64 or arm64 throughout. It runs with administrative privileges because reading every service’s log requires it. It opens no listening port and writes only its own config and state.

Prefer to read a script before piping it to a shell? Both are right here: install.sh and install.ps1.