Skip to main content
Migration Notice
We're migrating documentation from the old portal into this one. Some things may look a little different or out of place in the meantime — we know, and we're working to get it right. If something's unclear or doesn't look right, let us know.

Agent Fleet Management — Log Collection

How agent log collection works​

Agents periodically zip their on-disk log files and push the archive to the console so you can download and inspect them from the GUI without needing SSH access to the agent host.

  • Collection interval: every N minutes each agent zips its current log files and POSTs the archive to the console. The temp zip is deleted from the agent after a successful send — only the rolling log files remain on disk.

  • Console storage: the console keeps exactly one zip per agent (data/logs/agents/{agentId}.zip). Each push overwrites the previous archive — only the most recent snapshot is retained.

  • Log retention: each copy agent keeps 7 days of rolled log files on its own disk; older files are removed at log rotation. This is fixed on the agent and is not a setting. The console never keeps older uploads — only the latest zip per agent, replaced on every upload.

Settings​

Agent Log Collection Interval (min): how often each agent packages and sends its current logs to the console. Range 15–1440 min; default 60 min. Lower values mean more up-to-date snapshots on the console but higher network and CPU overhead on the agent. Changes are delivered to the agent via the next heartbeat settings payload — no restart required.

Downloading logs​

Use the Download Logs button next to any registered agent on the Live Agents tab to download its latest zip. The archive contains all log files from the agent's current retention window.