consistent versions

Signed-off-by: chrislai <[email protected]>

Author: chriswlai

docs/tutorials/agent_tracing/docker-compose.yml

@@ -1,7 +1,7 @@
 version: '3'
 services:
   opensearch-node1:
-    image: opensearchproject/opensearch:3.1.0
+    image: opensearchproject/opensearch:3.1.0 # NOTE: Ensure versions are consistent across all OpenSearch services (OpenSearch, Dashboards, plugins)
     container_name: opensearch-node1
     environment:
       - cluster.name=opensearch-cluster
@@ -33,7 +33,7 @@ services:
       bash -c "
       bin/opensearch-plugin remove opensearch-skills; 
       bin/opensearch-plugin remove opensearch-ml; 
-      bin/opensearch-plugin install --batch telemetry-otel --batch file:///usr/share/opensearch/<YOUR_NAME>/opensearch-ml-3.1.0.0-SNAPSHOT.zip; 
+      bin/opensearch-plugin install --batch telemetry-otel --batch file:///usr/share/opensearch/<YOUR_NAME>/opensearch-ml-3.1.0.0-SNAPSHOT.zip;
       OPENSEARCH_LOG4J_CONFIG_FILE=/usr/share/opensearch/config/telemetry-log4j2.xml ./opensearch-docker-entrypoint.sh opensearch"
     ports:
       - 9200:9200
@@ -46,7 +46,7 @@ services:
       - "localhost:172.17.0.1"  # This maps localhost to the Docker host IP
 
   opensearch-dashboards:
-    image: opensearchproject/opensearch-dashboards:3.1.0
+    image: opensearchproject/opensearch-dashboards:3.1.0 # Must match OpenSearch version
     container_name: opensearch-dashboards
     ports:
       - 5601:5601

docs/tutorials/agent_tracing/setup_agent_tracing_and_visualization.md

@@ -34,6 +34,9 @@ The [`docker-compose.yml`](docker-compose.yml) file orchestrates all the service
 **⚠️ Development Configuration**: The configuration files in this tutorial use `ssl: false` and basic authentication for development simplicity. For production use, you must configure proper TLS certificates and security settings.
 
 ### Key Points
+- **Version Consistency:**
+  - Ensure all OpenSearch services use the same version (e.g., 3.1.0 for OpenSearch, Dashboards, and plugins)
+  - Version mismatches can cause compatibility issues and unexpected behavior
 - **Volume Mounts:**
   - Data Prepper expects its configuration files to be mounted directly to `/usr/share/data-prepper/config/data-prepper-config.yaml` and `/usr/share/data-prepper/pipelines/pipelines.yaml` inside the container.
   - Incorrect mount paths (such as mounting into subdirectories) will cause Data Prepper to fail to start.