1. Blog
    2. /
  2. Releasing Graphite Query Language in Open Source VictoriaMetrics
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:

Upcoming Conferences & Meetups: Where to Meet Our Team

We love connecting with our community in person, and the next few months are packed with opportunities to do just that. Our team will be attending (and in some cases, speaking at) several conferences and meetups. If you’re planning to be there, we’d love to meet you—here’s where you can find us.

VictoriaMetrics Long-Term Support (LTS): H2 2025 Update

As we’re half-way through the year, we’d like to take this opportunity to provide an update on the most recent changes in our Long-Term Support (LTS) releases.

Creating a Sustainable Open Source Business Model - Introduction

Open source defies everything you’ve ever heard or learned about business before. This blog post is an introduction to how we’re creating a sustainable business model rooted in open source.

Full-Stack Observability with VictoriaMetrics in the OTel Demo

The OpenTelemetry Astronomy Shop demo has long served as a reference environment for exploring observability in distributed systems, but until now it shipped with only a Prometheus datasource. VictoriaMetrics forked the demo and extended it with VictoriaMetrics, VictoriaLogs, and VictoriaTraces, providing insights into VictoriaMetrics’ observability stack where metrics, logs, and traces flow into a unified backend.