diff --git a/docker/telemetry/grafana/provisioning/dashboards/dashboards.yaml b/docker/telemetry/grafana/provisioning/dashboards/dashboards.yaml
index 6aeaff31e6..dec8dc87c0 100644
--- a/docker/telemetry/grafana/provisioning/dashboards/dashboards.yaml
+++ b/docker/telemetry/grafana/provisioning/dashboards/dashboards.yaml
@@ -1,9 +1,9 @@
 apiVersion: 1
 
 providers:
-  - name: rippled-telemetry
+  - name: xrpld-telemetry
     orgId: 1
-    folder: rippled
+    folder: xrpld
     type: file
     disableDeletion: false
     editable: true
diff --git a/docs/telemetry-runbook.md b/docs/telemetry-runbook.md
index 1ff7c4a51b..1772e4bb43 100644
--- a/docs/telemetry-runbook.md
+++ b/docs/telemetry-runbook.md
@@ -241,12 +241,14 @@ Three dashboards are pre-provisioned in `docker/telemetry/grafana/dashboards/`:
 
 ## Troubleshooting
 
-### No traces appearing in Jaeger
+### No traces appearing in Tempo
 
 1. Check xrpld logs for `Telemetry starting` message
 2. Verify `enabled=1` in the `[telemetry]` config section
 3. Test collector connectivity: `curl -v http://localhost:4318/v1/traces`
-4. Check collector logs: `docker compose logs otel-collector`
+4. Check collector logs: `docker compose -f docker/telemetry/docker-compose.yml logs otel-collector`
+5. Verify Tempo is receiving data: open Grafana → Explore → select Tempo datasource → search by `service.name = xrpld`
+6. Check Tempo logs: `docker compose -f docker/telemetry/docker-compose.yml logs tempo`
 
 ### High memory usage