Manage log verbosity

Access Gateway enables you to configure the level of detail you want to store in your logs.

Note: Log verbosity doesn't impact log forwarding. All events are forwarded regardless of the log verbosity setting.

This table lists the default logging level for components in Access Gateway:

Component	Default logging level
NGINX	`Error`
DNS Resolver	`Operational information`
SimpleSAMLphp	`Notice`
Kerberos	`Info`
Access Gateway UI service*	`Info`
Access Gateway Management console service	`Info`
Underlying shell scripts	`Info`

* The Access Gateway Admin UI console service generates log events based on the Access Gateway Management console debug setting. Access Gateway doesn't filter events by log verbosity.

Note: Global log verbosity is set to DEBUG by default. This configures the appliance's System Log to capture logs at this level or lower, but it doesn't enable debug logging for individual services. Service-level debugging must be configured separately in the Access Gateway Management console. See Monitor. To manage log volume in production environments, particularly when using log forwarding, use WARNING or ERROR.

Configure the level of log verbosity

Go to your Access Gateway instance.
Select the Backups and Logs tab.
Select the Log Storage pane.
In the Storage management section, click Edit.
Select the radio button next to the required log event level:
- Debug: Use this setting for initial setup or for troubleshooting. This option records all events.
- Info: Use this setting for daily monitoring requirements.
- Warning: Use this setting to store only warnings. This option consumes less disk space than the Info level.
- Error: Use this setting only when you have set up a log forwarder and only for storing error events. This option consumes less disk space than the Warning, Info, or Debug levels.
  Note:
  When you change the log event level, existing events in your log below that level are discarded.
Click Save.

CAUTION:

Take extreme care when changing logging levels. If you set the logging level to ALL, the log entries might consume your disk space. If you set the logging level higher than Info, this could result in lost events.