Logging

Review where Breeze Agent writes logs and how to adjust verbosity and rotation.

Locations

• Linux/macOS
  • Scheduled runs (systemd/cron): /opt/breeze-agent/var/log/breeze-agent.log
  • Manual runs: STDOUT (unless log_file is set)
• Windows
  • Scheduled runs and manual runs: C:\\Program Files\\Breeze\\agent.log

Log destinations can also be controlled via log_file in agent.conf.

Rotation

• Linux/macOS
  • Log rotation is typically handled via /etc/cron.d/breeze-agent-logrotate and the system logrotate configuration.
  • Adjust retention and size limits in your OS logrotate policy if needed.
• Windows
  • A scheduled task such as Breeze Agent Logrotate can truncate or rotate logs on a schedule, depending on your deployment.

For large estates, review rotation settings to avoid disks filling due to verbose logging.

Verbosity

Logging verbosity is controlled by log_level in agent.conf, where lower numeric values are more verbose (for example, "0" debug, "1" info, "2" warn).

• Use default/“info or warn” levels for day‑to‑day operation.
• Temporarily enable debug/verbose for troubleshooting and then revert to normal levels.

Troubleshooting Tips

• If logs are empty:
  • Confirm the scheduler is running (systemd timer/cron/Task Scheduler).
  • Run the launcher manually (./app.sh or breeze run) to capture immediate output.
• Proxy/TLS errors:
  • Often indicate trust or interception issues; confirm proxy configuration and Cloudaware trust.
  • See Environment & Proxy for proxy and Cloudaware bundle settings.