Polyglot Matters: mimir vs qryn

Polyglot Matters: mimir vs qryn


3 min read

Grafana Mimir recently turned 1 year old so let's congratulate our friends at Grafana!

Different Strokes

Grafana offers its LGTM Stack (Loki for logs, Grafana for visualization, Tempo for traces, and Mimir for metrics) splitting everything into (very) different projects and forcing users to puzzle them back together.

On the other hand, our polyglot stack qryn does the opposite and rejoins those functions into one with 100% API compatibility in Grafana and a solid variety of ingestion formats and query standards into a thin and fast overlay operating as a powerful and flexible traspilier on top of OLAP databases and Cloud Storage.

๐Ÿฅณ In their celebratory post, Grafana involuntarily makes a great case for the polyglot features native in qryn - born and designed to be "transparently different" ๐Ÿฅณ

#1: No Need for Proxies

Grafana: When we launched Mimir, we focused on natively consuming Prometheus metrics. But within four months, we open-sourced three write proxies to ingest metrics for Datadog, InfluxDB, and Graphite. OpenTelemetry

A workflow diagram shows how Prometheus metrics are sent to Mimir.

TLDR; To simply ingest InfluxDB, Datadog, Opentelemetry... you need more software!

๐Ÿš€ qryn to the rescue!

Unlike Mimir, qryn is designed to be polygot and natively ingests metrics formats from Prometheus, InfluxDB, Datadog, Elastic, Open Telemetry and many others.

If that's not enough the qryn-otel-collector offers hundreds of additional formats.

And since qryn is compatible with Prometheus, you can still use the Grafana Proxies if you want to compare methods and performance. Freedom of choice is the game.

#2: Out of Order Inserts

Grafana: With the release of Grafana Mimir 2.2 came experimental support to accept out-of-order samples. With out-of-order support, Grafana Mimir can accept time series data from any metrics system that requires old samples to be ingested. This makes Grafana Mimir a general purpose TSDB,...

๐Ÿš€ qryn is your delorean!

Unlike Mimir, qryn was designed to support out-of-order inserts in ClickHouse out the box (including JS/Edge version) for all your Metrics, Logs and Telemetry traces.

This makes ClickHouse + qryn a genuine alternative to any general-purpose TSDB!

#3: Less is More

Mimir only gets your metrics covered. If you want logs, you need Loki. If you need telemetry, you need Tempo. Each with its config, versions and various quirks.

qryn and qryn.cloud get you everything at once, allowing users to ingest Logs, Metrics and Traces with end-to-end visibility using qryn's polyglot API using data from Loki, Prometheus, Opentelemetry, InfluxDB, Elastic and many more powered by ClickHouse performance - without requiring any new language, formats, or proxies.

Let's Get Polyglot!

Give qryn a try today with a free trial at qryn.cloud โค๏ธ

Did you find this article valuable?

Support qryn by becoming a sponsor. Any amount is appreciated!