rewritten last resillence exercise

Author: hagen-p

content/en/ninja-workshops/10-advanced-otel/4-building-resilience/4-4-recovery.md

@@ -20,11 +20,33 @@ In this exercise, we’ll test how the **OpenTelemetry Collector** recovers from
 ../otelbin --config=gateway.yaml
 ```
 
-**Inspect the Agent logs**: Once the **Gateway** is up and running the **Agent** will resume sending data from the last checkpointed state, ensuring no data is lost. You should see the **Gateway** begin receiving the previously missed traces without requiring any additional action on your part.
-
 {{% /notice %}}
-{{% notice title="Tip" style="primary" icon="lightbulb" %}}
-Note that only the **Gateway** will show that the checkpointed traces have arrived. The agent will not display any indication that data new or old has been sent.
+
+After the **Agent** is up and running, the **File_Storage** extension will detect buffered data in the checkpoint folder.  
+It will start to dequeue the stored spans from the last checkpoint folder, ensuring no data is lost.
+
+{{% notice title="Exercise" style="green" icon="running" %}}
+
+**Verify the Agent Debug output**  
+Note that the Agent Debug Screen does **NOT** change and still shows the following line indicating no new data is being exported.
+  
+  ```text
+  2025-02-07T13:40:12.195+0100    info    [email protected]/service.go:253 Everything is ready. Begin running and processing data.
+  ```
+
+**Watch the Gateway Debug output**  
+You should see from the **Gateway** debug screen, it has started receiving the previously missed traces without requiring any additional action on your part.  
+
+  ```txt
+  2025-02-07T12:44:32.651+0100    info    [email protected]/service.go:253 Everything is ready. Begin running and processing data.
+  2025-02-07T12:47:46.721+0100    info    Traces  {"kind": "exporter", "data_type": "traces", "name": "debug", "resource spans": 4, "spans": 4}
+  2025-02-07T12:47:46.721+0100    info    ResourceSpans #0
+  Resource SchemaURL: https://opentelemetry.io/schemas/1.6.1
+  Resource attributes:
+  ```
+
+**Check the `gateway-traces.out` file**  
+Count the number of traces in the recreated `./gateway-traces.out`. It should match the number you send when the **Gateway** was down
 {{% /notice %}}
 
 ### Conclusion
@@ -33,6 +55,4 @@ This exercise demonstrated how to enhance the resilience of the OpenTelemetry Co
 
 By implementing file-based checkpointing and queue persistence, you ensure the telemetry pipeline can gracefully recover from temporary interruptions, making it a more robust and reliable for production environments.
 
-If you want to know more about the `FileStorage` extension, you can find it [**here**](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/storage/filestorage).
-
 Stop the **Agent** and **Gateway** using `Ctrl-C`.