qryn

... it's pronounced /ˈkwɪr..ɪŋ/ or just querying

:rocket: qryn is a polyglot observability framework built on top of ClickHouse

• All your Logs, Metrics and Traces. Compatible with multiple standards, with native correlation, shared labels
• Ingestion and PUSH APIs transparently compatible with LogQL, PromQL, InfluxDB, Elastic and more
• Native Grafana ^3 and LogQL APIs for querying, processing, ingesting, tracing and alerting ^2
• Powerful pipeline to dynamically search, filter and extract data from logs, events, traces and beyond
• Ready to use with Agents such as Promtail, Grafana-Agent, Vector, Logstash, Telegraf and many others
• Built in Explore UI and CLI for querying and extracting data
• Cloud native, object storage friendly, stateless and compact.

🚀 Get Started

:octocat: Get qryn up and running in no time using our Documentation or join our Matrix Room

Supported Features

📚 LogQL

qryn implements a complete LogQL API to provide transparent compatibility with Loki clients
The Grafana Loki datasource can be used to natively browse and query logs and display extracted timeseries


:tada: No plugins needed

📈 Prometheus

qryn implements a complete Prometheus API to provide transparent compatibility with Prometheus clients
The Grafana Prometheus datasource can be used to natively browse and query metrics and display extracted timeseries


:tada: No plugins needed

🕛 Tempo

qryn implements the Tempo API to provide transparent compatibility with Tempo/OTLP clients.
The Tempo datasource can be used to natively query traces including beta search and service graphs


:tada: No plugins needed

↔️ Correlation

Data correlation made simple with dynamic links between logs, metrics and traces

:eye: View

No Grafana? No Problem. qryn ships with view - it's own lightweight data exploration tool

---

📚 Follow our team behind the scenes on the qryn blog

---

Contributors

    

License

©️ QXIP BV, released under the GNU Affero General Public License v3.0. See LICENSE for details.
We encourage forking and changing the code, hacking around with it, and experimenting. If you modify the qryn source code, and run that modified code in a way that's accessible over a network, you must make your modifications to the source code available following the guidelines of the license:

[I]f you modify the Program, your modified version must prominently offer all users interacting with it remotely 
through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding 
Source of your version by providing access to the Corresponding Source from a network server at no charge, through 
some standard or customary means of facilitating copying of software.