Merge pull request #1557 from SEKOIA-IO/fix_dead_link

Fix dead link to Syslog / Https pages

docs/xdr/features/collect/integrations/application/alsid.md

@@ -16,4 +16,4 @@ As of now, the main solution to collect Alsid logs leverages the Rsyslog recipe.
 
 ### Rsyslog
 
-Please refer to the documentation of Alsid to forward events to your rsyslog server. The reader is also invited to consult the [Rsyslog Transport](../../../ingestion_methods/rsyslog/) documentation to forward these logs to Sekoia.io.
+Please refer to the documentation of Alsid to forward events to your rsyslog server. The reader is also invited to consult the [Rsyslog Transport](../../../ingestion_methods/syslog/overview/) documentation to forward these logs to Sekoia.io.

docs/xdr/features/collect/integrations/application/apache.md

@@ -221,7 +221,7 @@ As of now, the main solution to collect Apache logs leverages the Rsyslog recipe
 
 ### Forward logs to Sekoia.io
 
-This setup guide will show you how to forward both your access and error logs to Sekoia.io by means of an rsyslog transport channel. The reader is also invited to consult the [Rsyslog Transport](../../../ingestion_methods/rsyslog/) documentation to forward these logs to Sekoia.io.
+This setup guide will show you how to forward both your access and error logs to Sekoia.io by means of an rsyslog transport channel. The reader is also invited to consult the [Rsyslog Transport](../../../ingestion_methods/syslog/overview/) documentation to forward these logs to Sekoia.io.
 
 At the beginning of your rsyslog configuration file for the Apache logs,  paste the following instruction to order the rsyslog server to load the module `imfile`:
 ```bash

docs/xdr/features/collect/integrations/application/bind.md

@@ -16,7 +16,7 @@ As of now, the main solution to collect BIND logs leverages the Rsyslog recipe.
 
 ### Rsyslog
 
-This Section shows how to configure BIND to forward its events to your rsyslog server. The reader is also invited to consult the [Rsyslog Transport](../../../ingestion_methods/rsyslog/) documentation to forward these logs to Sekoia.io.
+This Section shows how to configure BIND to forward its events to your rsyslog server. The reader is also invited to consult the [Rsyslog Transport](../../../ingestion_methods/syslog/overview/) documentation to forward these logs to Sekoia.io.
 
 First, you need to configure your BIND daemon to log queries and forward them to your rsyslog instance. If rsyslog and BIND are installed on the same box, you can simply add the following statement in your BIND’s main configuration file:
 

docs/xdr/features/collect/integrations/application/dhcpd.md

@@ -15,4 +15,4 @@ As of now, the main solution to collect ISC DHCP logs leverages the Rsyslog reci
 
 ### Rsyslog
 
-Please refer to the documentation of ISC DHPD to forward events to your rsyslog server. The reader can consult the [Rsyslog Transport](../../../ingestion_methods/rsyslog/) documentation to forward these logs to Sekoia.io.
+Please refer to the documentation of ISC DHPD to forward events to your rsyslog server. The reader can consult the [Rsyslog Transport](../../../ingestion_methods/syslog/overview/) documentation to forward these logs to Sekoia.io.

docs/xdr/features/collect/integrations/application/haproxy.md

@@ -63,7 +63,7 @@ For more information on Rsyslog configuration, please consult the next section.
 
 ### Rsyslog
 
-The reader is invited to consult the [Rsyslog Transport](../../../ingestion_methods/rsyslog/) documentation to forward these logs to Sekoia.io.
+The reader is invited to consult the [Rsyslog Transport](../../../ingestion_methods/syslog/overview/) documentation to forward these logs to Sekoia.io.
 
 ## Further Reading
 - [HAProxy Official Documentation](http://www.haproxy.org/#docs)

docs/xdr/features/collect/integrations/application/microsoft_iis.md

@@ -195,7 +195,7 @@ Restart-Service nxlog
 
 Please read the dedicated documentation for each concentrator:
 
-- [Rsyslog](https://www.notion.so/ingestion_methods/rsyslog/)
+- [Rsyslog](https://www.notion.so/ingestion_methods/syslog/overview/)
 - [Logstash](https://www.notion.so/ingestion_methods/logstash/)
 - [Syslog-ng](https://www.notion.so/ingestion_methods/syslog-ng/)
 - [Graylog](https://www.notion.so/ingestion_methods/graylog/)

docs/xdr/features/collect/integrations/application/nginx.md

@@ -40,7 +40,7 @@ $InputFilePollInterval 1
 $InputRunFileMonitor
 ```
 
