Package Exports
- qryn
- qryn/qryn.js
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (qryn) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
qryn.dev ☁️ qryn.cloud ❤️
... it's pronounced /ˈkwɪr..ɪŋ/ or just querying
🚀 qryn is a drop-in Grafana compatible polyglot observability framework
- Logs, Metrics and Traces living happily together. Drop-in compatible with multiple vendors formats.
- Native LogQL/PromQL/TempoQL APIs support for querying, processing, tracing and alerting [^2] in Grafana [^3]
- Ingestion APIs transparently compatible with Opentelemetry, Loki, Prometheus, InfluxDB, Elastic and more
- Dynamically search, filter and extract metrics from logs, events, spans and traces. NO SQL required.
- Ready to use with popular Agents such as Promtail, Grafana-Agent, Vector, Logstash, Telegraf and more
- Built in Explore UI and CLI for querying supported datasources
- Designed for edge (js/wasm) and core/backend deployments (go/rust).
- Total data control. Compatible with ClickHouse or InfluxDB IOx with S3 object storage.
🚀 qryn.cloud is the supercharged qryn version developed in go with additional functionality, speed and features!
🚀 Get Started
:octocat: Get qryn OSS up and running on-prem in no time using the Documentation or join our Matrix Room
☁️ Create a free account on qryn.cloud and go straight to production at any scale with polyglot confidence.
Supported Features
📚 OpenTelemetry
qryn fully supports opentelemetry and comes with a powerful otel-collector distribution supporting any log, trace or metric format and writing directly to ClickHouse qryn tables ready to be consumed through any query API.
📚 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
🎉 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
🎉 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
🎉 No plugins needed
↔️ Correlation
Data correlation made simple with dynamic links between logs, metrics and traces
👁️ 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
Contributions
Whether it's code, documentation or grammar, we ❤️ all contributions. Not sure where to get started?
- Join our Matrix Channel, and ask us any questions.
- Have a PR or idea? Request a session / code walkthrough with our team for guidance.
Contributors
License
©️ QXIP BV, released under the GNU Affero General Public License v3.0. See LICENSE for details.
[^1]: qryn is not affiliated or endorsed by Grafana Labs or ClickHouse Inc. All rights belong to their respective owners.
[^2]: qryn is a 100% clear-room api implementation and does not fork, use or derivate from Grafana Loki code or concepts.
[^3]: Grafana®, Loki™ and Tempo® are a Trademark of Raintank, Grafana Labs. ClickHouse® is a trademark of ClickHouse Inc. Prometheus is a trademark of The Linux Foundation.