Overview:
Gigapipe is a lightweight, open-source observability stack designed to handle logs, metrics, traces, and continuous profiling within a single platform. It acts as a drop-in replacement for several popular observability tools, supporting native ingestion and querying via Loki, Prometheus, Tempo, and Pyroscope APIs. The project is aimed at developers and operators who want a polyglot observability solution that allows them to retain full control over their data. It can be used with familiar query languages like LogQL, PromQL, and TraceQL, and is built to work seamlessly with Grafana without requiring plugins.
Core Features:
API Compatibility: Implements Loki, Prometheus, Tempo/Zipkin, and Pyroscope APIs for transparent, drop-in compatibility with existing clients and tools.
Multi-Protocol Ingestion: Supports data ingestion via OpenTelemetry, and native protocols from Loki, Prometheus, Tempo, InfluxDB, DataDog, and Elastic.
Built-In Explorer (View): Includes a zero-dependency, lightweight data explorer for browsing logs, metrics, and traces.
Multi-Language Query Support: Enables querying of ingested data using LogQL, PromQL, and TraceQL.
Data Storage Options: Can store observability data using ClickHouse or DuckDB, with support for S3 object storage.
Use Cases:
Developers monitoring applications: Teams can ingest OpenTelemetry data and query it using LogQL, PromQL, or TraceQL without modifying their instrumentation.
Operators centralizing observability: System administrators can use Gigapipe as a single backend to replace separate Loki, Prometheus, and Tempo instances.
Users exploring data without Grafana: Operators can use the built-in View explorer to navigate logs, metrics, and traces directly.
Prometheus users migrating stacks: Teams using Prometheus-compatible clients can point them at Gigapipe and continue querying with PromQL.
Why It Matters:
Gigapipe provides a unified, open-source alternative to vendor-controlled observability stacks by independently implementing multiple popular APIs and protocols. Its polyglot design allows teams to mix and match ingestion and query tools (e.g., OpenTelemetry with LogQL) while retaining full data control through self-hosted storage backends like ClickHouse. The project’s commitment to being a direct drop-in replacement for Loki, Prometheus, Tempo, and Pyroscope reduces lock-in and simplifies migration for existing deployments.
