Trace your distributed requests, in France
🔒 VPS onlyAn affordable and scalable distributed tracing backend powered by Grafana Tempo, installed and maintained by DINAO. Visualize the path of each request across your microservices, on a French infrastructure.
What is Grafana Tempo?
Grafana Tempo is an open-source, high-volume, and cost-effective distributed tracing backend developed by Grafana Labs. It allows you to collect, store, and explore traces from your applications, i.e., the complete path of a request across multiple services in a distributed or microservices architecture.
Tempo's key strength lies in its cost model: unlike solutions that index all data, Tempo only indexes the trace ID and stores the rest on cheap object storage (S3-compatible). This allows you to retain massive volumes of traces at a controlled cost while remaining highly scalable.
Tempo is compatible with major instrumentation standards — OpenTelemetry, Jaeger, Zipkin, and OpenCensus — and integrates natively with Grafana for trace exploration using its TraceQL query language. Coupled with Loki (logs) and Prometheus (metrics), it completes Grafana's observability stack, providing the essential logs / metrics / traces correlation for diagnosing complex systems.
Host Grafana Tempo at DINAO
Resource tiers compatible with Grafana Tempo prerequisites (minimum 1 vCPU / 512 Mo / 5 Go). Hosted in France, fully managed.
Application available on a dedicated VPS
This application requires privileged access to the host machine, incompatible with managed shared hosting. It is installed on a dedicated VPS server where you keep full control — managed by DINAO.
Technical reason: bind-mount d'un chemin hôte (volumes nommés uniquement en managé).
Discover the Docker VPS →Requirements for Grafana Tempo: 1 vCPU, 512 Mo, 5 Go. Our Docker VPS at €11 excl. VAT per month covers them.
Technical details
You might be wondering…
What is distributed tracing?
Distributed tracing follows the path of a request through all the services it traverses (frontend, API, database, message queues…). Each trace reveals latencies and bottlenecks, essential for diagnosing a microservices architecture.
Why is Tempo cost-effective?
Tempo only indexes the trace ID and stores the rest on cheap object storage (S3-compatible). This allows you to retain very large volumes of traces without the cost of solutions that index everything.
Does my existing instrumentation work?
Yes. Tempo is compatible with major standards: OpenTelemetry, Jaeger, Zipkin, and OpenCensus. You connect your current instrumentation without rewriting everything.
How are traces visualized?
Traces are explored directly in Grafana, with possible correlation to your logs (Loki) and metrics (Prometheus). DINAO can connect Tempo to your Grafana instance.
Where are my traces stored?
On DINAO's French infrastructure. Your observability data remains on French territory, in compliance with GDPR.
