Metrics, logs, and traces.
One bill. Every incident claim linked to evidence.
Point your OpenTelemetry collector at PackDB. Keep your Grafana dashboards. Follow an incident from the service graph to the failing span and the logs it emitted, then paste the link in the postmortem.
PromQL · LogQL · TraceQL$49/mo for 100 GB across all three signals
130 GB on Pro = $49 + 30 GB × $0.50 = $64/month
One workflow, no tab-hopping
Follow the whole investigation
From the service graph to the failing request's trace, then the logs that span emitted, with that service's metrics on the same window.
- 1
Service graph
Spot the service that's erroring or slow in the dependency map.
- 2
Trace
Open a representative trace and walk the spans to the culprit.
- 3
Logs & metrics
Open the logs that span emitted, or that service's metrics, on the same window.
- 4
Evidence
Copy a link that reopens the query and window — or the selected trace and span — in the incident.
Point your OpenTelemetry collector at PackDB
One exporter block, authenticated with a workspace API key.
# otel-collector-config.yaml
receivers:
otlp:
protocols:
grpc:
http:
processors:
batch:
exporters:
otlphttp/packdb:
endpoint: "https://ingest.packdb.io"
headers:
x-api-key: "<YOUR_PACKDB_API_KEY>"
compression: gzip
service:
pipelines:
metrics:
receivers: [otlp]
processors: [batch]
exporters: [otlphttp/packdb]
logs:
receivers: [otlp]
processors: [batch]
exporters: [otlphttp/packdb]
traces:
receivers: [otlp]
processors: [batch]
exporters: [otlphttp/packdb]Then verify your first telemetry and run your first queries in the quickstart.
The workflows, not the feature list
Every card is something you do in the product today.
Send data with one exporter block
Point your OpenTelemetry collector at PackDB with one exporter block, then verify each signal is flowing from the workspace readiness checks.
Follow the quickstartKeep your Grafana dashboards
Provision Prometheus, Loki, Tempo, and Jaeger datasources against PackDB with one API key — existing Prometheus dashboards import unchanged.
Set up the datasourcesQuery in your language
PromQL for metrics, LogQL for logs, TraceQL for traces, and SQL over FlightSQL or REST for cross-signal analytics — plus a Jaeger-compatible API for the tooling you already run.
Browse the docsLink evidence in incidents
Use Copy link in the explorer to preserve the query and time window — or the selected trace and span — behind an incident claim.
Watch the investigation loopBring your own Grafana
Keep Grafana. Add PackDB.
PackDB speaks the Prometheus, Loki, Tempo, and Jaeger query APIs, so existing Grafana connects through standard datasource types — no plugin.
Prometheus
MetricsPromQL-compatible endpoint; existing Prometheus dashboards import unchanged.
Loki
LogsLogQL-compatible endpoint for log queries and Explore.
Tempo
TracesTraceQL trace search in Grafana Explore, over the same workspace key.
Jaeger
TracesJaeger-compatible trace exploration for existing setups.
Compatible APIs mean no migration headaches. Set up the datasources
One bucket, one rate
Costs you can predict
One telemetry bucket across metrics, logs, and traces, then a single flat overage rate — not a separate meter per signal.
One included bucket
100 GB/mo
on Pro across every signal; 5 GB on the 90-day free evaluation.
Flat overage
$0.50/GB
beyond your bucket — the same rate for metrics, logs, and traces.
Retention
30 days
on Pro (14-day on Free), across every signal.
Try it on a real workload
90-day evaluation with 5 GB/month included. No credit card required.
Larger team or procurement requirements? See PackDB for Enterprise or schedule a demo.