Trace your distributed requests, in France
An affordable and scalable distributed tracing backend powered by Grafana Tempo, installed and maintained by DINAO. Visualize the journey of each request through your microservices, on French infrastructure.
Was ist 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 of your applications, i.e., the complete journey of a request through the multiple services of a distributed or microservices architecture.
The great strength of Tempo 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 retaining huge 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.
Hosten Sie Grafana Tempo bei DINAO
Ressourcenstufen kompatibel mit den Anforderungen von Grafana Tempo (min. 1 vCPU / 512 Mo / 5 Go). In Frankreich gehostet, vollständig gemanagt.
- 1 dedizierte vCPUs
- 2 Go RAM
- 20 GB NVMe
- Tägliche Backups
- Gemanagt & überwacht von DINAO
- 2 dedizierte vCPUs
- 4 Go RAM
- 40 GB NVMe
- Tägliche Backups
- Gemanagt & überwacht von DINAO
- 4 dedizierte vCPUs
- 8 Go RAM
- 80 GB NVMe
- Tägliche Backups
- Gemanagt & überwacht von DINAO
- 8 dedizierte vCPUs
- 16 Go RAM
- 160 GB NVMe
- Tägliche Backups
- Gemanagt & überwacht von DINAO
Technische Details
Sie fragen sich…
What is distributed tracing?
Distributed tracing follows the journey of a request through all the services it passes through (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). You can thus 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 infrastructure in France. Your observability data remains on French territory, in compliance with DSGVO.
