Skip to content

Local Agent

Nick Wilkinson edited this page Jul 6, 2026 · 3 revisions

Local Agent

The local agent reports services from a Linux host, primarily systemd units.

Use it for machines where Docker/Kubernetes/Proxmox is not the right abstraction, or where you want host-level service visibility.

Typical deployment

The local agent is normally installed as a systemd service on the host it monitors.

The repository includes:

deploy/systemd/trove-agent-local.service

Common configuration

Variable Required Purpose
TROVE_SERVER_URL yes Trove server URL reachable from the host.
TROVE_TOKEN yes Trove agent token.
TROVE_INTERVAL no Push interval.
TROVE_AGENT_NAME no Agent display name.

Install shape

A typical install looks like:

sudo install -m 0755 trove-agent-local /usr/local/bin/trove-agent-local
sudo install -m 0644 deploy/systemd/trove-agent-local.service /etc/systemd/system/trove-agent-local.service
sudo install -m 0600 /dev/null /etc/trove-agent-local.env

Then edit:

/etc/trove-agent-local.env

with:

TROVE_SERVER_URL=http://YOUR-SERVER:8080
TROVE_TOKEN=trove_xxxxxxxx
TROVE_INTERVAL=30s
TROVE_AGENT_NAME=my-linux-host

Enable and start:

sudo systemctl daemon-reload
sudo systemctl enable --now trove-agent-local
sudo systemctl status trove-agent-local

Read-only boundary

The local agent should query service state. It should not start, stop, restart, enable, disable, or modify units.

Troubleshooting

Check logs:

journalctl -u trove-agent-local -f

Common failures:

  • wrong TROVE_SERVER_URL
  • invalid TROVE_TOKEN
  • firewall blocking the server
  • systemd command not available in the runtime environment

Clone this wiki locally