Install the agent

One command. The token is already in it — you do not create one.

Linux · macOS

curl -fsSL https://get.anyglance.net | sudo sh -s -- --token=ag_ins_7Kq2v9xR

No curl (a fresh Debian, for example)? Change curl -fsSL to wget -qO-. Logged in as root with no sudo? Leave out sudo.

Picks the build for your OS and CPU, verifies the checksum, installs the .deb and starts anyglance-agent.service. On macOS it unpacks a tar.gz and starts a launchd daemon instead.

Windows Server

msiexec /i https://get.anyglance.net/anyglance-agent_amd64.msi TOKEN=ag_ins_7Kq2v9xR SERVERURL=https://ingest.anyglance.net /qn

Installs the anyglance-agent service. Silent, so it works from a GPO.

What it needs

NetworkOutbound HTTPS (443) to ingest.anyglance.net. Nothing listens on the server.
Ubuntu20.04 or newer · systemd
Debian12 or newer · systemd
CentOS Stream9 or newer · systemd
openSUSE Leap16 or newer · systemd
Amazon Linux2023 · systemd
WindowsServer 2016 or newer
macOS13 Ventura or newer · Apple Silicon
CPULinux: x86-64 or arm64 · Windows: x86-64 · macOS: Apple Silicon
GPUOptional. NVIDIA on Linux, any vendor on Windows (usage and memory), Apple GPU on macOS.
Footprint~9 MB binary · reports every 10 seconds · about 1.5 MB per server per day

Configuration

The agent is configured by a file, not by a GUI. On Linux it lives at /etc/anyglance/agent.env, on Windows at %ProgramData%\anyglance\agent.env, on macOS at /Library/Application Support/anyglance/agent.env.

# where this agent reports
ANYGLANCE_SERVER_URL=https://ingest.anyglance.net
# Install token — used only for the first registration. One token, one server.
#ANYGLANCE_INSTALL_TOKEN=ag_ins_...
# Only if outbound 443 is blocked. Empty means the standard HTTPS_PROXY is used.
#ANYGLANCE_PROXY_URL=http://proxy.example.com:3128

Alert thresholds are not in this file. They live on the server, so you change them once in the dashboard instead of editing a file on every machine over SSH.

Uninstall

Linux

sudo apt remove anyglance-agent

macOS

sudo launchctl bootout system/net.anyglance.agent
sudo rm -f /Library/LaunchDaemons/net.anyglance.agent.plist /usr/local/bin/anyglance-agent
sudo rm -rf "/Library/Application Support/anyglance" /Library/Logs/anyglance

Windows

Settings → Apps → anyglance-agent → Uninstall, or in PowerShell as administrator:

Get-CimInstance Win32_Product -Filter "Name='anyglance-agent'" | Invoke-CimMethod -MethodName Uninstall

From version 0.2.9 this also deletes %ProgramData%\anyglance (settings and identity). Don't uninstall with msiexec /x and a freshly downloaded MSI — if it is a different version from the installed one, it removes nothing and still reports success.

We do not add an APT repository to your sources. The package installs; it does not sign you up for anything else.

Removing the agent does not remove the server from your list — you get an unreported alert after 3 minutes. To remove it, open the server and use Delete in Server settings.

If a server doesn't show up

Wait a few minutes after installing: the onboarding page tells you whether the agent never reached us or reached us and then stopped. If you need to dig further:

NetworkThe agent needs outbound HTTPS (443) to ingest.anyglance.net. Behind a proxy, set ANYGLANCE_PROXY_URL in the settings file and restart the agent.
Install tokenOne token registers one server and closes when it is used. Tokens don't expire, but revoked ones are refused. For another server, get a new token from Add server.
Logs Linux journalctl -u anyglance-agent -n 50
macOS /Library/Logs/anyglance/agent.log
Windows Event Viewer → Windows Logs → Application, source anyglance-agent
Restart Linux sudo systemctl restart anyglance-agent
macOS sudo launchctl kickstart -k system/net.anyglance.agent
Windows Restart-Service anyglance-agent

Scheduled maintenance

Until the service is stable, we may perform maintenance up to once a month. We announce it at least 3 days ahead by email and with a notice at the top of the app after you sign in. It usually takes less than an hour. The agent keeps about 20 minutes of reports and sends them afterwards — nothing to do on your servers. If maintenance runs longer, metrics for the rest of that time may be missing and alerts may not be sent.