Documentation
Everything you need to send telemetry to PackDB and explore it. Start with the quickstart, then dig into the reference guides.
Start here
Quickstart
Send your first telemetry with an OpenTelemetry collector or a single curl, then read it back.
Read the quickstart →Connect your data
Copy-paste OTel, curl, and Grafana examples wired to your environment endpoints and workspace API-key flow.
Open Connect →API keys
Mint a machine key (packdb_…) for ingestion and queries. Use it as the X-API-Key header.
Manage keys →Guides
Reference guides
Deep-dive guides are expanding. Here is the map of what they cover — the quickstart above and the in-product Connect panel cover the activation path today.
Getting Started
- Introduction — What PackDB is and how it works
- Quick Start — Up and running in 5 minutes
- Account Setup — Create and configure your account
- Configuration — Platform settings and tuning
Send Data
- OpenTelemetry (OTLP) — HTTP and gRPC ingestion
- Prometheus Remote Write — Prometheus-compatible ingestion
- API Keys & Auth — Authentication for data ingestion
Query Data
- PromQL Guide — Query metrics with Prometheus syntax
- SQL Reference — PostgreSQL date_bin() dialect over FlightSQL and REST
- LogQL Guide — Log queries with LogQL
- TraceQL Guide — Trace search with TraceQL — the default trace query surface
- Jaeger Traces — Trace exploration with Jaeger API
API Reference
- REST API — HTTP endpoints for all signals
- gRPC API — High-performance gRPC interface
- Authentication — API keys and tokens
- Error Codes — Error reference and troubleshooting
Platform
- Service Graph — Service dependency visualization
- Dashboards — Built-in and Grafana dashboards
- Team Management — Users, roles, and permissions
- Usage & Billing — Monitor your usage and plan
Architecture
- Architecture Overview — System design and data flow
- Storage Engine — Arrow-based columnar storage
- Security — Data encryption and compliance
Can't find what you need? Ask us →