Releasing Graphite Query Language in Open Source VictoriaMetrics

Releasing Graphite Query Language in Open Source VictoriaMetrics

Share: Share on LinkedIn Share on X (Twitter)

As many of our users and the wider monitoring community will know, Graphite Query Language is a query language for Graphite monitoring tools, which helps analyze data stored in it.

Graphite is a well-known and respected pioneer in the monitoring space, which has seen a number of next generation monitoring solutions enter the scene … such as ourselves. It’s been used by a wide range of companies, which started using monitoring tools more than a decade ago. These companies include Etsy, Salesforce, Reddit, GitHub and Booking.com to name but a few; Booking.com probably being one of the largest implementations and users of Graphite.

Historically, VictoriaMetrics included support for data ingestion in Graphite protocol as well as support for the following Graphite querying APIs, which are needed for Graphite datasource in Grafana:

Our powerful query language for VictoriaMetrics components, MetricsQL, also includes features such as Graphite-compatible filters that can be passed via {__graphite__="foo.*.bar"} syntax.

What are we announcing?

#

Whereas Graphite Query Language has been a feature in VictoriaMetrics Enterprise (compatible with Graphite render API) thus far, we have decided to release it in open source VictoriaMetrics starting with VictoriaMetrics v1.90 - in other words, we’re open sourcing Graphite Query Language in VictoriaMetrics.

Why are we making this announcement?

#

We’ve been seeing high user demand in the VictoriaMetrics community and want to help our users migrate to modern monitoring solutions seamlessly. With the Graphite Query Language in open source VictoriaMetrics, engineers can switch the storage and get all benefits of using open source VictoriaMetrics while retaining the graphite protocol for data ingestion and querying time series.

This significantly helps with migration as VictoriaMetrics becomes a drop-in replacement for Graphite.

How to get started!

To get started with VictoriaMetrics, please visit our Quick Start page and Graphite API usage.

Leave a comment below or Contact Us if you have any questions!
comments powered by Disqus

You might also like:

VictoriaMetrics at KubeCon: Optimizing Tail Sampling in OpenTelemetry with Retroactive Sampling

If you’ve been struggling with the high resource overhead of tail sampling, check out retroactive sampling, an approach that significantly reduces sampling overhead for distributed tracing in OpenTelemetry.

VictoriaMetrics March 2026 Ecosystem Updates

March 2026 VictoriaMetrics Stack releases deliver Grafana Cardinality Explorer, VMUI pagination, JWT auth enhancements, log UI sidebar, and Kubernetes log enrichment for scalable observability. Upgrade now for better UI usability, query performance, and production-ready monitoring workflows.

Observability Lessons From OpenAI

OpenAI applies observability to autonomous AI agents using the VictoriaMetrics Stack and OpenTelemetry. Learn to build your own local setup with metrics, logs, and traces that help LLMs test, benchmark, and iterate autonomously.

Benchmarking Kubernetes Log Collectors: vlagent, Vector, Fluent Bit, OpenTelemetry Collector, and more

We benchmarked vlagent, Vector, Fluent Bit, Filebeat, Fluentd, Promtail, Grafana Alloy, and OpenTelemetry Collector on throughput, resource usage, and delivery correctness - and found correctness issues that most benchmarks overlook.