Discarding gRPC-Go: The Story Behind OTLP/gRPC Support in VictoriaTraces
Why did VictoriaTraces build gRPC support without using gRPC-Go? And what are the benefits of adopting a simple HTTP/2 server and easyproto?
Why did VictoriaTraces build gRPC support without using gRPC-Go? And what are the benefits of adopting a simple HTTP/2 server and easyproto?
When it comes to observability, people often refer to its three pillars: metrics, tracing, and logging. At VictoriaMetrics, we already have solutions for metrics and logging. Throughout these years, we’ve heard a common question from the community: When will VictoriaTraces be released? If you are interested in this topic, then this blog post is for you. We’ll share the results of our research into distributed tracing and explore two key questions: Will there be a VictoriaTraces? And how competitive could it be?
OpenTelemetry, Prometheus 2.x, Prometheus 3.x, and vmagent are put together for comparison in scraping and pushing data to remote storage.
This blog post is the first in the series of the blog posts based on the talk about ‘How to reduce expenses on monitoring’, stackconf 2023. It is about open-source instruments and techniques from theVictoriaMetrics ecosystem for improving cost-efficiency of monitoring.
One of the latest benchmarks we made was ‘VictoriaMetrics: scaling to 100 million metrics per second’. While the fact of such scale for VictoriaMetrics is noteworthy on its own, the benchmark tool used to generate that load is usually overlooked. In this blog post I’ll explain in more details the challenge of running such benchmarks.
A Helm chart for pushing node_exporter metrics to Prometheus-compatible systems via remote_write protocol