Skip to main content
The Termique monitoring agent runs on a Linux host and reports CPU, memory, and disk usage to your account every 30 seconds. You see live values and history in the desktop app, and you can add alert rules that notify you when usage crosses a threshold or the host stops reporting.
Monitoring works on synced hosts. On Free, a host kept only on this computer shows This host is only on this computer on its Monitoring tab. Click Sync this host to enable monitoring.

​
Install the agent

  1. Open the host and select the Monitoring tab.
  2. Click Install agent.
  3. Review what the agent does, then click Agree & continue. Termique creates an agent token and an install command for this host.
  4. Optional: set up security events in the same dialog.
  5. Install the agent:
    • Click Run over SSH to open a session to the host and run the command there, or
    • Click Copy under Run on host and run the command yourself.
The dialog shows Waiting for the agent to check in… until the first report arrives, then Agent connected, and closes. The Monitoring tab then shows live metrics for the host.
Install the agent dialog with the masked install command, Detect security sources, and the Security events switch
The install command has this form. The token and server ID are masked on screen, and Copy and Run over SSH use the real values:
The agent token is shown once. Expand Manual setup - show token to see and copy it before you close the dialog. Anything you copy from this dialog is cleared from the clipboard after 1 minute.
If you close the dialog before the agent checks in, the Monitoring tab shows Waiting for the agent. Click Show install command to get a fresh command, or Refresh to check again.

​
What the agent collects

  • CPU, memory, and disk usage, every 30 seconds. Memory includes cached and swap figures when the host reports them.
  • Uptime, and the disk device and mount point it measures.
  • Nothing else: no file contents, command output, or credentials.
The agent only sends data. It never accepts inbound connections. The install script writes a config file holding an opaque token at ~/.config/termique-agent/config.toml (chmod 600) and registers a systemd service.

​
Config file

The app sets most options for you. To edit config.toml directly, for example on a host you manage over a plain SSH session: Restart the agent to apply changes:
Reinstalling writes a fresh config.toml and overwrites manual edits. Use automatic updates for routine version updates, not a reinstall.

​
Security events

Optional, off by default. When enabled, the agent watches a fixed set of sources and reports structured events, never raw log lines or request bodies:
  • Failed and successful SSH logins, from auth.log or secure.
  • fail2ban bans and unbans, if fail2ban is installed.
  • HTTP error-rate spikes: many 4xx and 5xx responses from one IP within a minute.
  • HTTP path-targeted brute force: many requests to the same path from one IP within a minute, whatever the response status. This catches login-form brute force, which usually returns 200 for every attempt.
Security events are evidence for Incident investigation. The app does not show them as a standalone log.

​
Enable it

In the install dialog:
  1. Optional: click Detect under Detect security sources. Termique checks the host over SSH for an auth log, fail2ban, and a reverse-proxy access log, then fills in the settings below.
  2. Turn on Security events.
  3. To detect HTTP brute force, enter your web server’s access log under Reverse proxy access log, for example /var/log/nginx/access.log. Use an absolute path with letters, numbers, ., _, -, and / only. Any other path is left out of the install command.
On an agent that is already installed, add the fields to config.toml instead. See Config file.

​
Check that capture works

While the agent reports, the host’s Monitoring tab lists each source under Security sources as Active or Inactive. If capture is on but no source was found, the tab warns that investigations will have no security evidence until you fix it.

​
Retention

The agent sends captured events in batches every 2 minutes. Events are kept for 14 days on Free and 90 days on Pro.

​
View metrics

​
On the host

The host’s Overview tab shows a Health card with live CPU, memory, and disk usage. The Monitoring tab shows:
  • The agent status: Reporting with the time of the last update, or Agent offline with when it was last seen.
  • CPU, memory, and disk charts for 1 hour, 24 hours, or 7 days.
  • View charts, which opens the full detail page.

​
Monitoring page

Click Monitoring in the sidebar to see every host with a reporting agent. The sidebar shows how many agents are reporting, for example 3/4.
  • Hosts are grouped by group. Each row shows CPU, memory, and disk usage, when the agent last reported, and any alert that is on.
  • Hosts lists all monitored hosts. Alerts lists hosts where an enabled rule is over its threshold right now. Not monitored lists synced hosts without an agent, each with Install agent.
  • Values refresh every 10 seconds. A host counts as online if it reported within the last 2 minutes.
  • Usage of 70% or more is highlighted.
Monitoring page listing hosts by group with CPU, memory, and disk usage, agent status, and alerts

​
Detail page

Click a host on the Monitoring page, or View charts on its Monitoring tab, to open its detail page:
  • Live resources: CPU, memory (with cached memory), disk (with mount point and file system), and swap if the host has any, from the most recent report. Bars turn amber at 70% and red at 90%.
  • History: CPU, RAM, and disk on one chart, for 1h, 6h, 24h, 7d, 30d, or 1y.
  • The side panel: status, uptime, last seen, linked host, access (Owner or Shared with you), and the server ID.
Monitoring detail page with live CPU, memory, and disk bars, the history chart, and the agent side panel

​
Data retention

Raw reports are kept for 24 hours on every plan. Longer ranges use rolled-up averages, kept by plan: The 1y range needs Pro. For a shared host, the owner’s plan sets the limit.

​
Alert rules

Add rules from the Alerts section of the host’s Monitoring tab. It appears once the agent has reported at least once. Click Add alert rule and set: A CPU, RAM, or Disk rule fires when a report is above the threshold. Each host can have up to 20 rules. Turn a rule on or off with its switch. Deleting a rule shows Undo for a few seconds. You can also manage rules on the mobile app from a host’s Manage alerts screen.

​
Notifications

  • Desktop: while Termique is running, it checks your rules every minute and shows a system notification when one fires. Available on every plan.
  • Mobile push: on Pro, alerts arrive as push notifications on the mobile app, even when the desktop app is closed. The notification names the host and metric, for example CPU threshold exceeded, but not the value. Tap it to open the host’s alert rules.
Push notifications require a Pro subscription. On Free, rules only notify through the desktop app.

​
Automatic updates

The agent checks for a new version once a day, at about 03:00 server time (with up to 30 minutes of random delay), and updates only if one is available. If it is already on the latest version, nothing happens: no reinstall, no restart. If an update fails to start correctly, the agent restores the previous version and restarts. No manual recovery is needed. To turn off automatic updates:
  • At install time, set TERMIQUE_AUTO_UPDATE=false before running the install command.
  • On an installed agent, add auto_update = false to ~/.config/termique-agent/config.toml. This takes effect on the next daily check, with no restart.
With automatic updates off, the agent stays on its installed version until you reinstall it.

​
Revoke, reinstall, or uninstall

  • Revoke: on the host’s Monitoring tab, click the trash icon (Revoke monitoring token), or click Revoke token on the detail page. Confirm with Revoke token. The agent stops reporting within 30 seconds but keeps running on the host until you uninstall it.
  • Reinstall: on the Monitoring tab, click the reinstall icon (Reinstall agent with a new token). Termique revokes the current token and shows a new install command, without the terms step.
  • Uninstall: run this on the host. The detail page shows it under Uninstall with a copy button.
An agent that stops reporting for 5 days is revoked automatically, and you get an email. Reinstall it to resume monitoring.

​
Shared hosts

If a host is shared with you and the owner installed the agent, you can see its metrics and history. Installing, revoking, and alert rules stay with the owner. See Sharing.