Gigapipe

Running Loki, Prometheus, Tempo and Pyroscope separately means four storage layers and four operational stories. Gigapipe, formerly known as qryn, implements all four sets of APIs itself, so logs, metrics, traces and profiles land in one lightweight stack that existing clients already know how to talk to.

Ingestion is deliberately promiscuous. OpenTelemetry is officially integrated and needs no changes to your instrumentation, while native ingestion also covers Loki, Prometheus, Tempo, Zipkin, Pyroscope, Influx, Datadog and Elastic. Storage sits on ClickHouse, DuckDB or GigAPI with S3 object storage, so the data stays under your control.

Querying works through the languages people already use.

• LogQL: the Loki API is implemented, so any Loki client or the Grafana Loki datasource works with no plugin.
• PromQL: Prometheus API compatibility is provided using WASM.
• TraceQL: Tempo query support covers traces alongside the other signals.
• Profiling API: profiling endpoints export DOT format for Graphviz, and OTLP profiles are ingested through a development endpoint.
• Index stats and tail: stream metadata queries return stream, entry, byte and chunk counts, and live tail takes limit and start parameters and reports dropped entries.

A built-in explorer and a CLI cover people without Grafana, and an OTLP over gRPC receiver takes traces, logs, metrics and profiles. Configuration, a Docker quickstart and cross-cluster setup are documented in the repository. Gigapipe presents itself as the community-powered alternative to vendor-controlled observability stacks, with a hosted free trial for anyone who wants to test before installing. Contributions require a CLA.