-The reader can consult the [Rsyslog Transport](../../../ingestion_methods/rsyslog/) documentation to forward these logs to Sekoia.io.
+The reader can consult the [Rsyslog Transport](../../../ingestion_methods/syslog/overview/) documentation to forward these logs to Sekoia.io.
 
 ### Method 2: configure NGINX to forwards logs using syslog and the UDP protocol
 This method is simplier as you don't need to set up a Rsyslog to forward logs.

docs/xdr/features/collect/integrations/application/openldap.md

@@ -36,7 +36,7 @@ Below is a couple of suggestions you can follow to configure your system to coll
    ```
 
 ### Forward logs to SEKOIA.IO
-Please consult the [Rsyslog Transport](../../../ingestion_methods/rsyslog/) documentation to forward these logs to Sekoia.io.
+Please consult the [Rsyslog Transport](../../../ingestion_methods/syslog/overview/) documentation to forward these logs to Sekoia.io.
 
 ## Further Readings
 

docs/xdr/features/collect/integrations/application/openssh.md

@@ -15,7 +15,7 @@ As of now, the main solution to collect OpenSSH logs leverages the Rsyslog recip
 
 ### Rsyslog
 
-Please refer to the documentation of OpenSSH to forward events to your rsyslog server. The reader can consult the [Rsyslog Transport](../../../ingestion_methods/rsyslog/) documentation to forward these logs to Sekoia.io.
+Please refer to the documentation of OpenSSH to forward events to your rsyslog server. The reader can consult the [Rsyslog Transport](../../../ingestion_methods/syslog/overview/) documentation to forward these logs to Sekoia.io.
 
 ## Further Readings
 

docs/xdr/features/collect/integrations/application/unbound.md

@@ -13,4 +13,4 @@ Unbound is a validating, recursive, and caching DNS resolver product from NLnet
 This setup guide will show you how to forward logs produced by your Unbound server to Sekoia.io by means of an rsyslog transport channel.
 
 ### Configure the Rsyslog server
-Please consult the [Rsyslog Transport](../../../ingestion_methods/rsyslog/) documentation to forward these logs to Sekoia.io.
+Please consult the [Rsyslog Transport](../../../ingestion_methods/syslog/overview/) documentation to forward these logs to Sekoia.io.

docs/xdr/features/collect/integrations/cloud_and_saas/cisco_umbrella/umbrella_dns.md

@@ -26,7 +26,7 @@ logger -t dnslogs -f <YYYY>-<MM>-<DD>-<hh>-<mm>-<xxxx>.csv
 ```
 
 ### Configure the Rsyslog server
