formerly known as qryn
🚀 Gigapipe is a lighweight, multi-standard, polyglot observability stack for Logs, Metrics, Traces and Profiling
- Polyglot: All-in-one, drop-in compatible with Loki, Prometheus, Tempo, Pyroscope
- Lightweight: Powered by Bun - the fast, all-in-one JavaScript runtime + ClickHouse OLAP Engine
- Familiar: Use stable & popular LogQL, PromQL, TempoQL languages to query and visualize data
- Voracious: Ingest using OpenTelemetry, Loki, Prometheus, Tempo, Influx, Datadog, Elastic + more
- Versatile: Explore data with qryn's built-in Explorer and CLI or native Grafana datasource compatibility
- Secure: Retain total control of data, using ClickHouse, DuckDB or InfluxDB IOx with S3 object storage
- Independent: Open source, community powered, anti lock-in alternative to vendor controlled stacks
💡 gigapipe independently implements popular observability standards, protocols and query languages
- Setup & Deploy gigapipe opensource using the documentation and get help in our Matrix room
- Looking for a quick test before installing? Signup for a free trial at gigapipe.com
⚡ gigapipe is officially integrated with OpenTelemetry supports any log, trace or metric format
Ingested data can be queried using any of the available gigapipe APIs (LogQL, PromQL, TraceQL)
💡 No modifications required to your OpenTelemetry instrumentation!
gigapipe supports native ingestion for Loki, Prometheus, Tempo/Zipkin, Pyroscope and many other protocols
With gigapipe integrators can push and read data using any desired combination of APIs and formats
💡 No opentelemetry or any other middlewayre/proxy required!
Any Loki compatible client or application can be used with gigapipe out of the box
⚡ gigapipe implements the Loki API for transparent compatibility with LogQL clients
The Grafana Loki datasource can be used to natively browse and query logs and display extracted timeseries
🎉 No plugins needed
👁️ No Grafana? No problem! Use View
Any Prometheus compatible client or application can be used with gigapipe out of the box
⚡ gigapipe implements the Prometheus API for transparent PromQL compatibility using WASM 🏆
The Grafana Prometheus datasource can be used to natively to query metrics and display timeseries
🎉 No plugins needed
👁️ No Grafana? No problem! Use View
⚡ gigapipe implements the Tempo API for transparent compatibility with TraceQL clients.
Any Tempo/OpenTelemetry compatible client or application can be used with gigapipe out of the box
The Tempo datasource can be used to natively query traces including TraceQL and supporting service graphs
🎉 No plugins needed
👁️ No Grafana? No problem! Use View
⚡ gigapipe implements the Pyroscope API for transparent compatibility with Pyroscope SDK clients.
Any Pyroscope SDK client or Pyroscope compatible agent can be used with gigapipe out of the box for continuous profiling
gigapipe ships with view - our zero dependency, lightweight data explorer for Logs, Metrics and Traces
gigapipe can ingest data using formats from Grafana, InfluxDB, DataDog, Elastic and other vendors.
With gigapipe and Grafana everything just works right out of the box:
- Native datasource support without any plugin or extension
- Advanced Correlation between Logs, Metrics and Traces
- Service Graphs and Service Status Panels, and all the cool features
📚 Follow our team behind the scenes on the gigapipe blog
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.
©️ GIGAPIPE, HEPVEST BV, released under the GNU Affero General Public License v3.0. See LICENSE for details.
Footnotes
-
Gigapipe is a 100% clear-room api implementation and does not fork, use or derivate from Grafana code or design concepts.1 ↩
-
Gigapipe is not affiliated or endorsed by Grafana Labs or ClickHouse Inc. All rights belong to their respective owners.2 ↩
-
Grafana®, Loki™ and Tempo® are a Trademark of Raintank, Grafana Labs. ClickHouse® is a trademark of ClickHouse Inc.3 ↩