spellings and first steps of test resilience

Author: hagen-p

content/en/ninja-workshops/10-advanced-otel/30-filelog/1-agent-filelog.md

@@ -4,7 +4,7 @@ linkTitle: 3.1 Agent Filelog Config
 weight: 1
 ---
 
-### Upate the agent configuration
+### Update the agent configuration
 
 Check that you are in the `[WORKSHOP]/3-filelog` folder.  Open the `agent.yaml` copied across earlier and in your editor and add the `filelog` receiver to the `agent.yaml`.
 

content/en/ninja-workshops/10-advanced-otel/40-resillience/1-test-resilience.md

@@ -3,16 +3,35 @@ title: Test your Resilience Setup
 linkTitle: 4.1 Testing the Setup
 weight: 1
 ---
-3. **Run the Collector:**
-   Now, run the OpenTelemetry Collector using the configuration file you just created. You can do this by executing the following command in your terminal:
+
+### Step 1: Setup Test environment
+
+In this section we are going to  simulate an out age on the network and see if our configuration  helps the Collector recover from that issue:
+
+1. **Run the Gateway**
+   Now, run the OpenTelemetry Collector using the existing gateway configuration file. You can do this by executing the following command in your terminal:
 
    ```bash
-   otelcol --config agent.yaml
+   ../otelcol --config gateway.yaml
    ```
 
-   This will start the collector with the configurations specified in the YAML file.
+2. **Run the Agent**
+   Next, run the OpenTelemetry Collector using the configuration file you just created. You can do this by executing the following command in your terminal:
+
+   ```bash
+   ../otelcol --config agent.yaml
+   ```
+
+   This will start the collector with the resilience configurations specified in the YAML file.
+
+3. **Run the log-gen script**
+To generate traffic, we going to start our Log generating script:  
+
+   ```bash
+   ./log-gen.sh 
+   ```
 
-### Step 4: Testing the Resilience
+### Step 2: Testing the Resilience
 
 To test the resilience built into the system:
 
@@ -28,43 +47,8 @@ To test the resilience built into the system:
 4. **Inspect Logs and Files:**
    Inspect the logs to see the retry attempts. The `debug` exporter will output detailed logs, which should show retry attempts and any failures.
 
-### Step 5: Fine-Tuning the Configuration for Production
-
-- **Timeouts and Interval Adjustments:**
-   You may want to adjust the `retry_on_failure` parameters for different network environments. In high-latency environments, increasing the `max_interval` might reduce unnecessary retries.
-
-   ```yaml
-   retry_on_failure:
-     enabled: true
-     initial_interval: 1s
-     max_interval: 5s
-     max_elapsed_time: 20s
-   ```
-
-- **Compaction and Transaction Size:**
-   Depending on your use case, adjust the `max_transaction_size` for checkpoint compaction. A smaller transaction size will make checkpoint files more frequent but smaller, while a larger size might reduce disk I/O but require more memory.
-
-### Step 6: Monitoring and Maintenance
-
-- **Monitoring the Collector:**
-   Use Prometheus or other monitoring tools to collect metrics from the OpenTelemetry Collector. You can monitor retries, the state of the sending queue, and other performance metrics to ensure the collector is behaving as expected.
-
-- **Log Rotation:**
-   The `file` exporter has a built-in log rotation mechanism to ensure that logs do not fill up your disk.
-
-   ```yaml
-   exporters:
-     file:
-       path: ./agent.out
-       rotation:
-         max_megabytes: 2
-         max_backups: 2
-   ```
-
-   This configuration rotates the log file when it reaches 2 MB, and keeps up to two backups.
-
 ### Conclusion
 
 In this section, you learned how to enhance the resilience of the OpenTelemetry Collector by configuring the `file_storage/checkpoint` extension, setting up retry mechanisms for the OTLP exporter, and using a sending queue backed by file storage for storing data during temporary failures.
 
-By leveraging file storage for checkpointing and queue persistence, you can ensure that your telemetry pipeline can recover gracefully from failures, making it more reliable for production environments.
+By leveraging file storage for checkpointing and queue persistence, you can ensure that your telemetry pipeline can recover gracefully from failures, making it more reliable for  short interruptions for production environments.