The LogServer collects logs from other members of the Collective. This section describes how to configure a LogServer on your AppGate system.
Before adding a LogServer
Ensure the appliance-to-appliance communications have been set up appropriately:
Single packet authorization (SPA) implementation used by AppGate ZTNA for appliance-to-appliance communications can sometimes fall foul of firewalls set to allow all TLS. It is therefore strongly recommended to specifically allow TCP 443 between appliances.
The LogServer allows incoming traffic from peers. The other members of the Collective will establish connections to send audit logs/metrics (for more information, refer to Audit logs). A static IP address or resolvable hostname therefore needs to be configured in System Settings.
Configuring a LogServer
To configure a LogServer:
In the Add/Edit Appliance page, select the LogServer checkbox in the Functions tab.
Complete the following configuration fields:
Site Settings
Appliance Site. Select the Site from the dropdown list.
System TLS Connection (using SPA)
These settings are used for peer‑to‑peer traffic:
TLS Port. The inbound TLS connection port to the appliance.
Allowed Sources. Select +Add to add one or more allowed sources by adding the Address, Netmask Length, and the Network Interface. The requesting IP address must match at least one allowed source.
SPA Mode. Allows the SPA mode to be changed for a specific appliance. Select one of the following:
No override
Check TCP SPA key before allowing connections
Check UDP (and TCP) SPA key before allowing connections
Enable proxy protocol. When enabled, the appliance accepts only packets that include a proxy protocol header. AppGate ZTNA supports proxy protocol versions 1 and 2.
NOTE
When traffic originates from a known source, add that source to Allowed Sources. Failure to do so introduces a security risk.
Internal Log Settings
Audit Log Retention Period (days). Specify how long audit logs are retained in the LogServer database. The default value is 30.
NOTE
Do not set this value to more than 183 days (6 months). Higher values can cause the LogServer to run out of shards. Ensure that the disk size is sufficient for the expected log generation rate and the selected retention period.
NOTE
The LogServer must have administrative access to the Controllers on port 8443.
Admin/API TLS Connection
An Admin/API TLS connection is provided for system management on TCP port 8443. Inbound connections will be established by admins that want access to the admin UI and LogServer. Refer to System security - best practices before configuring Admin/API-to-appliance communications.
Unique Admin Hostname. Enter a fully-qualified domain name or an IPv4 or IPv6 address.
TLS Port. The default port is 8443.
Allowed Sources. Select +Add to add allowed sources by adding the Address, Netmask Length, and the Network Interface. The requesting IP address must match at least one allowed source.
TLS Ciphers. Select +Add to select the allowed TLS ciphers. The default ciphers are recommended unless browser requirements differ.
HTTPS Certificate. Adding a certificate removes the untrusted browser warning associated with the default self-signed certificate. For more information, see Removing the browser security warning. Select from the following options:
None.
Use CSR format. Select to create and download a CSR file to submit to a CSA. Once the file has been validated, you can upload it here.
Use PKCS #12 format. Select to upload a PKCS #12 file containing a CA-signed certificate and provide a password.
After completing the LogServer configuration, continue to the Miscellaneous tab.