- Blog /
- Releasing Graphite Query Language in Open Source VictoriaMetrics

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.
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.
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.
VictoriaMetrics Anomaly Detection enables reliable alerting for highly variable, multi-domain traffic without relying on static thresholds. In this case study, fine-tuned models, backtesting, and clear visualization helped reduce alert noise, improve confidence in anomaly detection, and lower operational overhead.
In 2025, VictoriaMetrics deepened its commitment to open source, community, and developer experience across the global cloud-native ecosystem. This year-in-review reflects on key observability themes, global engagement, OpenTelemetry contributions, and the people and conversations that shaped the year.
Spotify needed to replace its legacy in-house time series database to overcome stability and performance limitations, which would bring about query delays and timeouts. The Spotify observability team chose VictoriaMetrics to support efficient metric ingestion, querying, and alerting at scale.
Becoming a Red Hat OpenShift Certified Operator brings portability and scalability benefits on the leading enterprise Kubernetes platform.