Skip to content 
About VictoriaTraces
VictoriaTraces is a distributed tracing backend developed by VictoriaMetrics as part of their comprehensive observability ecosystem. It provides high-scale trace data ingestion and storage with native OpenTelemetry support. VictoriaTraces integrates seamlessly with the VictoriaMetrics stack (VictoriaMetrics for metrics and VictoriaLogs for logs) and offers flexible visualization options through both Grafana and Jaeger UI. Built with the same performance and cost-efficiency principles as other VictoriaMetrics products, it provides trace-based alerting capabilities and supports both single-node and cluster deployments for scalability.
GreptimeDB vs. VictoriaTraces
| Feature/Aspect | GreptimeDB | VictoriaTraces |
|---|---|---|
| Data Model | Unified Observability Database | Distributed Tracing Backend |
| Value Model | Multi-Value (supports complex data structures) | Trace spans with attributes |
| Multi-model Support | Metrics, Logs & Traces in one database | Traces only (requires VictoriaMetrics and VictoriaLogs for full observability) |
| Query Languages | SQL & PromQL (dual interface) | TraceQL-compatible queries |
| Ingestion Protocols | SQL gRPC InfluxDB Line Protocol Prometheus Remote Storage OpenTelemetry Jaeger Loki Push API Elasticsearch Bulk API HTTP API | OpenTelemetry Protocol (OTLP) Jaeger Zipkin |
| Data Retention | Flexible TTL policies with tiered storage | Configurable retention with automatic cleanup |
| Continuous Aggregation | Built-in SQL aggregation, Pipeline ETL engine & Flow streaming computation | Trace-based metrics and service graphs |
| Deployment Complexity | Single system deployment | Single-node or cluster deployment with optional multi-tenancy |
| Use Cases | Unified observability, real-time analytics, IoT monitoring, edge computing | Distributed tracing, request flow analysis, latency troubleshooting, trace-based alerting |
| Architecture | Cloud-native distributed with compute-storage separation | Cluster architecture with distributed components |
| Storage Format | Apache Parquet (columnar, compressed) | Optimized trace storage format |
| Storage Scalability | Object storage integration with unlimited capacity | Scalable storage with cluster deployment support |
| High Availability | Native clustering with automatic failover | Cluster mode with replication support |
| License | Apache 2.0 | Apache 2.0 |
| Written Language | Rust (memory safety, performance) | Go (ecosystem compatibility) |
| Deployment Options | Single-node, cluster, Kubernetes-native, edge-to-cloud with unified API | Single-node, cluster with Kubernetes via Helm charts |
| Operational Complexity | Single unified system with simplified Kubernetes operations | Part of VictoriaMetrics ecosystem (requires VictoriaMetrics and VictoriaLogs for full stack) |
| Visualization | Grafana, Jaeger UI, custom dashboards via SQL | Grafana and Jaeger UI support |
| Alerting | Unified alerting across metrics, logs, and traces | Trace-based alerting via vmalert |
Join our community
Get the latest updates and discuss with other users.