File locations

Linux

Path	Contents	Owner / mode
/usr/bin/logcore-agent	Agent binary	root, 0755
/etc/logcore-agent/logcore.yaml	Main configuration, including the API key	root:logcore-agent, 0640
/etc/logcore-agent/services/	Service files (*.yaml), plus *.yaml.example	root
/var/lib/logcore-agent/registry.json	Read position of every followed file	logcore-agent
/var/lib/logcore-agent/status.token	Token for logcore-agent status	logcore-agent, 0600
/etc/systemd/system/logcore-agent.service	systemd unit	root
journald (journalctl -u logcore-agent)	Agent's own log

The service runs as the logcore-agent system user, which is a member of adm and systemd-journal. With LOGCORE_RUN_AS_ROOT=true it runs as root instead.

Windows

Path	Contents
C:\Program Files\Logcore\logcore-agent.exe	Agent binary (folder added to PATH)
C:\ProgramData\Logcore\logcore.yaml	Main configuration
C:\ProgramData\Logcore\services\	Service files
C:\ProgramData\Logcore\data\	Read positions and status token
C:\ProgramData\Logcore\logs\agent.log	Agent's own log

The service is named Logcore Agent. It runs as LocalSystem and starts automatically at boot.

What's safe to delete

Item	Effect
registry.json	The agent forgets its read positions. Files present at the next start are treated as new and read from the end, per start_position.
status.token	Recreated at the next start.
A service file	That service stops being collected after a restart.