Daemon logs are generated on each appliance. You can download them on demand or export them continuously. These logs are most useful when troubleshooting an appliance or investigating a user’s connectivity issues. For information on using journalctl to view daemon log records, see Appliance commands reference.
Daemon log storage
Each appliance writes daemon logs to a local journal using journald. journald manages storage allocation based on the disk size specified for the appliance. The total allocation combines a fixed journald allocation of 3.2 GB with a variable amount equal to 10 percent of the disk size. For example, a 32 GB disk receives a total allocation of 6.08 GB. When the allocation is full, journald removes the oldest records.
Exporting daemon logs using Rsyslog
Each appliance can export all logs—audit and daemon—using Rsyslog. Each configured destination has a 1 GB buffer. This buffer is not a storage solution; if no Rsyslog destination is available, the logs are lost. Rsyslog is the only method for exporting daemon logs.
To export appliance logs using Rsyslog, configure Rsyslog Destinations for each appliance. Secure log transfer is also available using Rsyslog, but requires manual configuration on both the appliance and the destination.
Viewing daemon logs
You can download daemon logs from the Appliances page for local examination. Logs download as a ZIP archive that you must extract before viewing.
The archive contains a system-info.txt file, which includes useful information such as healthcheck summaries. The logs_by_daemon folder is the primary area of interest. The table below summarizes the function of each daemon you will find there.
If you cannot retrieve debug logs through the admin UI, use the following local command instead: sudo cz-config collect-logs.
Daemon log levels
Every logged event is assigned a severity level that indicates the importance of that event. The daemon log level setting controls which event types the appliance stores in its daemon log. You configure the daemon log level on each appliance. The default setting is INFO.
Daemon log level setting | Description | Events stored - severity levels | ||||
|---|---|---|---|---|---|---|
|
|
|
|
| ||
| Debug messages for running the system in debug mode or troubleshooting appliances. Remember to reduce the log level setting once troubleshooting has been successful to reduce the disk-writing load on the appliance. | yes | yes | yes | yes | yes |
| Normal activity events, such as user sign-ins, starting or stopping IP access. Default setting for debug log levels. | yes | yes | yes | yes | |
| Non-systematic errors, such as erroneous packets received or maximum number of connections reached. May be sufficient event logging for mature systems that have been running successfully. | yes | yes | yes | ||
| Systematic errors such as a a syntax error while parsing an expression. May be sufficient event logging for mature systems that have been running successfully. | yes | yes | |||
| Critical errors such as AppGate ZTNA could not read a configuration file. Should be acted upon immediately. May be sufficient event logging for mature systems that have been running successfully. | yes | ||||
Changing a daemon log level
You may need to change the daemon log level to:
Run the appliance in
DEBUGmode for troubleshootingReduce disk-write load by running the appliance in
WARNING,ERROR, orCRITICALmode
To change the daemon log level, log in to the appliance using SSH and enter: sudo cz-setup

Select Change log levels to view the list of log daemons and update the settings.
