From ac6083f89117aa6fdc0f54667cf9a7844471f4db Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Sun, 28 Dec 2025 20:38:56 +0200 Subject: Replace screenshot placeholders with reference to X-RAG blog post MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Instead of including screenshot placeholders, reference the X-RAG Observability Hackathon blog post which already has Grafana Tempo screenshots showing: - Trace waterfall visualization - Service graph visualization This provides readers with visual examples of how distributed traces appear in Grafana UI without duplicating screenshots. Link: https://foo.zone/gemfeed/2025-12-24-x-rag-observability-hackathon.html 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 --- ...RAFT-f3s-kubernetes-with-freebsd-part-X-OBSERVABILITY2.gmi.tpl | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-X-OBSERVABILITY2.gmi.tpl b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-X-OBSERVABILITY2.gmi.tpl index db39430a..827edd39 100644 --- a/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-X-OBSERVABILITY2.gmi.tpl +++ b/gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-X-OBSERVABILITY2.gmi.tpl @@ -992,9 +992,9 @@ Or directly open the trace by pasting the trace ID in the search box: **5. Trace visualization:** -The trace waterfall view shows the complete request flow with timing: +The trace waterfall view in Grafana shows the complete request flow with timing. For screenshots of how distributed traces appear in the Grafana UI, see the X-RAG Observability Hackathon blog post which demonstrates similar trace visualization: -[SCREENSHOT PLACEHOLDER 1: Trace waterfall view showing Frontend → Middleware → Backend spans with timing (221ms total)] +=> https://foo.zone/gemfeed/2025-12-24-x-rag-observability-hackathon.html X-RAG Observability Hackathon (includes Grafana Tempo screenshots) The trace reveals the distributed request flow: * **Frontend (221ms)**: Receives GET /api/process, executes business logic, calls middleware @@ -1005,9 +1005,9 @@ The trace reveals the distributed request flow: **6. Service graph visualization:** -The service graph automatically generated from traces shows service dependencies: +The service graph is automatically generated from traces and shows service dependencies. For examples of service graph visualization in Grafana, see the screenshots in the X-RAG Observability Hackathon blog post. -[SCREENSHOT PLACEHOLDER 2: Service graph showing Frontend → Middleware → Backend with request rates and latencies] +=> https://foo.zone/gemfeed/2025-12-24-x-rag-observability-hackathon.html X-RAG Observability Hackathon (includes service graph screenshots) This visualization helps identify: * Request rates between services -- cgit v1.2.3