docs(website): update DMQ configuration file in aggregator setup guide

Author: jpraynaud

docs/website/root/manual/operate/run-aggregator-node.md

@@ -60,7 +60,6 @@ Note that this guide works only on a Linux machine.
 - Operate a **Cardano full node**
 
 - To access the file system of the **Cardano full node**, you will need the following permissions:
-
   - Read rights on the `Database` folder (specified by the `--database-path` setting of the **Cardano node**)
   - Read and write rights on the `Inter Process Communication` file (typically defined by the `CARDANO_NODE_SOCKET_PATH` environment variable used to launch the **Cardano node**)
 
@@ -278,7 +277,6 @@ The configuration values for the `/opt/mithril/mithril-aggregator.env` file are
   - `SIGNER_IMPORTER_RUN_INTERVAL`: Time interval at which the pools names and ticker in blockfrost will be imported (in minutes, default: `720`).
 
 - The **Cardano database** configuration values are (only needed if supporting Cardano database certification):
-
   - `DB_DIRECTORY`: Directory of the Cardano node database stores (same as the `--database-path` setting of the Cardano node)
   - `DATA_STORES_DIRECTORY`: Directory where the aggregator will store its databases (eg, `/opt/mithril/stores`)
   - `GOOGLE_APPLICATION_CREDENTIALS_JSON`: JSON content of the GCP service account credentials (required if using GCP for snapshot storage)
@@ -302,7 +300,6 @@ The configuration values for the `/opt/mithril/mithril-aggregator.env` file are
 Here is an **example** set of values for **release-preprod** that will be used in this guide in the **tip** boxes to illustrate some commands:
 
 - **Base configuration**:
-
   - **SIGNED_ENTITY_TYPES**: `MithrilStakeDistribution,CardanoStakeDistribution,CardanoTransactions` (only supporting stake distributions and transactions, excluding database snapshots)
   - **SERVER_PORT**: `8080`
   - **PUBLIC_SERVER_URL**: `https://aggregator.example.com/aggregator`
@@ -326,7 +323,6 @@ Here is an **example** set of values for **release-preprod** that will be used i
   - **SIGNER_IMPORTER_RUN_INTERVAL**: 720
 
 - **Cardano database configuration**:
-
   - **DB_DIRECTORY**: `/cardano/db`
   - **DATA_STORES_DIRECTORY**: `/opt/mithril/stores`
   - **GOOGLE_APPLICATION_CREDENTIALS_JSON**: `**YOUR_SECRET**`
@@ -1022,9 +1018,12 @@ bash -c 'cat > /opt/dmq/config.json << EOF
   "SigSubmissionLogicTracer": true,
   "SigSubmissionClientTracer": true,
   "SigSubmissionServerTracer": true,
+  "SigSubmissionClientProtocolTracer": true,
+  "SigSubmissionServerProtocolTracer": true,
   "MuxTracer": true,
-  "ChannelTracer": true,
+  "ChannelTracer": false,
   "DebugPeerSelectionTracer": true,
+  "ValidationTracer": true
 }
 EOF'
 ```
@@ -1050,9 +1049,12 @@ bash -c 'cat > /opt/dmq/config.json << EOF
   "SigSubmissionLogicTracer": true,
   "SigSubmissionClientTracer": true,
   "SigSubmissionServerTracer": true,
+  "SigSubmissionClientProtocolTracer": true,
+  "SigSubmissionServerProtocolTracer": true,
   "MuxTracer": true,
-  "ChannelTracer": true,
+  "ChannelTracer": false,
   "DebugPeerSelectionTracer": true,
+  "ValidationTracer": true
 }
 EOF'
 ```
@@ -1288,7 +1290,6 @@ If you want to make your follower aggregator publicly discoverable, you should:
 1. **Ensure your aggregator is accessible via HTTPS** by setting up Traefik or another reverse proxy with a valid SSL certificate (as described in the [Set up the SSL certificate](#setup-the-ssl-certificate-traefik) section).
 
 2. **Register your aggregator in the networks configuration**. You can do this by:
-
    - Opening an issue in the [Mithril GitHub repository](https://github.com/input-output-hk/mithril/issues)
    - Or by creating a pull request that modifies the [`networks.json`](https://github.com/input-output-hk/mithril/blob/main/networks.json) file and updates the `aggregators` field in the Cardano network you are targeting.