Cloud agent config

Cloud collectors import ~/.agent-retry/config.yaml at startup. The dashboard enroll script writes this file before the native package is installed.

Lite does not use this file. Enterprise on-prem uses the same nested agent.manager.* shape with your manager URL — see Enterprise agent config.

Staging example

agent:
  manager:
    url: https://cloud-staging.retrysight.com
    api-key: rk_live_YOUR_ACCOUNT_KEY
  identity:
    id-file: ${user.home}/.agent-retry/agent-id
    lock-file: ${user.home}/.agent-retry/agent.lock
  platform:
    installation-tier: TIER_4_CLOUD
    auto-discovery: true
  discovery:
    recency-days: 30
    refresh-interval-seconds: 300
  session:
    idle-complete-minutes: 30
  upload:
    batch-interval-seconds: 10
    max-batch-size: 100
    buffer-path: ${user.home}/.agent-retry/buffer.db
  privacy:
    store-full-prompts: false

Field	Purpose
agent.manager.url	Cloud origin — https://cloud-staging.retrysight.com (dashboard and API share this host on staging)
agent.manager.api-key	Per-account rk_live_* from Account
agent.platform.auto-discovery	Probe known OS/WSL log layouts; refresh default 5 minutes
agent.upload.buffer-path	Local SQLite buffer while offline
agent.privacy.store-full-prompts	Keep false unless compliance review requires prompt bodies

Do not set the manager URL to app.retrysight.com — that host serves Enterprise CDN artifacts, not Cloud ingest.

Custom log directories still need watch-path (or discovery-mode: FIXED). Print the discovery map:

java -jar agent-app.jar --agent.cli.command=discover

Native installs usually do not need that command.

Environment variables

Variable	Maps to
AGENT_MANAGER_URL	agent.manager.url
AGENT_MANAGER_API_KEY	agent.manager.api-key

Proxy: agent.manager.proxy-host / proxy-port, or HTTP_PROXY / HTTPS_PROXY.

After edits

Restart the OS service (com.retrysight.agent / retrysight-agent.service / RetrySightAgent). Confirm Collectors.

Field-level reference also lives in config YAML.