Questions¶
Open¶
- Does VictoriaTraces require a completely separate VictoriaLogs cluster, or can it share the same storage nodes as the main VictoriaLogs cluster? — observability/victoriametrics/architecture
- How does LogsQL compare to LogQL (Loki) in terms of performance on large cardinality? — future comparison note
- How does VictoriaMetrics' downsampling (Enterprise) compare to Mimir's compactor? What data fidelity is lost? — observability/victoriametrics/benchmarks
- What are the production gotchas of running VictoriaLogs in cluster mode vs single-node for >1 TB/day logs? — observability/victoriametrics/operations
- How does vmagent's performance compare to Grafana Alloy for OTel-native telemetry pipelines? — observability/victoriametrics/benchmarks
- What is the actual trace search performance of VictoriaTraces vs Tempo at 100M+ spans/day? — observability/victoriametrics/benchmarks
- How does VictoriaMetrics anomaly detection (vmanomaly) work, and is it production-ready? — observability/victoriametrics/how-it-works
- What is the migration path from Elasticsearch to VictoriaLogs for existing log pipelines? — observability/victoriametrics/operations
- How does VictoriaMetrics Cloud pricing compare to Grafana Cloud at equivalent scale? — observability/victoriametrics/benchmarks
- Can vmauth replace NGINX Ingress as the sole entry point for the Victoria Stack on Kubernetes? — observability/victoriametrics/architecture
Answered¶
- Do they share a unified backend? — No, they are separate databases, though VictoriaTraces runs on top of VictoriaLogs storage engine, resolved in observability/victoriametrics/architecture
- What license is used? — Apache 2.0 for all core components; Enterprise features require paid license, resolved in observability/victoriametrics/index
- Is VictoriaMetrics a drop-in Prometheus replacement? — Yes, 100% PromQL compatible via MetricsQL superset; accepts remote_write natively, resolved in observability/victoriametrics/how-it-works
- Why is VictoriaMetrics more memory-efficient than Prometheus? — Custom LSM-Tree storage, ZSTD compression, and
-memory.allowedPercentenforcement preventing OOM, resolved in observability/victoriametrics/how-it-works - How do companies use it at scale? — Roblox (billions of series), Spotify (replaced Heroic), CERN (CMS detector), Grammarly (10x cost reduction), DreamHost (76M series), resolved in observability/victoriametrics/index