diff --git a/i18n/fr/docusaurus-plugin-content-docs-logmanagement/current/collector/collector-generator.md b/i18n/fr/docusaurus-plugin-content-docs-logmanagement/current/collector/collector-generator.md
new file mode 100644
index 000000000000..c6a1028875e6
--- /dev/null
+++ b/i18n/fr/docusaurus-plugin-content-docs-logmanagement/current/collector/collector-generator.md
@@ -0,0 +1,38 @@
+---
+id: collector-generator
+title: Générer un fichier de configuration de collecteur OTel
+---
+
+La configuration d'un collecteur OpenTelemetry peut être complexe. Log Management propose une interface où vous sélectionnez des extraits de configuration pour vos sources de données (snippets), puis les adaptez à votre environnement. Vous téléchargez ensuite le résultat, prêt à l'emploi.
+
+D'autres sources de données seront ajoutées au fil du temps. Si votre source de données ne figure pas dans la liste, utilisez plutôt la [procédure de configuration manuelle](collector.md).
+
+Le fichier généré contient des receivers, des processors et des exporters, comme expliqué dans [Fonctionnement d'un collecteur OpenTelemetry](opentelemetry-collector.md).
+
+## Étape 1 : Configurer les receivers
+
+1. Allez à la page **OTel collector configurator**, puis cliquez sur **Create**.
+2. Dans la fenêtre qui s'ouvre, sélectionnez le pack correspondant à la source de données souhaitée :
+   * Utilisez la barre de recherche en haut de la fenêtre, ou
+   * Cliquez sur **Add pack** dans la section **Configure packs**.
+   
+   Pour le moment, un pack contient un seul snippet.
+   
+   Une fois le pack sélectionné, un résumé apparaît dans la section **Configure packs** et le panneau **Preview configuration YAML** est mis à jour. Votre source de données est alors ajoutée à la section **receivers** du fichier de configuration.
+3. Vérifiez que le fichier de log affiché dans la section **Configure packs** pour votre source de données est correct.
+
+## Étape 2 : Configurer les processors
+
+1. Activez et configurez les paramètres souhaités dans la section **Configure processors**. Ceux-ci seront ajoutés à la section **processors** du fichier de configuration et s'appliqueront à toutes les sources de données.
+2. Vérifiez que tout est correct dans le panneau **Preview configuration YAML**.
+   * Un exporter pour Centreon Log Management est déjà pré-configuré (vous devrez le compléter à l'[étape 3](#étape-3--renseigner-le-jeton-dauthentification-pour-centreon-log-management)).
+   * Le pipeline adapté à vos receivers, processor et exporter est généré automatiquement.
+
+## Étape 3 : Renseigner le jeton d'authentification pour Centreon Log Management
+
+1. Copiez ou téléchargez votre fichier de configuration à l'aide des boutons en bas de la fenêtre.
+2. Avant de déployer votre fichier de configuration, remplacez la valeur d'exemple dans le champ **X-Api-Key** par votre [jeton d'authentification](../administration/tokens.md) Log Management.
+
+## Étape 4 : Déployer votre fichier de configuration
+
+Déployez votre fichier de configuration sur le serveur depuis lequel vous souhaitez collecter des logs.
diff --git a/i18n/fr/docusaurus-plugin-content-docs-logmanagement/current/collector/collector-simple.md b/i18n/fr/docusaurus-plugin-content-docs-logmanagement/current/collector/collector-simple.md
deleted file mode 100644
index 50017140742c..000000000000
--- a/i18n/fr/docusaurus-plugin-content-docs-logmanagement/current/collector/collector-simple.md
+++ /dev/null
@@ -1,232 +0,0 @@
----
-id: collector-simple
-title: Configurations simples de collecteur
-description: Exemples de configuration rapide de collecteur pour des sources de logs courantes
----
-
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
-Voici deux exemples de configurations simples. Si vous souhaitez collecter plusieurs types de logs à partir d'un même hôte, utilisez la page [Configuration complète de collecteur (sources de logs multiples)](collector.md).
-
-## Exemple 1 : Configuration rapide pour commencer à collecter les logs de l'Observateur d'événements Windows
-
-1. Sur une machine Windows, [installez l'OpenTelemetry Collector](https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.147.0/otelcol-contrib_0.147.0_windows_x64.msi).
-
-2. Dans Centreon Log Management, [générez un jeton pour authentifier l'hôte auprès de votre plateforme Log Management](../administration/tokens.md).
-
-3. Sur votre machine Windows, modifiez le fichier **config.yaml** qui a été créé dans le répertoire où vous avez installé OpenTelemetry Collector. Par défaut, il se trouve ici :
-
-   ```shell
-   C:\Program Files\OpenTelemetry Collector\config.yaml
-   ```
-
-4. Remplacez le contenu du fichier par l'extrait ci-dessous (remplacez **mytoken** par votre jeton). Veillez à enregistrer le fichier en tant qu'administrateur.
-
-   ```yaml
-   # Copyright 2025 Centreon.
-   # SPDX-License-Identifier: Apache-2.0
-
-   exporters:
-     otlphttp/centreon: # The exporter that will send logs to Log Management
-       endpoint: "https://api.euwest1.obs.mycentreon.com/v1/ingress/otlp"
-       headers:
-         "X-Api-Key": "mytoken" ## Replace mytoken by your actual token
-     debug: # The exporter that will write debug info to log files
-       verbosity: detailed
-   
-   processors:
-     batch: # This processor optimizes performance.
-     resourcedetection: # This processor enriches ALL logs with the information defined below.
-       detectors: ["system"]
-       system:
-         resource_attributes: # Each log entry will include the 4 attributes listed below.
-           host.name:
-             enabled: true
-           os.name:
-             enabled: true
-           os.type:
-             enabled: true
-           os.version:
-             enabled: true
-   
-   receivers:
-     windowseventlog/application:
-       channel: application
-       operators:
-         - type: severity_parser
-           parse_from: body.level
-           overwrite_text: true
-           mapping:
-             fatal:
-               - Critical
-               - Critique
-             error:
-               - Error
-               - Erreur
-             warn:
-               - Warning
-               - Avertissement
-             info:
-               - Informational
-               - Information
-         - type: copy
-           from: body.execution.process_id
-           to: attributes["process.pid"]
-         - type: copy
-           from: body.provider.name
-           to: resource["event.provider.name"]
-         - type: copy
-           from: body.provider.guid
-           to: resource["event.provider.guid"]
-           if: "body.provider.guid != ''"
-         - type: copy
-           from: body.event_id.id
-           to: attributes["event.id"]
-         - type: copy
-           from: body.record_id
-           to: attributes["event.record.id"]
-         - type: copy
-           from: body.task
-           to: attributes["event.task"]
-         - type: move
-           from: body.message
-           to: body
-         - type: add
-           field: resource["service.version"]
-           value: "1.0.0"
-         - type: add
-           field: resource["service.name"]
-           value: "windows-event-log"
-         - type: add
-           field: resource["service.namespace"]
-           value: "application"
-   
-   service:
-     pipelines: # This defines the order in which the collector runs its components.
-       logs:
-         receivers: [windowseventlog/application]
-         processors: [batch, resourcedetection]
-         exporters: [otlphttp/centreon]
-   ```
-
-5. redémarrez le service OpenTelemetry Collector.
-
-   ```shell
-   net stop otelcol-contrib
-   net start otelcol-contrib
-   ```
-
-   Vous devriez commencer à recevoir des logs dans Centreon Log Management.
-
-## Exemple 2 : Un fichier de configuration avec 3 sources de logs
-
-Dans l'exemple suivant, nous recevons des données provenant de trois sources différentes sur le même serveur Windows. Les logs transitent par un seul pipeline. Toute la configuration est regroupée dans le fichier **config.yaml** du collecteur. (Suivez la même procédure que pour l'exemple 1 et adaptez le fichier de configuration ci-dessous.)
-
-![image](../assets/receivers-processors-exporters.png)
-
-```yaml
-# Copyright 2025 Centreon
-# SPDX-License-Identifier: Apache-2.0
-
-exporters:
-  otlphttp/centreon: # The exporter that will send logs to Log Management
-    endpoint: "https://api.euwest1.obs.mycentreon.com/v1/ingress/otlp"
-    headers:
-      "X-Api-Key": "mytoken" ## Replace mytoken by your actual token
-  debug: # The exporter that will write debug info to log files
-    verbosity: detailed
-
-processors:
-  batch: # This processor optimizes performance.
-  resourcedetection: # This processor enriches ALL logs with the information defined below.
-    detectors: ["system"]
-    system:
-      resource_attributes: # Each log entry will include the 4 attributes listed below.
-        host.name:
-          enabled: true
-        os.name:
-          enabled: true
-        os.type:
-          enabled: true
-        os.version:
-          enabled: true
-
-receivers:
-
-  windowseventlog/application: # You will receive logs from the Windows Application Event Log.
-    channel: application
-    operators:
-      - type: severity_parser
-        parse_from: body.level
-        overwrite_text: true
-        mapping:
-          fatal: [Critical, Critique]
-          error: [Error, Erreur]
-          warn: [Warning, Avertissement]
-          info: [Informational, Information]
-      - type: move
-        from: body.message
-        to: body
-      - type: add
-        field: resource["service.namespace"]
-        value: "application"
-      - type: add
-        field: resource["service.name"]
-        value: "windows-event-logs"
-
-  filelog/mssql: # You will receive logs from Microsoft SQL Server log files.
-
-    include: 
-      - 'C:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\Log\ERRORLOG'
-    encoding: utf-16le
-    start_at: end
-    multiline:
-      line_start_pattern: '^\d{4}-\d{2}-\d{2}' 
-    operators:
-      - type: regex_parser
-        regex: '^(?P<time>\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2}\.\d+)\s+(?P<source>[^\s]+)\s+(?P<msg>(?s).*)'
-        timestamp:
-          parse_from: attributes.time
-          layout: '%Y-%m-%d %H:%M:%S.%f'
-      - type: add
-        field: resource["service.name"]
-        value: "mssql-server"  
-
-  filelog/messages: # You will receive logs from the system log files specified in the "include" attribute.
-    include:
-      - /var/log/messages
-    include_file_path: true
-    operators:
-      - type: regex_parser
-        regex: '^(?P<ts>\w{3}\s\d{2}\s\d{2}:\d{2}:\d{2})\s(?P<hostname>[\w_-]+)\s(?P<process>[\w_-]+)(\[(?<pid>\d+)\])?:\s(?<body>.*)$'
-        timestamp:
-          parse_from: attributes["ts"]
-          layout: '%b %d %H:%M:%S'
-      - type: move
-        from: attributes["pid"]
-        to: attributes["process.pid"]
-      - type: move
-        from: attributes["process"]
-        to: resource["service.name"]
-      - type: remove
-        field: attributes["ts"]
-      - type: move
-        from: attributes["body"]
-        to: body
-      # Add a service version, the template version
-      - type: add
-        field: resource["service.version"]
-        value: '1.0.0'
-      # Remove the hostname, use the resource detectors
-      - type: remove
-        field: attributes["hostname"]
-
-service:
-  pipelines: # This defines the order in which the collector runs its components.
-    logs:
-      receivers: [windowseventlog/application, filelog/mssql, filelog/messages]
-      processors: [batch, resourcedetection]
-      exporters: [otlphttp/centreon, debug]
-
-```
diff --git a/i18n/fr/docusaurus-plugin-content-docs-logmanagement/current/collector/collector.md b/i18n/fr/docusaurus-plugin-content-docs-logmanagement/current/collector/collector.md
index d8977dde5e7d..32335218db6d 100644
--- a/i18n/fr/docusaurus-plugin-content-docs-logmanagement/current/collector/collector.md
+++ b/i18n/fr/docusaurus-plugin-content-docs-logmanagement/current/collector/collector.md
@@ -1,18 +1,20 @@
 ---
 id: collector
-title: Configuration complète de collecteur (sources de logs multiples)
+title: Configuration manuelle de collecteur
 description: Configurer un collecteur OpenTelemetry pour collecter plusieurs sources de logs sur un même hôte
 ---
 
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-La section [Configurations simples de collecteur](opentelemetry-collector.md) fournit un fichier de configuration permettant de mettre en place la collecte des logs à partir d'une machine Windows. La procédure ci-dessous est plus adaptée aux cas où plusieurs types de journaux sont collectés sur le même hôte (sous Windows comme sous Linux).
+La page [Générer un fichier de configuration de collecteur OTel](./collector-generator.md) vous fournit une procédure simplifiée prenant en charge certaines sources de données. Si vous ne trouvez pas le snippet désiré dans la liste des sources de données disponibles, utilisez la procédure ci-dessous.
+
+<!-- La section [Configurations simples de collecteur](opentelemetry-collector.md) fournit un fichier de configuration permettant de mettre en place la collecte des logs à partir d'une machine Windows. La procédure ci-dessous est plus adaptée aux cas où plusieurs types de journaux sont collectés sur le même hôte (sous Windows comme sous Linux).
 
 > **Gagnez du temps avec les modèles Centreon**
 >
 > Centreon met à disposition [des modèles de configuration prêts à l'emploi pour les sources de logs les plus courantes](https://github.com/CentreonLabs/centreon-otel-col-log-template/tree/main). Utilisez-les comme point de départ pour configurer rapidement votre collecteur.
-
+ -->
 Si vous rencontrez des problèmes, consultez la page [Dépanner votre installation](collector-troubleshooting.md).
 
 <!-- attributs custom
diff --git a/logmanagement/collector/collector-generator.md b/logmanagement/collector/collector-generator.md
new file mode 100644
index 000000000000..f135da89fa5c
--- /dev/null
+++ b/logmanagement/collector/collector-generator.md
@@ -0,0 +1,38 @@
+---
+id: collector-generator
+title: Generating an OTel collector configuration file
+---
+
+Configuring an OpenTelemetry Collector can be complex. Log Management provides an interface where you can select configuration snippets for your data sources and edit them to match your setup. You then download the ready-to-use result.
+
+More data sources will be added over time. If your data source is not listed, use the [manual configuration procedure](collector.md) instead.
+
+The generated file contains receivers, processors and exporters as explained in [How an OpenTelemetry collector works](opentelemetry-collector.md).
+
+## Step 1: Configure receivers
+
+1. Go to **OTel collector configurator** and then click **Create**.
+2. In the window that opens, select the correct pack for the data source you want:
+   * Use the search bar at the top of the window, or
+   * Click **Add pack** in the **Configure packs** section.
+
+   At the moment, a pack contains just one snippet.
+
+   Once you have selected a pack, a summary appears in the **Configure packs** section and the **Preview configuration YAML** panel is updated. Your data source is then added to the **receivers** section of the configuration file.
+3. Check that the log file displayed in the **Configure packs** section for your data source is correct.
+
+## Step 2: Configure processors
+
+1. Enable and configure any parameters you want in the **Configure processors** section. These will be added to the **processors** section of the configuration file and will apply to every data source.
+2. Check that everything is correct in the **Preview configuration YAML** panel.
+   * An exporter for Centreon Log Management is already pre-configured (you will have to complete it in [step 3](#step-3-enter-the-authentication-token-for-centreon-log-management)).
+   * The correct pipeline for your receivers, processor and exporter is generated automatically.
+
+## Step 3: Enter the authentication token for Centreon Log Management
+
+1. Copy or download your configuration file using the buttons at the bottom of the window.
+2. Before you deploy your configuration file, make sure you replace the placeholder value in the **X-Api-Key** field with your Log Management [authentication token](../administration/tokens.md).
+
+## Step 4: Deploy your configuration file
+
+Deploy your configuration file on the server you want to collect logs from.
diff --git a/logmanagement/collector/collector-simple.md b/logmanagement/collector/collector-simple.md
deleted file mode 100644
index 37da4ae6e03e..000000000000
--- a/logmanagement/collector/collector-simple.md
+++ /dev/null
@@ -1,232 +0,0 @@
----
-id: collector-simple
-title: Simple collector configurations
-description: Quick collector configuration examples for common log sources
----
-
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-
-Here are two examples of simple configurations. If you want to collect many types of logs from the same host, use [Full collector configuration (multiple log sources)](collector.md).
-
-## Example 1: Quick configuration to start collecting logs from Windows Event Viewer
-
-1. On a Windows machine, [install the OpenTelemetry Collector](https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.147.0/otelcol-contrib_0.147.0_windows_x64.msi).
-
-2. In Centreon Log Management, [generate a token to authenticate the host to your Log Management platform](../administration/tokens.md).
-
-3. On your Windows machine, edit the **config.yaml** file that was created in the directory where you installed OpenTelemetry Collector. By default, it is located here:
-
-   ```shell
-   C:\Program Files\OpenTelemetry Collector\config.yaml
-   ```
-
-4. Replace the file's contents by the snippet below (replace **mytoken** with your actual token). Make sure you save the file as an administrator.
-
-   ```yaml
-   # Copyright 2025 Centreon.
-   # SPDX-License-Identifier: Apache-2.0
-
-   exporters:
-     otlphttp/centreon: # The exporter that will send logs to Log Management
-       endpoint: "https://api.euwest1.obs.mycentreon.com/v1/ingress/otlp"
-       headers:
-         "X-Api-Key": "mytoken" ## Replace mytoken by your actual token
-     debug: # The exporter that will write debug info to log files
-       verbosity: detailed
-   
-   processors:
-     batch: # This processor optimizes performance.
-     resourcedetection: # This processor enriches ALL logs with the information defined below.
-       detectors: ["system"]
-       system:
-         resource_attributes: # Each log entry will include the 4 attributes listed below.
-           host.name:
-             enabled: true
-           os.name:
-             enabled: true
-           os.type:
-             enabled: true
-           os.version:
-             enabled: true
-   
-   receivers:
-     windowseventlog/application:
-       channel: application
-       operators:
-         - type: severity_parser
-           parse_from: body.level
-           overwrite_text: true
-           mapping:
-             fatal:
-               - Critical
-               - Critique
-             error:
-               - Error
-               - Erreur
-             warn:
-               - Warning
-               - Avertissement
-             info:
-               - Informational
-               - Information
-         - type: copy
-           from: body.execution.process_id
-           to: attributes["process.pid"]
-         - type: copy
-           from: body.provider.name
-           to: resource["event.provider.name"]
-         - type: copy
-           from: body.provider.guid
-           to: resource["event.provider.guid"]
-           if: "body.provider.guid != ''"
-         - type: copy
-           from: body.event_id.id
-           to: attributes["event.id"]
-         - type: copy
-           from: body.record_id
-           to: attributes["event.record.id"]
-         - type: copy
-           from: body.task
-           to: attributes["event.task"]
-         - type: move
-           from: body.message
-           to: body
-         - type: add
-           field: resource["service.version"]
-           value: "1.0.0"
-         - type: add
-           field: resource["service.name"]
-           value: "windows-event-log"
-         - type: add
-           field: resource["service.namespace"]
-           value: "application"
-   
-   service:
-     pipelines: # This defines the order in which the collector runs its components.
-       logs:
-         receivers: [windowseventlog/application]
-         processors: [batch, resourcedetection]
-         exporters: [otlphttp/centreon]
-   ```
-
-5. Restart the OpenTelemetry Collector service.
-
-   ```shell
-   net stop otelcol-contrib
-   net start otelcol-contrib
-   ```
-
-   You should start receiving logs in Centreon Log Management.
-
-## Example 2 : One configuration file with 3 log sources
-
-In the following example, we receive data from three different sources on the same Windows server. Logs go through only one pipeline. All of the configuration is gathered into the collector's **config.yaml** file. (Follow the same procedure as in example 1 and adapt the configuration file below.)
-
-![image](../assets/receivers-processors-exporters.png)
-
-```yaml
-# Copyright 2025 Centreon.
-# SPDX-License-Identifier: Apache-2.0
-
-exporters:
-  otlphttp/centreon: # The exporter that will send logs to Log Management
-    endpoint: "https://api.euwest1.obs.mycentreon.com/v1/ingress/otlp"
-    headers:
-      "X-Api-Key": "mytoken" ## Replace mytoken by your actual token
-  debug: # The exporter that will write debug info to log files
-    verbosity: detailed
-
-processors:
-  batch: # This processor optimizes performance.
-  resourcedetection: # This processor enriches ALL logs with the information defined below.
-    detectors: ["system"]
-    system:
-      resource_attributes: # Each log entry will include the 4 attributes listed below.
-        host.name:
-          enabled: true
-        os.name:
-          enabled: true
-        os.type:
-          enabled: true
-        os.version:
-          enabled: true
-
-receivers:
-
-  windowseventlog/application: # You will receive logs from the Windows Application Event Log.
-    channel: application
-    operators:
-      - type: severity_parser
-        parse_from: body.level
-        overwrite_text: true
-        mapping:
-          fatal: [Critical, Critique]
-          error: [Error, Erreur]
-          warn: [Warning, Avertissement]
-          info: [Informational, Information]
-      - type: move
-        from: body.message
-        to: body
-      - type: add
-        field: resource["service.namespace"]
-        value: "application"
-      - type: add
-        field: resource["service.name"]
-        value: "windows-event-logs"
-
-  filelog/mssql: # You will receive logs from Microsoft SQL Server log files.
-
-    include: 
-      - 'C:\Program Files\Microsoft SQL Server\MSSQL16.MSSQLSERVER\MSSQL\Log\ERRORLOG'
-    encoding: utf-16le
-    start_at: end
-    multiline:
-      line_start_pattern: '^\d{4}-\d{2}-\d{2}' 
-    operators:
-      - type: regex_parser
-        regex: '^(?P<time>\d{4}-\d{2}-\d{2} \d{2}:\d{2}:\d{2}\.\d+)\s+(?P<source>[^\s]+)\s+(?P<msg>(?s).*)'
-        timestamp:
-          parse_from: attributes.time
-          layout: '%Y-%m-%d %H:%M:%S.%f'
-      - type: add
-        field: resource["service.name"]
-        value: "mssql-server"  
-
-  filelog/messages: # You will receive logs from the system log files specified in the "include" attribute.
-    include:
-      - /var/log/messages
-    include_file_path: true
-    operators:
-      - type: regex_parser
-        regex: '^(?P<ts>\w{3}\s\d{2}\s\d{2}:\d{2}:\d{2})\s(?P<hostname>[\w_-]+)\s(?P<process>[\w_-]+)(\[(?<pid>\d+)\])?:\s(?<body>.*)$'
-        timestamp:
-          parse_from: attributes["ts"]
-          layout: '%b %d %H:%M:%S'
-      - type: move
-        from: attributes["pid"]
-        to: attributes["process.pid"]
-      - type: move
-        from: attributes["process"]
-        to: resource["service.name"]
-      - type: remove
-        field: attributes["ts"]
-      - type: move
-        from: attributes["body"]
-        to: body
-      # Add a service version, the template version
-      - type: add
-        field: resource["service.version"]
-        value: '1.0.0'
-      # Remove the hostname, use the resource detectors
-      - type: remove
-        field: attributes["hostname"]
-
-service:
-  pipelines: # This defines the order in which the collector runs its components.
-    logs:
-      receivers: [windowseventlog/application, filelog/mssql, filelog/messages]
-      processors: [batch, resourcedetection]
-      exporters: [otlphttp/centreon, debug]
-
-```
diff --git a/logmanagement/collector/collector.md b/logmanagement/collector/collector.md
index 825dc9df17e3..855e732c2a16 100644
--- a/logmanagement/collector/collector.md
+++ b/logmanagement/collector/collector.md
@@ -1,17 +1,19 @@
 ---
 id: collector
-title: Full collector configuration (multiple log sources)
+title: Manual collector configuration
 description: Configure an OpenTelemetry collector to collect multiple log sources from one host
 ---
 
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 
-[Simple collector configurations](opentelemetry-collector.md) provides a configuration file to set up log collection from a Windows machine. The procedure below is better suited to cases where multiple log types are collected on the same host (Windows or Linux).
+The [Generating an OTel collector configuration file](./collector-generator.md) page provides a simplified procedure covering certain data sources. If you cannot find the snippet you need in the list of available data sources, use the procedure below.
 
-> **Save time with Centreon templates**
+<!-- [Simple collector configurations](opentelemetry-collector.md) provides a configuration file to set up log collection from a Windows machine. The procedure below is better suited to cases where multiple log types are collected on the same host (Windows or Linux). -->
+
+<!-- > **Save time with Centreon templates**
 >
-> Centreon provides [ready-to-use configuration templates for the most common log sources](https://github.com/CentreonLabs/centreon-otel-col-log-template/tree/main). Use them as a starting point to quickly configure your collector.
+> Centreon provides [ready-to-use configuration templates for the most common log sources](https://github.com/CentreonLabs/centreon-otel-col-log-template/tree/main). Use them as a starting point to quickly configure your collector. -->
 
 If you run into any problems, refer to the [Troubleshooting](collector-troubleshooting.md) page.
 
diff --git a/logmanagement/dashboards.md b/logmanagement/dashboards.md
index 72b7b4992f60..85198cc1ea23 100644
--- a/logmanagement/dashboards.md
+++ b/logmanagement/dashboards.md
@@ -10,7 +10,7 @@ Dashboards are built using widgets. They allow you to display [text](#generic-te
 
 ## Creating a dashboard
 
-1. To create a dashboard, in the **Dashboards** page, click **Add**.
+1. To create a dashboard, on the **Dashboards** page, click **Add**.
 2. In the window that opens, enter a name (mandatory) and a description (optional), then click **Create**. A blank dashboard appears.
 
    ![image](./assets/dashboard_blank.png)
@@ -21,16 +21,16 @@ Dashboards are built using widgets. They allow you to display [text](#generic-te
 ## Adding a widget to a dashboard
 
 1. If you are not already in your dashboard, [edit it](#editing-a-dashboard).
-2. In the dashboard, click **Add a widget**: the screen displays the widget creation screen.
-2. Select a widget type: the rest of the screen is updated to display the settings for this type of widget.
-3. [Use the available settings to configure your widget](#available-widgets).
-4. When you have finished configuring your widget, click **Save** in the bottom right corner. This only saves the widget: make sure you also save your dashboard before you do anything else.
+2. In the dashboard, click **Add a widget** to display the widget creation screen.
+3. Select a widget type: the rest of the screen is updated to display the settings for this type of widget.
+4. [Use the available settings to configure your widget](#available-widgets).
+5. When you have finished configuring your widget, click **Save** in the bottom right corner. This only saves the widget: make sure you also save your dashboard before you do anything else.
 
 ## Editing a dashboard
 
-On the **Dashboards** page, click the name of the dashboard you want to edit. The dashboard opens; click **Edit dashboard** in the top-right corner to enter edit mode.
+On the **Dashboards** page, click the name of the dashboard you want to edit. The dashboard opens; click **Edit dashboard** in the top right corner to enter edit mode.
 
-Edit each widget you want, saving your changes to each widget. Then save the dashboard itself.
+Edit each widget you want to change, saving your changes as you go, then save the dashboard itself.
 
 ## Editing a widget
 
@@ -47,13 +47,13 @@ Use this widget to insert titles, information or links into your dashboards. Use
 
 ### Log viewer
 
-Use this widget to display the list of logs matching a specific query in the last n minutes. In the resulting table, click **Show in context** on the right to display the log in the **Log explorer** page, along with the previous and next 2 minutes of logs that match the query.
+Use this widget to display the list of logs matching a specific query in the last `n` minutes. In the resulting table, click **Show in context** on the right to display the log in the **Log explorer** page, along with the previous and next 2 minutes of logs that match the query.
 
 ![image](./assets/widget_log_viewer.png)
 
 ### Metrics graph
 
-Here, "metrics" means the number of log entries that match a specific query, or the ratio obtained by dividing a query by another query. The resulting number of logs can be broken down according to another parameter. In the example below, each bar represents the number of INFO and ERROR logs for a service for a given period.
+Here, "metrics" means the number of logs that match a specific query, or the ratio obtained by dividing a query by another query. The resulting number of logs can be broken down according to another parameter. In the example below, each bar represents the number of INFO and ERROR logs for a service for a given period.
 
 ![image](./assets/widget_metrics_chart.png)
 
@@ -61,12 +61,12 @@ Select the settings you want in the left part of the screen.
 
 * The type of widget (here, **Metrics graph**).
 * A title and a description. These will be displayed in the widget at all times.
-* Configure the aspect of the graph using the **Display settings** section.
+* The graph's appearance, using the **Display settings** section.
 * The time period you want the graph to cover.
 
 #### Dataset selection
 
-In the right part of the screen, define the data you want to display. The graph can display several data series.  Each series is defined by a dataset. A dataset has the following parameters:
+In the right part of the screen, define the data you want to display. The graph can display several data series. Each series is defined by a dataset. A dataset has the following parameters:
 
 * **Name**: this will be the name of the data series in the legend of the graph.
 <!-- * **Datasource**: **Centreon Log Management** means the graph will use [data sent to Centreon Log Management by your OpenTelemetry collectors](./collector/collector.md). -->
@@ -76,4 +76,4 @@ In the right part of the screen, define the data you want to display. The graph
   * **Count** means that the query will return the number of log entries that match the query.
   * **Ratio** means that you divide the results of a query by the results of another query.
   
-If you display the graph in **Line** mode, each dataset will produce a curve. If you display the chart as a **Bar** chart, each dataset will produce a bar. Inside each bar, the data will be stacked according to the **Group by** parameter.
+If you display the graph in **Line** mode, each dataset will produce a curve. If you display it in **Bar** mode, each dataset will produce a bar. Inside each bar, the data will be stacked according to the **Group by** parameter.
diff --git a/logmanagement/sidebarsLogmanagement.js b/logmanagement/sidebarsLogmanagement.js
index 4df737fe26a8..8de162850500 100644
--- a/logmanagement/sidebarsLogmanagement.js
+++ b/logmanagement/sidebarsLogmanagement.js
@@ -50,7 +50,7 @@ module.exports = {
         },
         {
           type: 'doc',
-          id: 'collector/collector-simple'
+          id: 'collector/collector-generator'
         },
         {
           type: 'doc',