guides · what the telemetry you already send can tell you
Architecture and observability from OpenTelemetry, explained.
Each guide explains one job: what the telemetry has to carry, what you get back, and where Ritele does it for you. Nothing here needs Ritele to make sense, but every claim about it is true of the current release.
- guide · architecture diagram · OpenTelemetry
OpenTelemetry architecture diagram from traces
Generate a live system architecture diagram — services, databases, queues, caches, external APIs — from the OpenTelemetry traces you already send.
Read the guide → - guide · self-hosted observability · OpenTelemetry
Self-hosted OpenTelemetry observability
Self-hosted OpenTelemetry observability in one container: a bundled Collector, storage on your own disk, and nothing leaving unless you turn it on.
Read the guide → - guide · critical path · distributed tracing
Critical path analysis from distributed traces
How critical path analysis finds the steps a request waits on in a distributed trace, and why self time, not total time, shows which hop to speed up.
Read the guide → - guide · architecture drift · intended architecture
Architecture drift against an intended model
Detect architecture drift: compare an intended model from Structurizr, Mermaid or CSV with the dependencies OpenTelemetry traces show are running.
Read the guide → - comparison · Jaeger · Grafana · architecture
Ritele, Jaeger and Grafana: what each is for
How Ritele compares with Jaeger, Grafana Tempo and Loki, and with diagrams as code: what each does, where they overlap, and how to run them together.
Read the guide →