* New Crowdin translations by Github Action * Reset broken translated files to English * Ran script/i18n/homogenize-frontmatter.js * Ran script/fix-translation-errors.js * Reverted translated files with parsing and rendering errors * fix malformed liquid * add next directory to exclude list * currentversion -> currentVersion * fix liquid errors * fix liquid errors * Reset broken translated files to English * Ran script/i18n/homogenize-frontmatter.js * Revert /ja/github/authenticating-to-github/about-authentication-with-saml-single-sign-on * Reset known broken translation files LAST * Run script/i18n/homogenize-frontmatter.js Co-authored-by: Crowdin Bot <support+bot@crowdin.com> Co-authored-by: Rachael Sewell <rachmari@github.com> Co-authored-by: Kevin Heis <heiskr@users.noreply.github.com>
3.4 KiB
3.4 KiB
title, intro, redirect_from, versions, type, topics
| title | intro | redirect_from | versions | type | topics | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Log forwarding | {% data variables.product.product_name %} uses `syslog-ng` to forward {% if enterpriseServerVersions contains currentVersion %}system{% elsif currentVersion == "github-ae@latest" %}Git{% endif %} and application logs to the server you specify. |
|
|
how_to |
|
Any log collection system that supports syslog-style log streams is supported (e.g., Logstash and Splunk).
Enabling log forwarding
{% if enterpriseServerVersions contains currentVersion %}
- On the {% data variables.enterprise.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.
- Select Enable TLS.
- Click Choose File and choose a CA certificate to encrypt communication between syslog endpoints. 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. {% elsif currentVersion == "github-ae@latest" %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %}
- Under {% octicon "gear" aria-label="The Settings gear" %} Settings, click Log forwarding.

- Under "Log forwarding", select Enable log forwarding.

- Under "Server address", enter the address of the server you want to forward logs to.

- Use the "Protocol" drop-down menu, and select a protocol.

- Optionally, to enable TLS encrypted communication between syslog endpoints, select Enable TLS.

- Under "Public certificate", paste your x509 certificate.

- Click Save.
{% endif %}
{% if enterpriseServerVersions contains currentVersion %}
Устранение проблем
If you run into issues with log forwarding, contact
{% data variables.contact.contact_ent_support %} and attach the output file from http(s)://[hostname]/setup/diagnostics to your email.
{% endif %}