Zetta-Embodiment
Zetta는 자체 진화하는 물리적 지능을 위한 효율적인 폐쇄루프 구현 하네스이다
오픈 소스 기반 관측 데이터 웨어하우스, ClickHouse 위에 구축
Open source observability warehouse on ClickHouse. Send logs, metrics, traces and profiles with the agents you already run, and query them in Grafana with no plugins. Flat pricing, your infrastructure
개발 도구Go · MakefileGitHub @metrico온라인운영자 미확인
써 보셨어요? 한 번만 눌러 주세요. 로그인은 필요 없어요.
⭐️ The Open-Source Polyglot Observability Warehouse: Light, Fast, Cloud Native, Drop-in Grafana LGTMP alternative :rocket: Indie All-in-One Opentelemetry, Loki, Prometheus, Tempo, Pyroscope On-Prem Alternative :star:
저장소 README에서 가져옴
README 전체를 불러오는 중입니다.
README 전문 보기 ↗formerly known as qryn
:rocket: Gigapipe is a lighweight, multi-standard, polyglot observability stack for Logs, Metrics, Traces and Profiling
ADVANCED_SAMPLES_ORDERING, changing the ordering of an existing deployment/v1development/profiles/v1/metrics (protobuf + JSON)💡 gigapipe independently implements popular observability standards, protocols and query languages
⚡ 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
:tada: No plugins needed :eye: No Grafana? No problem! Use View
Index statistics: Query stream metadata using /loki/api/v1/index/stats to retrieve stream count, entry count, byte volume, and chunk count. Supports LogQL stream selectors for filtering:
GET /loki/api/v1/index/stats?query={job="app"}&start=<ns>&end=<ns>
Enhanced live-tail: The Tail service now supports limit and start query parameters for controlling tail behavior. The limit parameter caps the number of entries returned, and start sets the starting timestamp (in nanoseconds). WebSocket responses include a dropped_entries field indicating when entries were dropped due to backpressure:
{
"streams": [...],
"dropped_entries": []
}
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
:tada: No plugins needed :eye: 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
:tada: No plugins needed :eye: No Grafana? No problem! Use View
gigapipe supports TraceQL metrics endpoints for calculating metrics from trace data. Calculate error rates, latency distributions, and throughput directly from traces using TraceQL queries.
Metrics endpoints:
/api/metrics/query_range - range queries over a time window/api/metrics/query - instant queries at a specific timeParameters:
q or query - TraceQL query string (required)start - start timestamp (unix seconds, nanoseconds, or RFC3339)end - end timestamp (same format as start)since - relative time duration (e.g., "1h", "30m") - alternative to start/endstep - query resolution (e.g., "15s", "1m") - auto-calculated if not specifiedExample:
GET /api/metrics/query_range?q={span.http.status_code=200}&since=1h&step=1m
This query calculates span counts for successful HTTP requests over the last hour with 1-minute resolution.
⚡ 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 also ingests the OpenTelemetry profiles signal (profiles/v1development) directly from OpenTelemetry collectors:
POST /v1development/profiles Content-Type: application/x-protobuf
💡 No collector code changes required — point an
otlphttpexporter at gigapipe and profiles flow in.
OTLP profiles land in the same ClickHouse profiles tables as Pyroscope data and are queryable through the existing Pyroscope-compatible API (flamegraph, series, stacktraces). See docs/otlp-profiles.md for details.
The Render endpoint (/render?format=dot) generates Graphviz DOT format graphs for profiling visualization with enhanced readability:
Features:
maxNodes parameter: Limit the number of nodes displayed in DOT graphs (0 = unlimited). Use this to control graph complexity for large profiles.
GET /render?query=...&from=...&until=...&format=dot&maxNodes=50
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:
📚 Follow our team behind the scenes on the gigapipe blog
Whether it's code, documentation or grammar, we ❤️ all contributions. See docs/contributing.md to get started.
©️ HEPVEST BV, All Rights Reserves. Released under the GNU Affero General Public License v3.0