diff options
| -rw-r--r-- | gemfeed/DRAFT-f3s-kubernetes-with-freebsd-part-X-OBSERVABILITY2.gmi.tpl | 8 |
1 files changed, 6 insertions, 2 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 827edd39..66631955 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,13 @@ Or directly open the trace by pasting the trace ID in the search box: **5. Trace visualization:** -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: +The trace waterfall view in Grafana shows the complete request flow with timing: -=> https://foo.zone/gemfeed/2025-12-24-x-rag-observability-hackathon.html X-RAG Observability Hackathon (includes Grafana Tempo screenshots) +=> ./f3s-observability-tempo/grafana-tempo-trace.png Distributed trace visualization in Grafana Tempo showing Frontend → Middleware → Backend spans + +For additional examples of Tempo trace visualization, see also: + +=> https://foo.zone/gemfeed/2025-12-24-x-rag-observability-hackathon.html X-RAG Observability Hackathon (more Grafana Tempo screenshots) The trace reveals the distributed request flow: * **Frontend (221ms)**: Receives GET /api/process, executes business logic, calls middleware |