Fix otel stack configuration and extend documentation.

docs/06-configuring-services.md

@@ -528,7 +528,7 @@ docker/sdk up
 
 By default, in the New Relic dashboard, the APM is displayed as `company-staging-newrelic-app`. To improve visibility, you may want to configure each application as a separate APM. For example, `YVES-DE (docker.dev)`.
 
-To do it, adjust the Monitoring service in `src/Pyz/Service/Monitoring/MonitoringDependencyProvider.php`:  
+To do it, adjust the Monitoring service in `src/Pyz/Service/Monitoring/MonitoringDependencyProvider.php`:
 
 ```php
 <?php declare(strict_types = 1);
@@ -655,3 +655,31 @@ tideways:
 docker/sdk boot deploy.*.yml &&\
 docker/sdk up
 ```
+
+## Local OpenTelemetry Stack
+
+The Local OpenTelemetry Stack is a powerful tool designed for real-time monitoring of Application Performance Monitoring (APM) locally. It allows you to track APM traces across all containers or specific ones running PHP applications.
+
+This stack integrates the following containers into your local environment:
+* tempo-init
+* tempo
+* collector
+* prometheus
+* grafana
+
+### Configuration
+
+1. Adjust your `deploy.*.yml` as follows:
+
+```yaml
+    grafana:
+        engine: otel-stack
+        endpoints:
+            grafana.spryker.local:
+```
+
+2. Bootstrap the docker setup and rebuild the application:
+```bash
+docker/sdk boot deploy.*.yml &&\
+docker/sdk up
+```

generator/src/templates/service/otel-stack/latest/otel-stack.yml.twig

@@ -52,7 +52,7 @@
   grafana:
       image: grafana/grafana:11.0.0
       volumes:
-          - ./${DEPLOYMENT_PATH}/context/grafana-datasources.yaml:/etc/grafana/provisioning/datasources/datasources.yaml
+          - ./${DEPLOYMENT_PATH}/context/otel-stack/grafana-datasources.yaml:/etc/grafana/provisioning/datasources/datasources.yaml
       networks:
           - public
           - private