If an agent can ship to Loki, Prometheus, Tempo, OTLP, InfluxDB, Elastic or Datadog, it can ship to Gigapipe. Point it at a Gigapipe endpoint and change nothing else.
Ingest endpoints are protocol-compatible, not merely inspired by the originals. OTLP is accepted over both gRPC and HTTP, so an unmodified OpenTelemetry Collector exports to Gigapipe with a standard exporter block. That includes the OpenTelemetry profiles signal (profiles/v1development) alongside the classic Pyroscope ingest API — both land in the same ClickHouse tables and are queried the same way.
How Gigapipe handles OpenTelemetryThe same stored data answers several query languages: LogQL for logs, PromQL for metrics, TraceQL for traces and FlameQL for profiles, plus ClickHouse SQL when you want to reach past all of them. Existing dashboards, alert rules and recording rules keep working, because the query API they call has not changed. Profiles are served through the Pyroscope query API — flamegraphs, diffs, series, label and profile-type discovery — and can also be exported as Graphviz DOT for external tooling.