Merge pull request #36166 from github/repo-sync

Repo sync

content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity-in-your-enterprise/log-forwarding.md

@@ -21,10 +21,14 @@ topics:
 
 ## About log forwarding
 
+Forwarding logs to an external receiver allows your organization to centralize log management and retention, providing the data needed for monitoring system activity, detecting anomalies, and integrating with existing security and analytics tools.
+
 Any log collection system that supports syslog-style log streams is supported (e.g., [Logstash](https://www.elastic.co/products/logstash) and [Splunk](https://docs.splunk.com/Documentation/Splunk/latest/Data/Monitornetworkports)).
 
 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.
 
+For more information on log content, see [AUTOTITLE](/admin/monitoring-and-managing-your-instance/monitoring-your-instance/about-system-logs).
+
 ## Enabling log forwarding
 
 1. On the {% data variables.enterprise.management_console %} settings page, in the left sidebar, click **Monitoring**.

src/audit-logs/data/fpt/organization.json

@@ -94,6 +94,11 @@
     "description": "Code scanning alerts were fixed.",
     "docs_reference_links": "/code-security/code-scanning/introduction-to-code-scanning/about-code-scanning"
   },
+  {
+    "action": "code_scanning.alert_closed_became_outdated",
+    "description": "Code scanning alerts were closed as outdated (all configurations they were detected in were deleted).",
+    "docs_reference_links": "/code-security/code-scanning/introduction-to-code-scanning/about-code-scanning"
+  },
   {
     "action": "code_scanning.alert_closed_by_user",
     "description": "Code scanning alerts were manually dismissed.",

src/audit-logs/data/ghec/enterprise.json

@@ -689,6 +689,11 @@
     "description": "Code scanning alerts were fixed.",
     "docs_reference_links": "/code-security/code-scanning/introduction-to-code-scanning/about-code-scanning"
   },
+  {
+    "action": "code_scanning.alert_closed_became_outdated",
+    "description": "Code scanning alerts were closed as outdated (all configurations they were detected in were deleted).",
+    "docs_reference_links": "/code-security/code-scanning/introduction-to-code-scanning/about-code-scanning"
+  },
   {
     "action": "code_scanning.alert_closed_by_user",
     "description": "Code scanning alerts were manually dismissed.",

src/audit-logs/data/ghec/organization.json

@@ -94,6 +94,11 @@
     "description": "Code scanning alerts were fixed.",
     "docs_reference_links": "/code-security/code-scanning/introduction-to-code-scanning/about-code-scanning"
   },
+  {
+    "action": "code_scanning.alert_closed_became_outdated",
+    "description": "Code scanning alerts were closed as outdated (all configurations they were detected in were deleted).",
+    "docs_reference_links": "/code-security/code-scanning/introduction-to-code-scanning/about-code-scanning"
+  },
   {
     "action": "code_scanning.alert_closed_by_user",
     "description": "Code scanning alerts were manually dismissed.",

src/audit-logs/lib/config.json

@@ -3,5 +3,5 @@
     "apiOnlyEvents": "This event is not available in the web interface, only via the REST API, audit log streaming, or JSON/CSV exports.",
     "apiRequestEvent": "This event is only available via audit log streaming."
   },
-  "sha": "f1afd484608dbf8aee7b8982295d829f9f5f2d1b"
+  "sha": "cc5c30b400bb9bfc6db55dfef4522ac840be69b0"
 }

src/links/lib/excluded-links.yml

@@ -83,3 +83,5 @@
 - startsWith: https://www.ilo.org
 - is: https://www.codeproject.com/Articles/1214409/Learn-YAML-in-five-minutes
 - is: https://learning.getpostman.com/docs/postman/sending_api_requests/graphql/
+- is: https://www.nongnu.org/oath-toolkit/man-oathtool.html
+- is: https://www.gnu.org/software/emacs/