Modified files to match the new external links

mrgarris0n · mrgarris0n · commit db3640e3a5ca · 2024-05-17T17:19:11.000+02:00
Signed-off-by: mrgarris0n &lt;gergely.karacsonyi@gmail.com&gt;
diff --git a/_includes/doc/admin-guide/manpages-footnote.md b/_includes/doc/admin-guide/manpages-footnote.md
@@ -4,6 +4,8 @@ The syslog-ng.conf manual page
 The syslog-ng manual page
 
 >**NOTE:**
->If you experience any problems or need help with syslog-ng OSE, visit the syslog-ng mailing list. \
->For news and notifications about syslog-ng OSE, visit the syslog-ng blogs.
+>If you experience any problems or need help with syslog-ng OSE, visit
+>the [syslog-ng mailing list](https://lists.balabit.hu/mailman/listinfo/syslog-ng).
+>  
+>For news and notifications about syslog-ng OSE, visit the [syslog-ng blogs](https://syslog-ng.com/blog/).
 {: .notice--info}
diff --git a/_includes/doc/admin-guide/manpages-intro.md b/_includes/doc/admin-guide/manpages-intro.md
@@ -5,5 +5,4 @@ package. The latest version of the syslog-ng OSE application is
 available at the [syslog-ng OSE page](https://syslog-ng.com/).
 {: .notice--info}
 
-This manual page is only an abstract, for the complete documentation of
-syslog-ng OSE, see the [syslog-ng OSE Documentation page](https://www.syslog-ng.com/).
+This manual page is only an abstract.
diff --git a/doc/_admin-guide/020_The_concepts_of_syslog-ng/002_Modes_of_operation.md b/doc/_admin-guide/020_The_concepts_of_syslog-ng/002_Modes_of_operation.md
@@ -47,9 +47,8 @@ To ensure at least a best effort level of reliability, One Identity
 recommends that you deploy a relay on the network, close to the source
 devices. With the most reliable hops between the source and the relay,
 you can minimize the risk of losing UDP packets. Once the packet arrives
-at the relay, [syslog-ng OSE](https://syslog-ng.com/blog/upgrading-from-syslog-ng-open-source-to-premium-edition/)
-ensures that the messages are delivered to the central server in a
-reliable manner, based on TCP/TLS.
+at the relay, syslog-ng OSE ensures that the messages are delivered to
+the central server in a reliable manner, based on TCP/TLS.
 
 ### Too many source devices
 
diff --git a/doc/_admin-guide/020_The_concepts_of_syslog-ng/006_High_availability.md b/doc/_admin-guide/020_The_concepts_of_syslog-ng/006_High_availability.md
@@ -8,4 +8,4 @@ description: >-
 ---
 
 A tool that can be used to create UNIX clusters is Heartbeat (for details,
-see [this page](http://www.linux-ha.org/wiki/Main_Page/)).
+see the archived page of Linux-HA.
diff --git a/doc/_admin-guide/020_The_concepts_of_syslog-ng/007_The_structure_of_a_log_message/000_BSD_syslog_messages.md b/doc/_admin-guide/020_The_concepts_of_syslog-ng/007_The_structure_of_a_log_message/000_BSD_syslog_messages.md
@@ -3,7 +3,7 @@ title: BSD-syslog or legacy-syslog messages
 id: adm-struct-bsd
 description: >-
     This section describes the format of a syslog message, according to the
-    [legacy-syslog or BSD-syslog protocol](https://tools.ietf.org/search/rfc3164).
+    [legacy syslog (BSD-syslog) protocol](https://tools.ietf.org/search/rfc3164).
 ---
 
 A syslog message consists of the following parts:
@@ -35,7 +35,7 @@ size when using UDP destinations.
 ## The PRI message part
 
 This section describes the PRI message part of a syslog message, according to the
-[legacy-syslog or BSD-syslog protocol](https://tools.ietf.org/search/rfc3164).
+[legacy syslog (BSD-syslog) protocol](https://tools.ietf.org/search/rfc3164).
 
 The PRI part of the syslog message (known as Priority value) represents
 the Facility and Severity of the message. Facility represents the part
@@ -72,7 +72,7 @@ example:
 
 ## The HEADER message part
 
-This section describes the HEADER message part of a syslog message, according to the [legacy-syslog or BSD-syslog protocol](https://tools.ietf.org/search/rfc3164).
+This section describes the HEADER message part of a syslog message, according to the [legacy syslog (BSD-syslog) protocol](https://tools.ietf.org/search/rfc3164).
 
 The HEADER message part contains a timestamp and the hostname (without
 the domain name) or the IP address of the device. The timestamp field is
@@ -97,7 +97,7 @@ format. For details, see the ts-format() option in Global options.
 ## The MSG message part
 
 This section describes the MSG message part of a syslog message, according to
-the [legacy-syslog or BSD-syslog protocol](https://tools.ietf.org/search/rfc3164).
+the [legacy syslog (BSD-syslog) protocol](https://tools.ietf.org/search/rfc3164).
 
 The MSG part contains the name of the program or process that generated
 the message, and the text of the message itself. The MSG part is usually
diff --git a/doc/_admin-guide/020_The_concepts_of_syslog-ng/011_Commercial_version.md b/doc/_admin-guide/020_The_concepts_of_syslog-ng/011_Commercial_version.md
@@ -97,4 +97,4 @@ For further details about syslog-ng Store Box, see
 ## Upgrading from syslog-ng OSE to syslog-ng PE
 
 If you wish to upgrade from syslog-ng OSE to syslog-ng PE, read the blog
-post [Upgrading from syslog-ng OSE to syslog-ng PE](https://syslog-ng.com/blog/upgrading-from-syslog-ng-open-source-to-premium-edition/) for instructions and tips.
+post Upgrading from syslog-ng OSE to syslog-ng PE for instructions and tips.
diff --git a/doc/_admin-guide/050_The_configuration_file/001_Configuration_syntax.md b/doc/_admin-guide/050_The_configuration_file/001_Configuration_syntax.md
@@ -41,7 +41,7 @@ log {
 };
 ```
 
-As a syslog-ng user described on a [mailing list](https://lists.gt.net/gentoo/user/209108):
+As a syslog-ng user described on a Gentoo mailing list:
 
 > Alan McKinnon
 >
diff --git a/doc/_admin-guide/060_Sources/060_mqtt/README.md b/doc/_admin-guide/060_Sources/060_mqtt/README.md
@@ -7,10 +7,8 @@ description: >-
     messages from MQTT brokers.
 ---
 
-The mqtt() source builds on the [MQTT
-protocol](https://www.hivemq.com/mqtt/mqtt-protocol/), and uses its
-[client](https://www.hivemq.com/blog/seven-best-mqtt-client-tools/) and
-[broker](https://www.hivemq.com/hivemq/mqtt-broker/) entities.
+The mqtt() source builds on the MQTT protocol, and uses its
+MQTT client and MQTT broker entities.
 
 **NOTE:** The rest of this chapter and its sections build on your
 familiarity with the MQTT protocol, the concept of client and broker
diff --git a/doc/_admin-guide/060_Sources/090_mbox/README.md b/doc/_admin-guide/060_Sources/090_mbox/README.md
@@ -18,9 +18,8 @@ syslog-ng OSE configuration:
 The mbox() driver is actually a reusable configuration snippet
 configured to read log messages using the file() driver. For details on
 using or writing such configuration snippets, see
-Reusing configuration blocks.  
-You can find the source of the configuration snippet on
-[GitHub](https://github.com/syslog-ng/syslog-ng/blob/master/scl/mbox/mbox.conf).
+[[Reusing configuration blocks]].  
+You can find the source of the mbox configuration snippet on GitHub.
 
 ### Example: Using the mbox() driver
 
diff --git a/doc/_admin-guide/060_Sources/100_osquery/README.md b/doc/_admin-guide/060_Sources/100_osquery/README.md
@@ -3,7 +3,7 @@ title: 'osquery: Collect and parse osquery result logs'
 short_title: osquery
 id: adm-src-osquery
 description: >-
-    The [osquery](https://osquery.io) application allows you to ask
+    The [[osquery|other-osquery]] application allows you to ask
     questions about your machine using an SQL-like language. For example,
     you can query running processes, logged in users, installed packages and
     syslog messages as well. You can make queries on demand, and also
diff --git a/doc/_admin-guide/060_Sources/120_pacct/README.md b/doc/_admin-guide/060_Sources/120_pacct/README.md
@@ -54,6 +54,5 @@ log { source(s_pacct); destination(...); };
 The pacct() driver is actually a reusable configuration snippet
 configured to handle Linux accounting logs. For details on using or
 writing such configuration snippets, see
-Reusing configuration blocks.  
-You can find the source of the pacct configuration snippet on
-[GitHub](https://github.com/syslog-ng/syslog-ng/blob/master/scl/pacct/plugin.conf).
+[[Reusing configuration blocks]].  
+You can find the source of the pacct configuration snippet on GitHub.
diff --git a/doc/_admin-guide/060_Sources/160_sun-streams/README.md b/doc/_admin-guide/060_Sources/160_sun-streams/README.md
@@ -19,12 +19,12 @@ STREAMS device to open, and the door() option. For the list of available
 optional parameters, see
 sun-streams() source options. 
 
-**NOTE:** Starting with version 3.7, the syslog-ng OSEsystem() driver
+**NOTE:** Starting with version 3.7, the syslog-ng OSE system() driver
 automatically extracts the msgid from the message (if available), and
 stores it in the .solaris.msgid macro. To extract the msgid from the
-message without using the system()driver, use the
+message without using the system() driver, use the
 **extract-solaris-msgid()** parser. You can find the exact source of
-this parser in the [syslog-ng OSE GitHub repository](https://github.com/syslog-ng/syslog-ng/blob/master/scl/solaris/plugin.conf).
+the Solaris parser on GitHub.
 {: .notice--info}
 
 **Declaration**
diff --git a/doc/_admin-guide/060_Sources/180_System/README.md b/doc/_admin-guide/060_Sources/180_System/README.md
@@ -53,12 +53,12 @@ such messages without losing any information to CIM-aware applications
 |              | If the kernel of the host is version 3.5 or newer, and /dev/kmsg is seekable, syslog-ng OSE will use that instead of /proc/kmsg, using the multi-line-mode(indented), keep-timestamp(no), and the format(linux-kmsg)options.                      |
 |              | If syslog-ng OSE is running in a jail or a Linux Container (LXC), it will not read from the /dev/kmsg or /proc/kmsg files.                                 |
 | macOS        |     file("/var/log/system.log" follow-freq(1));      |
-|              | **NOTE:** Starting with version 3.7, the syslog-ng OSE system() driver automatically extracts the msgid  from the message (if available), and stores it in the .solaris.msgid macro. To extract the msgid from the message without using the system()driver, use the **extract-solaris-msgid()** parser. You can find the exact source of this parser in the [syslog-ng OSE GitHub repository](https://github.com/syslog-ng/syslog-ng/blob/master/scl/solaris/plugin.conf).|
+|              | **NOTE:** Starting with version 3.7, the syslog-ng OSE system() driver automatically extracts the msgid  from the message (if available), and stores it in the .solaris.msgid macro. To extract the msgid from the message without using the system()driver, use the **extract-solaris-msgid()** parser. You can find the exact source of the Solaris parser on GitHub.|
 | NetBSD       |     unix-dgram("/var/run/log");                      |
-|              | NOTE: Starting with version 3.7, the syslog-ng OSE system() driver automatically extracts the msgid  from the message (if available), and stores it in the .solaris.msgid macro. To extract the msgid from the message without using the system()driver, use the **extract-solaris-msgid()** parser. You can find the exact source of this parser in the [syslog-ng OSE GitHub repository](https://github.com/syslog-ng/syslog-ng/blob/master/scl/solaris/plugin.conf). |
+|              | NOTE: Starting with version 3.7, the syslog-ng OSE system() driver automatically extracts the msgid  from the message (if available), and stores it in the .solaris.msgid macro. To extract the msgid from the message without using the system()driver, use the **extract-solaris-msgid()** parser. You can find the exact source of the Solaris parser on GitHub. |
 | Solaris 8    |     sun-streams("/dev/log");                         |
-|              | NOTE: Starting with version 3.7, the syslog-ng OSE system() driver automatically extracts the msgid  from the message (if available), and stores it in the .solaris.msgid macro. To extract the msgid from the message without using the system()driver, use the **extract-solaris-msgid()** parser. You can find the exact source of this parser in the [syslog-ng OSE GitHub repository](https://github.com/syslog-ng/syslog-ng/blob/master/scl/solaris/plugin.conf). |
+|              | NOTE: Starting with version 3.7, the syslog-ng OSE system() driver automatically extracts the msgid  from the message (if available), and stores it in the .solaris.msgid macro. To extract the msgid from the message without using the system()driver, use the **extract-solaris-msgid()** parser. You can find the exact source of the Solaris parser on GitHub. |
 | Solaris 9    | sun-streams("/dev/log" door("/etc/.syslog_door")); |
-|              | NOTE: Starting with version 3.7, the syslog-ng OSE system() driver automatically extracts the msgid  from the message (if available), and stores it in the .solaris.msgid macro. To extract the msgid from the message without using the system()driver, use the **extract-solaris-msgid()** parser. You can find the exact source of this parser in the [syslog-ng OSE GitHub repository](https://github.com/syslog-ng/syslog-ng/blob/master/scl/solaris/plugin.conf). |
+|              | NOTE: Starting with version 3.7, the syslog-ng OSE system() driver automatically extracts the msgid  from the message (if available), and stores it in the .solaris.msgid macro. To extract the msgid from the message without using the system()driver, use the **extract-solaris-msgid()** parser. You can find the exact source of the Solaris parser on GitHub. |
 | Solaris 10   |  sun-streams("/dev/log" door("/var/run/syslog_door")); |
-|              | NOTE: Starting with version 3.7, the syslog-ng OSE system() driver automatically extracts the msgid  from the message (if available), and stores it in the .solaris.msgid macro. To extract the msgid from the message without using the system()driver, use the **extract-solaris-msgid()** parser. You can find the exact source of this parser in the [syslog-ng OSE GitHub repository](https://github.com/syslog-ng/syslog-ng/blob/master/scl/solaris/plugin.conf). |
+|              | NOTE: Starting with version 3.7, the syslog-ng OSE system() driver automatically extracts the msgid  from the message (if available), and stores it in the .solaris.msgid macro. To extract the msgid from the message without using the system()driver, use the **extract-solaris-msgid()** parser. You can find the exact source of the solaris parser on GitHub. |
diff --git a/doc/_admin-guide/070_Destinations/153_OpenObserve/001_OpenObserve-destination-options.md b/doc/_admin-guide/070_Destinations/153_OpenObserve/001_OpenObserve-destination-options.md
@@ -12,7 +12,7 @@ description: >-
 |  Type:|      string|
 |  Default:|   `"default"`|
 
-*Description:* The name of the [OpenObserve](https://openobserve.ai/docs/user-guide/organizations/) organization where syslog-ng OSE sends the data.
+*Description:* The name of the OpenObserve organization where syslog-ng OSE sends the data.
 
 {% include doc/admin-guide/options/password.md %}
 
@@ -30,7 +30,7 @@ description: >-
 |  Type:|      string|
 |  Default:|   `"default"`|
 
-*Description:* The [OpenObserve](https://openobserve.ai/docs/user-guide/streams/) stream where syslog-ng OSE sends the data, for example, `your-example-stream`.
+*Description:* The OpenObserve stream where syslog-ng OSE sends the data, for example, `your-example-stream`.
 
 ## user()
 
diff --git a/doc/_admin-guide/070_Destinations/153_OpenObserve/README.md b/doc/_admin-guide/070_Destinations/153_OpenObserve/README.md
@@ -3,7 +3,7 @@ title: 'OpenObserve: Send messages to OpenObserve'
 short_title: OpenObserve
 id: adm-dest-opobs
 description: >-
-    In syslog-ng-OSE version 4.5 and later versions it is possible to send  messages to [OpenObserve](https://openobserve.ai/docs/api/ingestion/logs/json/) using its [Log Ingestion - JSON API](https://openobserve.ai/docs/api/ingestion/logs/json/). This API receives multiple-record batches in JSON format.
+    In syslog-ng-OSE version 4.5 and later versions it is possible to send  messages to  OpenObserve using OpenObserve Log Ingestion - JSON API. This API receives multiple-record batches in JSON format.
 
 ---
 
diff --git a/doc/_admin-guide/120_Parser/008_Apache_access_log_parser/README.md b/doc/_admin-guide/120_Parser/008_Apache_access_log_parser/README.md
@@ -80,6 +80,5 @@ OSE configuration:
 The apache-accesslog-parser() is actually a reusable configuration
 snippet configured parse Apache access log messages. For details on
 using or writing such configuration snippets, see
-Reusing configuration blocks. You can find the source of
-this configuration snippet on
-[GitHub](https://github.com/syslog-ng/syslog-ng/blob/master/scl/apache/apache.conf).
+[[Reusing configuration blocks]]. You can find the source of
+the Apache configuration snippet on GitHub.
diff --git a/doc/_admin-guide/120_Parser/010_Cisco_parser.md b/doc/_admin-guide/120_Parser/010_Cisco_parser.md
@@ -55,9 +55,8 @@ Note that you have to disable message parsing in the source using the
 
 The cisco-parser() is actually a reusable configuration snippet
 configured to parse Cisco messages. For details on using or writing such
-configuration snippets, see Reusing configuration blocks.
-You can find the source of this configuration
-snippet on [GitHub](https://github.com/syslog-ng/syslog-ng/blob/master/scl/cisco/plugin.conf).
+configuration snippets, see [[Reusing configuration blocks]].
+You can find the source of the Cisco configuration snippet on GitHub.
 
 {% include doc/admin-guide/options/prefix.md %}
 
diff --git a/doc/_admin-guide/120_Parser/012_iptables_parser.md b/doc/_admin-guide/120_Parser/012_iptables_parser.md
@@ -19,9 +19,8 @@ description: >-
 
 The iptables-parser() is actually a reusable configuration snippet
 configured to parse iptables messages. For details on using or writing
-such configuration snippets, see Reusing configuration blocks.
-You can find the source of this configuration snippet on
-[GitHub](https://github.com/syslog-ng/syslog-ng/blob/master/scl/iptables/iptables.conf).
+such configuration snippets, see [[Reusing configuration blocks]].
+You can find the source of the iptables configuration snippet on GitHub.
 
 {% include doc/admin-guide/options/prefix.md %}
 
diff --git a/doc/_admin-guide/120_Parser/015_sudo_parser.md b/doc/_admin-guide/120_Parser/015_sudo_parser.md
@@ -21,9 +21,8 @@ log {
 
 The sudo-parser() is actually a reusable configuration snippet
 configured to parse sudo messages. For details on using or writing such
-configuration snippets, see Reusing configuration blocks.
-You can find the source of this configuration snippet on
-[GitHub](https://github.com/syslog-ng/syslog-ng/blob/master/scl/sudo/sudo.conf).
+configuration snippets, see [[Reusing configuration blocks]].
+You can find the source of the sudo configuration snippet on GitHub.
 
 {% include doc/admin-guide/options/prefix.md %}
 
diff --git a/doc/_admin-guide/120_Parser/023_db_parser/001_Using_pattern_databases/001_Downloading_sample_patterndb.md b/doc/_admin-guide/120_Parser/023_db_parser/001_Using_pattern_databases/001_Downloading_sample_patterndb.md
@@ -33,5 +33,4 @@ For legal details, the full text of the license is [available here](https://crea
 
 If you create patterns that are not available in the GitHub repository,
 consider sharing them with us and the syslog-ng community. To do this,
-open a GitHub issue, or send them to the syslog-ng mailing
-list.
+open a GitHub issue, or send them to the syslog-ng mailing list.
diff --git a/doc/_admin-guide/120_Parser/README.md b/doc/_admin-guide/120_Parser/README.md
@@ -57,8 +57,8 @@ following application logs:
 - Linux Audit (auditd) logs. For details, see
     Linux audit parser.
 - Netskope log messages. For details, see
-    Netskope parser.
-- [osquery](https://osquery.io) result logs. For details, see
+    [[Netskope parser]].
+- [[osquery|other-osquery]] result logs. For details, see
     [[osquery: Collect and parse osquery result logs]].
 
 - SNMP traps of the [Net-SNMP](http://www.net-snmp.org)\'s snmptrapd
diff --git a/doc/_admin-guide/170_Troubleshooting_syslog-ng/README.md b/doc/_admin-guide/170_Troubleshooting_syslog-ng/README.md
@@ -50,7 +50,7 @@ description: >-
     Things to consider when forwarding messages between syslog-ng OSE hosts.
 
 - In case you experience a problem that is not covered in this guide,
-    send it the syslog-ng mailing list.
+    send it to the syslog-ng mailing list.
 
     To report bugs found in syslog-ng OSE, visit the syslog-ng issue tracker on GitHub.
 
diff --git a/doc/_admin-guide/190_The_syslog-ng_manual_pages/002_pdbtool.md b/doc/_admin-guide/190_The_syslog-ng_manual_pages/002_pdbtool.md
@@ -14,8 +14,7 @@ pdbtool \[command\] \[options\]
 
 ## Description
 
-This manual page is only an abstract, for the complete documentation of
-syslog-ng OSE, see the [syslog-ng OSE Documentation page](https://www.syslog-ng.com/).
+This manual page is only an abstract.
 
 The syslog-ng OSE application can match the contents of the log messages
 to a database of predefined message patterns (also called patterndb). By
diff --git a/doc/_admin-guide/190_The_syslog-ng_manual_pages/007_syslog-ng_control_tool.md b/doc/_admin-guide/190_The_syslog-ng_manual_pages/007_syslog-ng_control_tool.md
@@ -199,7 +199,7 @@ stats \[options\]
 
 Use the stats command to display statistics about the processed
 messages. For details about the displayed statistics,
-see [The syslog-ng OSE Administrator Guide](https://www.syslog-ng.com).
+see [The syslog-ng OSE Administration Guide](https://www.syslog-ng.com).
 The stats command has the following options:
 
 - \--control=\<socket\> or -c
diff --git a/doc/_admin-guide/190_The_syslog-ng_manual_pages/009_syslog-ng_manual.md b/doc/_admin-guide/190_The_syslog-ng_manual_pages/009_syslog-ng_manual.md
@@ -13,8 +13,7 @@ syslog-ng \[options\]
 
 ## Description
 
-This manual page is only an abstract, for the complete documentation of
-syslog-ng OSE, see the [syslog-ng OSE Documentation page](https://www.syslog-ng.com/).
+This manual page is only an abstract.
 
 The syslog-ng OSE application is a flexible and highly scalable system
 logging application. Typically, syslog-ng OSE is used to manage log
diff --git a/doc/_admin-guide/190_The_syslog-ng_manual_pages/010_syslog-ng_conf.md b/doc/_admin-guide/190_The_syslog-ng_manual_pages/010_syslog-ng_conf.md
@@ -13,8 +13,7 @@ syslog-ng.conf
 
 ## Description
 
-This manual page is only an abstract, for the complete documentation of
-syslog-ng OSE, see the [syslog-ng OSE Documentation page](https://www.syslog-ng.com/).
+This manual page is only an abstract.
 
 The syslog-ng OSE application is a flexible and highly scalable system
 logging application. Typically, syslog-ng OSE is used to manage log
@@ -217,8 +216,7 @@ options { use-dns(no); };
 ```
 
 The sources, destinations, and filters available in syslog-ng OSE are
-listed below. For details, see the
-[syslog-ng OSE Documentation page](https://www.syslog-ng.com).
+listed below.  
 
 ## Table 1: Source drivers available in syslog-ng OSE
 

Original file line number	Diff line number	Diff line change
`@@ -41,7 +41,7 @@ log {`
`41`	`41`	`};`
`42`	`42`	```
`43`	`43`
`44`		`-As a syslog-ng user described on a [mailing list](https://lists.gt.net/gentoo/user/209108):`
	`44`	`+As a syslog-ng user described on a Gentoo mailing list:`
`45`	`45`
`46`	`46`	`> Alan McKinnon`
`47`	`47`	`>`