About log forwarding
Any log collection system that supports syslog-style log streams is supported (e.g., Logstash and Splunk).
When you enable log forwarding, you must upload a CA certificate to encrypt communications between syslog endpoints. Your appliance and the remote syslog server will perform two-way SSL, each providing a certificate to the other and validating the certificate which is received.
Enabling log forwarding
- On the Management Console settings page, in the left sidebar, click Monitoring.
- Select Enable log forwarding.
- In the Server address field, type the address of the server to which you want to forward logs. You can specify multiple addresses in a comma-separated list.
- In the Protocol drop-down menu, select the protocol to use to communicate with the log server. The protocol will apply to all specified log destinations.
- Optionally, select Enable TLS. We recommend enabling TLS according to your local security policies, especially if there are untrusted networks between the appliance and any remote log servers.
- To encrypt communication between syslog endpoints, click Choose File and choose a CA certificate for the remote syslog server. You should upload a CA bundle containing a concatenation of the certificates of the CAs involved in signing the certificate of the remote log server. The entire certificate chain will be validated, and must terminate in a root certificate. For more information, see TLS options in the syslog-ng documentation.
If you run into issues with log forwarding, contact GitHub Enterprise Support and attach the output file from
http(s)://[hostname]/setup/diagnostics to your email.