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:

VictoriaLogs Basics: What You Need to Know, with Examples & Visuals

Cluster mode in VictoriaLogs is not a separate build. It is the same victoria-logs binary started with different flags, so you can scale out without a migration step. Storage nodes persist data on disk, while gateway nodes can stay stateless by pointing to storage with -storageNode. It also ships with practical safety switches, like read-only protection when -storageDataPath runs low and optional partial results when a storage node is down.

What's New in VictoriaMetrics Cloud Q4 2025? New tiers, more deployment options, IaC and alerting rules.

In the last quarter of 2025, VictoriaMetrics Cloud brings many great features: New powerful Capacity Tiers, the expansion to the us-east-1 (N.Virginia) AWS region in the US, new Notification Groups, a Terraform provider to complete your IaC, 9 brand new Alerting Rule Integrations and much more.

Vibe coding tools observability with VictoriaMetrics Stack and OpenTelemetry

Learn how to add observability to Vibe Coding Tools using OpenTelemetry and the VictoriaMetrics Stack. This guide explains how to configure popular vibe coding tools to export their metrics telemetry and get insights about your vibe coding sessions.

How a US Software Provider Improved Traffic Alerting with VictoriaMetrics Anomaly Detection

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.