From 36332d19d2fab3729702afbe9ee045be2da783ab Mon Sep 17 00:00:00 2001 From: Pierre Penhouet Date: Mon, 5 Aug 2024 11:49:52 +0200 Subject: [PATCH 1/2] Fix broken links --- _shared_content/integration/forwarder_configuration.md | 4 ++-- docs/integration/categories/endpoint/vmware_esxi.md | 2 +- docs/integration/categories/endpoint/vmware_vcenter.md | 2 +- docs/integration/categories/network_security/sophos_fw.md | 2 +- .../categories/network_security/watchguard_firebox.md | 2 +- docs/integration/ingestion_methods/index.md | 4 ++-- .../syslog/{secured_forwarded.md => secured_forwarding.md} | 0 mkdocs.yml | 4 ++-- 8 files changed, 10 insertions(+), 10 deletions(-) rename docs/integration/ingestion_methods/syslog/{secured_forwarded.md => secured_forwarding.md} (100%) diff --git a/_shared_content/integration/forwarder_configuration.md b/_shared_content/integration/forwarder_configuration.md index ee8e122922..9699a63f07 100644 --- a/_shared_content/integration/forwarder_configuration.md +++ b/_shared_content/integration/forwarder_configuration.md @@ -12,8 +12,8 @@ and after To achieve this you can: -- Use the [Sekoia.io forwarder](./sekoiaio_forwarder.md) which is the official supported way to collect data using the syslog protocol in Sekoia.io. In charge of centralizing data coming from many equipments/sources and forwarding them to Sekoia.io with the apporpriated format, it is a prepackaged option. You only have to provide your intake key as parameter. -- Use your own [Syslog service](./syslog_service.md) instance. Maybe you already have an intance of one of these components on your side and want to reuse it in order to centralize data before forwarding them to Sekoia.io. When using this mode, you have to configure and maintain your component in order to respect the expected Sekoia.io format. +- Use the [Sekoia.io forwarder](/integration/ingestion_methods/syslog/sekoiaio_forwarder/) which is the official supported way to collect data using the syslog protocol in Sekoia.io. In charge of centralizing data coming from many equipments/sources and forwarding them to Sekoia.io with the apporpriated format, it is a prepackaged option. You only have to provide your intake key as parameter. +- Use your own [Syslog service](/integration/ingestion_methods/syslog/syslog_service/) instance. Maybe you already have an intance of one of these components on your side and want to reuse it in order to centralize data before forwarding them to Sekoia.io. When using this mode, you have to configure and maintain your component in order to respect the expected Sekoia.io format. !!! warning diff --git a/docs/integration/categories/endpoint/vmware_esxi.md b/docs/integration/categories/endpoint/vmware_esxi.md index 11c45ad295..1025bc5ba3 100644 --- a/docs/integration/categories/endpoint/vmware_esxi.md +++ b/docs/integration/categories/endpoint/vmware_esxi.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 [Syslog Forwarding](../../../../ingestion_methods/sekoiaio_forwarder/) documentation to forward these logs to Sekoia.io. +Please consult the [Syslog Forwarding](../../../ingestion_methods/sekoiaio_forwarder/) documentation to forward these logs to Sekoia.io. {!_shared_content/operations_center/integrations/generated/2b13307b-7439-4973-900a-2b58303cac90_sample.md!} diff --git a/docs/integration/categories/endpoint/vmware_vcenter.md b/docs/integration/categories/endpoint/vmware_vcenter.md index 5da8de6899..b416b24a87 100644 --- a/docs/integration/categories/endpoint/vmware_vcenter.md +++ b/docs/integration/categories/endpoint/vmware_vcenter.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 [Syslog Forwarding](../../../../ingestion_methods/sekoiaio_forwarder/) documentation to forward these logs to Sekoia.io. +Please consult the [Syslog Forwarding](../../../ingestion_methods/sekoiaio_forwarder/) documentation to forward these logs to Sekoia.io. Create a new configuration file: diff --git a/docs/integration/categories/network_security/sophos_fw.md b/docs/integration/categories/network_security/sophos_fw.md index db8d03a705..2365bb2ec9 100644 --- a/docs/integration/categories/network_security/sophos_fw.md +++ b/docs/integration/categories/network_security/sophos_fw.md @@ -31,7 +31,7 @@ You can configure a syslog server in Sophos Firewall by following the instructio ### Forward logs to Sekoia.io -Please consult the [Syslog Forwarding](../../../../ingestion_methods/sekoiaio_forwarder/) documentation to forward these logs to Sekoia.io. +Please consult the [Syslog Forwarding](../../../ingestion_methods/sekoiaio_forwarder/) documentation to forward these logs to Sekoia.io. {!_shared_content/operations_center/integrations/generated/325369ba-8515-45b4-b750-5db882ea1266_sample.md!} diff --git a/docs/integration/categories/network_security/watchguard_firebox.md b/docs/integration/categories/network_security/watchguard_firebox.md index 1582447799..be73e9e568 100644 --- a/docs/integration/categories/network_security/watchguard_firebox.md +++ b/docs/integration/categories/network_security/watchguard_firebox.md @@ -34,7 +34,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/syslog/overview/) 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. {!_shared_content/operations_center/integrations/generated/d719e8b5-85a1-4dad-bf71-46155af56570_sample.md!} diff --git a/docs/integration/ingestion_methods/index.md b/docs/integration/ingestion_methods/index.md index 9ea686e1f3..9a4b41dbe9 100644 --- a/docs/integration/ingestion_methods/index.md +++ b/docs/integration/ingestion_methods/index.md @@ -12,7 +12,7 @@ Sekoia.io supports the following log collecting methods: - [HTTPS](/integration/ingestion_methods/https/overview/) (`https://intake.sekoia.io`): `POST` your JSON events to Sekoia.io. - [Syslog](/integration/ingestion_methods/syslog/overview/) over TLS (`intake.sekoia.io:10514`): forward your events with the Syslog protocol specified in RFC 5424. -- [RELP](/integration/ingestion_methods/syslog/syslog_service/#how-to-forward-logs-to-sekoiaio-using-relp) over TLS (`relp.intake.sekoia.io:11514`): forward your events with Rsyslog’s reliable protocol called RELP. +- [RELP](/integration/ingestion_methods/syslog/rsyslog/#how-to-forward-logs-to-sekoiaio-using-relp) over TLS (`relp.intake.sekoia.io:11514`): forward your events with Rsyslog’s reliable protocol called RELP. - [Cloud hosting and API polling](/integration/ingestion_methods/cloud_saas/overview/): configure Sekoia.io to regularly retrieve your logs. If these solutions do not meet your needs, contact our support. @@ -30,7 +30,7 @@ and after <%pri%>1 %timestamp:::date-rfc3339% %hostname% %app-name% %procid% LOG [SEKOIA@53288 intake_key=\"YOUR_INTAKE_KEY\"] RAW_MESSAGE ``` -We provide [documentation and example configurations](/integration/ingestion_methods/syslog/overview/) on how to configure your log system for Rsyslog, syslog-ng or use our [Sekoia.io Forwarder](/integration/ingestion_methods/syslog/sekoiaio_forwarder/, but it should be easy to configure other log collectors to forward their events to Sekoia.io. +We provide [documentation and example configurations](/integration/ingestion_methods/syslog/overview/) on how to configure your log system for Rsyslog, syslog-ng or use our [Sekoia.io Forwarder](/integration/ingestion_methods/syslog/sekoiaio_forwarder/), but it should be easy to configure other log collectors to forward their events to Sekoia.io. ## HTTPS integration diff --git a/docs/integration/ingestion_methods/syslog/secured_forwarded.md b/docs/integration/ingestion_methods/syslog/secured_forwarding.md similarity index 100% rename from docs/integration/ingestion_methods/syslog/secured_forwarded.md rename to docs/integration/ingestion_methods/syslog/secured_forwarding.md diff --git a/mkdocs.yml b/mkdocs.yml index d28d6a8ac5..5f2a8d6072 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -305,10 +305,10 @@ nav: - Logstash: integration/ingestion_methods/https/logstash.md - Syslog: - Overview: integration/ingestion_methods/syslog/overview.md - - Rsyslog: integration/ingestion_methods/syslog/rsyslog.md - - Secured Forwarded: integration/ingestion_methods/syslog/secured_forwarded.md - Sekoia.io Forwarder: integration/ingestion_methods/syslog/sekoiaio_forwarder.md + - Secured Forwarding: integration/ingestion_methods/syslog/secured_forwarding.md - Third-party syslog services: integration/ingestion_methods/syslog/syslog_service.md + - Rsyslog: integration/ingestion_methods/syslog/rsyslog.md - Syslog NG: integration/ingestion_methods/syslog/syslog-ng.md - List of Intakes: - Overview: integration/categories/overview.md From 2c99ef1b577e0b3b4ece79c0d8610fe1ce159cd1 Mon Sep 17 00:00:00 2001 From: Pierre Penhouet Date: Mon, 5 Aug 2024 11:52:55 +0200 Subject: [PATCH 2/2] Remove secured forwarding page --- mkdocs.yml | 1 - 1 file changed, 1 deletion(-) diff --git a/mkdocs.yml b/mkdocs.yml index 5f2a8d6072..caf62ca4da 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -306,7 +306,6 @@ nav: - Syslog: - Overview: integration/ingestion_methods/syslog/overview.md - Sekoia.io Forwarder: integration/ingestion_methods/syslog/sekoiaio_forwarder.md - - Secured Forwarding: integration/ingestion_methods/syslog/secured_forwarding.md - Third-party syslog services: integration/ingestion_methods/syslog/syslog_service.md - Rsyslog: integration/ingestion_methods/syslog/rsyslog.md - Syslog NG: integration/ingestion_methods/syslog/syslog-ng.md