Daemon Configuration

Configuration Priority

Scanopy daemons use the following priority order (highest to lowest):

1. Command-line arguments (highest priority)
2. Environment variables
3. Configuration file
4. Default values (lowest priority)

Later sources override earlier ones. For example, an environment variable overrides the config file but is overridden by a command-line argument.

Configuration Methods

Command-line arguments (also accepted by scanopy-daemon install, which persists them to the config file — see Running as a Service):

scanopy-daemon --server-url http://192.168.1.100:60072 --api-key YOUR_KEY

Environment variables:

export SCANOPY_SERVER_URL=http://192.168.1.100:60072
export SCANOPY_DAEMON_API_KEY=YOUR_KEY
scanopy-daemon

Docker environment:

environment:
  - SCANOPY_SERVER_URL=http://192.168.1.100:60072
  - SCANOPY_DAEMON_API_KEY=YOUR_KEY

Configuration file:

The daemon automatically creates a config file at:

• Linux: ~/.config/scanopy/daemon/config.json
• macOS: ~/Library/Application Support/com.scanopy.daemon/config.json
• Windows: %APPDATA%\scanopy\daemon\config.json

The config file stores runtime state (daemon ID, host ID) alongside your settings. Command-line and environment variables take priority over the file.

Parameter Reference

Seeding Credentials at Registration

--credential-id / SCANOPY_CREDENTIAL_IDS

Seeds one or more credentials for the daemon to use on its first scan — so it can gather SNMP, Docker, or Podman data before you assign credentials in the UI. Provide credentials as a repeatable --credential-id flag or as a comma-separated SCANOPY_CREDENTIAL_IDS environment variable.

Each entry is a credential ID, optionally targeted at specific IP addresses:

To target the daemon's own host — for example a local Docker or Podman socket credential — use its loopback address: <uuid>@127.0.0.1.

# CLI (repeatable)
scanopy-daemon --credential-id [email protected] --credential-id [email protected]

# Environment (comma-separated)
export SCANOPY_CREDENTIAL_IDS="[email protected],[email protected]"

After the first scan, seeded credentials are auto-assigned to the matching hosts and used on every subsequent scan.

Deprecated in v0.15.0

• --docker-proxy / SCANOPY_DOCKER_PROXY
• --docker-proxy-ssl-cert / SCANOPY_DOCKER_PROXY_SSL_CERT
• --docker-proxy-ssl-key / SCANOPY_DOCKER_PROXY_SSL_KEY
• --docker-proxy-ssl-chain / SCANOPY_DOCKER_PROXY_SSL_CHAIN

Scan speed settings (--scan-rate-pps, --arp-rate-pps, etc.) configured at the daemon level are no longer used. Scan speed is now configured per-discovery in the Speed tab. See the migration guide.

Concurrent Scans

Controls how many hosts the daemon scans simultaneously during network discovery.

Default behavior: Auto-detected based on system resources

• Calculates based on available memory
• Typical range: 10-20 for most systems
• Adjusts to prevent memory exhaustion

When to set manually:

• System crashes during scans
• Memory errors in logs
• Very large networks (100+ hosts)
• Resource-constrained devices (Raspberry Pi)

Recommended values:

• Raspberry Pi 4 (4GB): 5-10
• Standard desktop: 15-20
• Server: 20-30+
• Low memory: Start with 5, increase gradually

Setting:

# CLI
scanopy-daemon --concurrent-scans 10

# Environment
export SCANOPY_CONCURRENT_SCANS=10

# Docker
environment:
  - SCANOPY_CONCURRENT_SCANS=10

Symptoms of too high:

• Daemon crashes during scans
• "CONCURRENT_SCANS too high for this system" error
• Out of memory errors
• System becomes unresponsive

Impact:

• Lower value = slower scans, more stable
• Higher value = faster scans, more memory usage

Logging

Output Destination

The daemon logs to stdout and stderr on all platforms. Where those logs end up depends on how you run the daemon.

Log Levels

Set the log level with --log-level or SCANOPY_LOG_LEVEL:

# CLI
scanopy-daemon --log-level debug

# Environment
export SCANOPY_LOG_LEVEL=debug

Viewing Logs by Platform

Foreground (all platforms): Logs appear directly in the terminal where you started the daemon.

Docker:

docker logs scanopy-daemon
docker logs -f scanopy-daemon  # follow/stream logs

The daemon installs as a native service via scanopy-daemon install — see Running as a Service.

Linux (systemd): output goes to the journal.

journalctl -u scanopy-daemon -f

macOS (launchd): the service writes to /var/log/scanopy/scanopy-daemon.out.log; the daemon's own log file is at ~/Library/Logs/scanopy/scanopy-daemon.log.

tail -f /var/log/scanopy/scanopy-daemon.out.log

Windows (service): the daemon writes its log file under %ProgramData%\scanopy\.

Get-Content "$env:ProgramData\scanopy\scanopy-daemon.log" -Wait

Capturing Logs to a File

When running in the foreground, you can capture logs to a file for sharing with support:

Linux / macOS:

./scanopy-daemon 2>&1 | tee ~/scanopy-daemon.log

Windows (PowerShell):

.\scanopy-daemon.exe 2>&1 | Tee-Object -FilePath "$env:USERPROFILE\scanopy-daemon.log"