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:

A daemon you run yourself creates its config file under your user profile:

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

A daemon installed as a service uses a system directory instead. A background service runs under a different profile than whoever installed it, so install writes the config to a system location and points the service at it explicitly. The install command prints the config and log paths it settled on — read them off the output rather than guessing.

Use --config-dir / SCANOPY_CONFIG_DIR to override the directory holding 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 1a2b3c4d-...@192.168.1.10 --credential-id 5e6f7a8b-...@127.0.0.1

# Environment (comma-separated)
export SCANOPY_CREDENTIAL_IDS="1a2b3c4d-...@192.168.1.10,5e6f7a8b-...@127.0.0.1"

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

Deprecated Parameters

The Docker proxy parameters (--docker-proxy, --docker-proxy-ssl-cert, --docker-proxy-ssl-key, --docker-proxy-ssl-chain, and their SCANOPY_* equivalents) are superseded by Docker Proxy credentials. See the migration guide for steps.

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

Scan Concurrency

The daemon decides how many hosts to scan simultaneously on its own, based on available memory and its file descriptor limit. There is no setting to configure it.

If scans are slower than expected because concurrency has been clamped low, the usual cause is a restrictive file descriptor limit — see "Too Many Open Files".

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"