-Please consult the [Rsyslog Transport](../../../../ingestion_methods/rsyslog/) documentation to forward these logs to Sekoia.io.
+Please consult the [Rsyslog Transport](../../../../ingestion_methods/syslog/overview/) documentation to forward these logs to Sekoia.io.
 
 ## Further Readings
 - [CISCO Umbrella User Guide - Logs Management](https://docs.umbrella.com/deployment-umbrella/docs/log-management)

docs/xdr/features/collect/integrations/cloud_and_saas/cisco_umbrella/umbrella_ip.md

@@ -24,7 +24,7 @@ logger -t iplogs -f <YYYY>-<MM>-<DD>-<hh>-<mm>-<xxxx>.csv
 ```
 
 ### Configure the Rsyslog server
-Please consult the [Rsyslog Transport](../../../../ingestion_methods/rsyslog/) documentation to forward these logs to Sekoia.io.
+Please consult the [Rsyslog Transport](../../../../ingestion_methods/syslog/overview/) documentation to forward these logs to Sekoia.io.
 
 
 ## Further Readings

docs/xdr/features/collect/integrations/cloud_and_saas/cisco_umbrella/umbrella_proxy.md

@@ -24,7 +24,7 @@ logger -t proxylogs -f <YYYY>-<MM>-<DD>-<hh>-<mm>-<xxxx>.csv
 ```
 
 ### Configure the Rsyslog server
-Please consult the [Rsyslog Transport](../../../../ingestion_methods/rsyslog/) documentation to forward these logs to Sekoia.io.
+Please consult the [Rsyslog Transport](../../../../ingestion_methods/syslog/overview/) documentation to forward these logs to Sekoia.io.
 
 ## Further Readings
 - [CISCO Umbrella User Guide - Logs Management](https://docs.umbrella.com/deployment-umbrella/docs/log-management)

docs/xdr/features/collect/integrations/email/postfix.md

@@ -16,4 +16,4 @@ As of now, the main solution to collect Postfix logs leverages the Rsyslog recip
 
 ### Rsyslog
 
-Please refer to the documentation of Postfix to forward events to your rsyslog server. The reader can consult the [Rsyslog Transport](../../../ingestion_methods/rsyslog/) documentation to forward these logs to Sekoia.io.
+Please refer to the documentation of Postfix to forward events to your rsyslog server. The reader can consult the [Rsyslog Transport](../../../ingestion_methods/syslog/overview/) documentation to forward these logs to Sekoia.io.

docs/xdr/features/collect/integrations/email/spamassassin.md

@@ -11,4 +11,4 @@ SpamAssassin is a computer program used for e-mail spam filtering. SpamAssassin
 {!_shared_content/operations_center/integrations/generated/7954ae6f-eafa-404d-8e15-4b99a12b754c.md!}
 
 ## Configure
-This setup guide will show you how to forward logs produced by your SpamAssassin servers to Sekoia.io by means of an rsyslog transport channel. Please consult the [Rsyslog Transport](../../../ingestion_methods/rsyslog/) documentation to forward these logs to Sekoia.io.
+This setup guide will show you how to forward logs produced by your SpamAssassin servers to Sekoia.io by means of an rsyslog transport channel. Please consult the [Rsyslog Transport](../../../ingestion_methods/syslog/overview/) documentation to forward these logs to Sekoia.io.

docs/xdr/features/collect/integrations/endpoint/auditbeat_linux.md

@@ -271,7 +271,7 @@ sudo systemctl restart rsyslog.service
 
 ### Forward logs to Sekoia.io
 
-The reader is invited to consult the [Rsyslog Transport](../../../ingestion_methods/rsyslog/) documentation or [Syslog Forwarding](../../../ingestion_methods/sekoiaio_forwarder/) documentation to transport logs to Sekoia.io.
+The reader is invited to consult the [Rsyslog Transport](../../../ingestion_methods/syslog/overview/) documentation or [Syslog Forwarding](../../../ingestion_methods/sekoiaio_forwarder/) documentation to transport logs to Sekoia.io.
 
 ### Enjoy your events
 Go to the [events page](https://app.sekoia.io/operations/events) to watch your incoming events.

docs/xdr/features/collect/integrations/endpoint/log_insight_windows.md

@@ -22,4 +22,4 @@ As of now, the main solution to collect Windows logs with Log Insight leverages
 
 ### Rsyslog
 
-Please refer to the documentation of Linux to forward events to your rsyslog server. The reader can consult the [Rsyslog Transport](../../../ingestion_methods/rsyslog/) documentation to forward these logs to Sekoia.io.
+Please refer to the documentation of Linux to forward events to your rsyslog server. The reader can consult the [Rsyslog Transport](../../../ingestion_methods/syslog/overview/) documentation to forward these logs to Sekoia.io.

docs/xdr/features/collect/integrations/endpoint/windows.md

@@ -207,7 +207,7 @@ Restart-Service nxlog
 ### Configure the concentrator to forward events to Sekoia.io
 Please read the dedicated documentation for each concentrator:
 
-* [Rsyslog](../../../ingestion_methods/rsyslog/)
+* [Rsyslog](../../../ingestion_methods/syslog/overview/)
 * [Logstash](../../../ingestion_methods/logstash/)
 * [Syslog-ng](../../../ingestion_methods/syslog-ng/)
 * [Graylog](../../../ingestion_methods/graylog/)

docs/xdr/features/collect/integrations/generic/cef.md

@@ -19,7 +19,7 @@ As of now, the main solution to collect CEF logs leverages the Rsyslog recipe. P
 
 ### Rsyslog
 
-Please refer to the documentation of your vendor to forward events to your rsyslog server. The reader is also invited to consult the [Rsyslog Transport](../../../ingestion_methods/rsyslog/) documentation to forward these logs to Sekoia.io.
+Please refer to the documentation of your vendor to forward events to your rsyslog server. The reader is also invited to consult the [Rsyslog Transport](../../../ingestion_methods/syslog/overview/) documentation to forward these logs to Sekoia.io.
 
 
 ## Further Reading

docs/xdr/features/collect/integrations/network/netfilter.md

@@ -29,7 +29,7 @@ As of now, the main solution to send Netfilter events to Sekoia.io is to use a R
 
 ### Rsyslog
 
-Please consult the [Rsyslog Transport](../../../ingestion_methods/rsyslog/) documentation to forward these logs to Sekoia.io
+Please consult the [Rsyslog Transport](../../../ingestion_methods/syslog/overview/) documentation to forward these logs to Sekoia.io
 
 ### Configure Netfilter using Iptables
 The first step is to configure Netfilter to log the awaited

docs/xdr/features/collect/integrations/network/skyhigh_secure_web_gateway.md

@@ -35,4 +35,4 @@ To forward your logs to our servers, in our MWG console:
 
 - Select `Configuration` section then the `File Editor` tab.
 - In the tree, select `rsyslog.conf`.
-- Consult the [Rsyslog Transport](../../../ingestion_methods/rsyslog/) documentation to configure Rsyslog in order to forward these logs to Sekoia.io.
+- Consult the [Rsyslog Transport](../../../ingestion_methods/syslog/overview/) documentation to configure Rsyslog in order to forward these logs to Sekoia.io.

docs/xdr/features/collect/integrations/network/squid.md

@@ -18,7 +18,7 @@ As of now, the main solution to collect Squid logs leverages the Rsyslog recipe.
 
 ### Rsyslog
 
-In this Section, we detail how to configure Squid’s logging output for Sekoia.io by means of the Rsyslog transport. We hereby focus on the configuration of Squid and invite the reader to the [Rsyslog Transport](../../../ingestion_methods/rsyslog/) documentation to forward these logs to Sekoia.io.
+In this Section, we detail how to configure Squid’s logging output for Sekoia.io by means of the Rsyslog transport. We hereby focus on the configuration of Squid and invite the reader to the [Rsyslog Transport](../../../ingestion_methods/syslog/overview/) documentation to forward these logs to Sekoia.io.
 
 To configure Squid logging, you can create a new configuration `99-sekoiaio.conf` file in the `/etc/squid/conf.d/` directory of your server. With most of Squid configurations (including Debian, Red Hat Entreprise Linux, etc.), this file will automatically be used.
 

docs/xdr/features/collect/integrations/network/suricata.md

@@ -36,7 +36,7 @@ outputs:
 ```
 
 ### Configure the Rsyslog server
-Given this Suricata configuration, your local rsyslog server will handle produced records. Please consult the [Rsyslog Transport](../../../ingestion_methods/rsyslog/) documentation to forward these logs to Sekoia.io.
+Given this Suricata configuration, your local rsyslog server will handle produced records. Please consult the [Rsyslog Transport](../../../ingestion_methods/syslog/overview/) documentation to forward these logs to Sekoia.io.
 
 ## Further Readings
 - [Suricata User Guide](https://suricata.readthedocs.io/)

docs/xdr/features/collect/integrations/network/trellix_nx.md

@@ -40,4 +40,4 @@ You should have:
 Go to the [intake page](https://app.sekoia.io/operations/intakes) and create a new intake from the format Trellix Network Security.
 
 ### Configure the Rsyslog server
-Please consult the [Rsyslog Transport](../../../ingestion_methods/rsyslog/) documentation to forward these logs to Sekoia.io.
+Please consult the [Rsyslog Transport](../../../ingestion_methods/syslog/overview/) documentation to forward these logs to Sekoia.io.

docs/xdr/features/collect/integrations/network/vectra.md

@@ -14,4 +14,4 @@ Vectra provides AI-powered incident detection and resolution support for native
 This setup guide will show you how to forward logs produced by your Vectra Appliance server to Sekoia.io by means of an rsyslog transport channel.
 
 ### Configure the Rsyslog server
-Please consult the [Rsyslog Transport](../../../ingestion_methods/rsyslog/) documentation to forward these logs to Sekoia.io.
+Please consult the [Rsyslog Transport](../../../ingestion_methods/syslog/overview/) documentation to forward these logs to Sekoia.io.

docs/xdr/features/collect/integrations/network/wallix.md

@@ -14,4 +14,4 @@ WALLIX Bastion is a “Privileged Access Management” solution.
 This setup guide will show you how to forward logs produced by your Wallix bastion to Sekoia.io by means of an rsyslog transport channel.
 
 ### Configure the Rsyslog server
-Please consult the [Rsyslog Transport](../../../ingestion_methods/rsyslog/) documentation to forward these logs to Sekoia.io.
+Please consult the [Rsyslog Transport](../../../ingestion_methods/syslog/overview/) documentation to forward these logs to Sekoia.io.

docs/xdr/features/collect/integrations/network/watchguard_firebox.md

@@ -30,7 +30,7 @@ Go to the [intake page](https://app.sekoia.io/operations/intakes) and create a n
 
 ## Forward logs to Sekoia.io
 
-Please consult the [Rsyslog Transport](../../../ingestion_methods/rsyslog/) documentation or [Syslog Forwarding](../../../../ingestion_methods/sekoiaio_forwarder/) documentation to forward these logs to Sekoia.io.
+Please consult the [Rsyslog Transport](../../../ingestion_methods/syslog/overview/) documentation or [Syslog Forwarding](../../../../ingestion_methods/sekoiaio_forwarder/) documentation to forward these logs to Sekoia.io.
 
 ## Further Readings
 - [Watchguard Firebox Rsyslog Integration Overview](https://www.watchguard.com/help/docs/help-center/en-US/Content/Integration-Guides/General/ubuntu_rsyslog.html)

docs/xdr/features/collect/integrations/network/zeek.md

@@ -11,7 +11,7 @@ Zeek is a free and open-source software network analysis framework; it was origi
 {!_shared_content/operations_center/integrations/generated/428035c0-a251-4664-8e58-fed15f4e442c.md!}
 
 ## Configure
-Refer to the configuration of Zeek's export to syslog to forward dns, http and conn logs to Sekoia.io by means of an rsyslog transport channel. Please consult the [Rsyslog Transport](../../../ingestion_methods/rsyslog/) documentation to forward these logs to Sekoia.io.
+Refer to the configuration of Zeek's export to syslog to forward dns, http and conn logs to Sekoia.io by means of an rsyslog transport channel. Please consult the [Rsyslog Transport](../../../ingestion_methods/syslog/overview/) documentation to forward these logs to Sekoia.io.
 
 
 ## Further Reading

docs/xdr/xdr_quick_start.md

@@ -25,7 +25,7 @@ The Intakes correspond to the different technologies used (also called Data Sour
 To create intakes associated to the technology you would like to collect:
 
 1. Go to the Intakes page and create intakes one by one from the catalog.
-2. Make sure the logs are pushed to Sekoia.io using [syslog](https://docs.sekoia.io/xdr/features/collect/ingestion_methods/rsyslog/) or [HTTPS](https://docs.sekoia.io/xdr/features/collect/ingestion_methods/https/) protocols providing the `Intake key` accordingly, or pulled by API.
+2. Make sure the logs are pushed to Sekoia.io using [syslog](https://docs.sekoia.io/xdr/features/collect/ingestion_methods/syslog/overview/) or [HTTPS](https://docs.sekoia.io/xdr/features/collect/ingestion_methods/https/overview/) protocols providing the `Intake key` accordingly, or pulled by API.
 
 !!! note
     Find more details on each integration in our [integrations catalog](https://docs.sekoia.io/xdr/features/collect/integrations/).