Pitot

Pitot (pronounced PEE-toh).

Observability your agents can operate. Send OpenTelemetry to one binary, then investigate with Pitot's built-in agent or connect your own over MCP.

Current Pitot interface with deterministic offline sample telemetry.

Pitot keeps OpenTelemetry traces, logs, and metrics in one binary and one data directory, with no external storage services to operate. Pitot is pre-release and changes without migration paths; the browser client, built-in agent, MCP tools, dashboards, and alerts are preview capabilities (status). Start with the documentation or run it below.

• OTLP ingest over gRPC and HTTP, with local Parquet storage and DuckDB analytics.
• Explore and PitotQL for querying telemetry without an AI provider.
• An investigation agent that answers questions about your telemetry in plain language.
• An MCP server for external agents using the same typed query tools.
• Dashboards across traces, logs, and metrics, and alerts on service error rate, latency, throughput, and log volume.

Quick start

Docker

docker run --name pitot --restart unless-stopped -p 7520:7520 \
  -v pitot-data:/var/lib/pitot/data \
  -e PITOT_AUTH_CODE_SECRET=$(openssl rand -hex 32) \
  labstack/pitot:latest

Open the one-time setup URL printed by the container and create the first administrator. Pitot displays the ingest token exactly once, unless PITOT_INGEST_TOKEN already set it; save it with your collector secrets. For later sign-in without SMTP, mint a 15-minute, single-use link against the running container's control database:

docker exec pitot pitot login-link [email protected]

The UI, API, MCP, and both OTLP transports share port 7520. See installation for image defaults and bind-mount ownership, and first boot for setup and SMTP login.

Native binary

Install a checksum-verified release for Linux or macOS, amd64 or arm64:

curl -fsSL https://raw.githubusercontent.com/labstack/pitot/main/scripts/install.sh | sh
export PITOT_AUTH_CODE_SECRET=$(openssl rand -hex 32)
pitot

Set PITOT_VERSION to a release tag, such as v2026.11.0-alpha, to pin a release, and PITOT_PREFIX to choose the installation directory. Native installs bind 127.0.0.1:7520; set PITOT_ADDR=:7520 for remote access, then follow the same first-boot setup.

Send telemetry

A standard OTLP/HTTP exporter can use the saved ingest token:

export OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf
export OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:7520
export OTEL_EXPORTER_OTLP_HEADERS="authorization=Bearer%20$INGEST_TOKEN"

For a Collector on the same private container network, the forwarding side is:

exporters:
  otlp_http/pitot:
    endpoint: http://pitot:7520
    headers:
      Authorization: "Bearer ${env:INGEST_TOKEN}"

service:
  pipelines:
    traces:  { receivers: [otlp], exporters: [otlp_http/pitot] }
    metrics: { receivers: [otlp], exporters: [otlp_http/pitot] }
    logs:    { receivers: [otlp], exporters: [otlp_http/pitot] }

Use an existing otlp receiver, set INGEST_TOKEN, and replace pitot with the Collector's reachable private hostname. OTLP/gRPC uses localhost:7520 locally; see send telemetry for TLS and HTTP/2 setup.

Enable chat

Select PITOT_AI_PROVIDER=anthropic and inject ANTHROPIC_API_KEY, or select PITOT_AI_PROVIDER=openai and inject OPENAI_API_KEY, then restart Pitot; the selected provider requires its key at startup. With no provider, chat is disabled and the other features still work. See AI settings.

Connect an MCP client

Set PITOT_PUBLIC_URL to your stable, externally reachable HTTPS origin, then point a remote MCP client at that origin's /mcp endpoint. The client discovers and registers through OAuth; you authorize its scopes in the browser. Pitot serves MCP 2026-07-28 and, through the initialize handshake, 2025-11-25 and 2025-06-18 over Streamable HTTP. See connect over MCP for setup and permissions.

This is the beginning of the README. Read the rest at the original. Read the full README ↗