Oriel Documentation

Oriel is a self-hosted, OpenTelemetry-native observability platform. It ingests OTLP traces, logs, and metrics, stores telemetry in ClickHouse, stores control plane data in PostgreSQL, uses Valkey for runtime cache/pub-sub, and exposes a browser UI plus an HTTP API.

Oriel overview showing request throughput, latency, active alerts, service health, and slow operations.

Use Oriel

Query telemetry, inspect traces, read logs, manage feature flags, build dashboards, manage alerts, and administer workspaces.

Start with the scope model.

Operate Oriel

Install the service, configure storage and TLS, run migrations, monitor readiness, and recover from common failures.

Start with the architecture guide. For cluster installs, use the Kubernetes guide.

Fast Path

For a local full stack:

cd deploy/compose
docker compose up --build

When the stack is healthy, bootstrap the first user and workspace:

docker compose exec -e ORIEL_BOOTSTRAP_PASSWORD='change-me' oriel \
  oriel admin bootstrap --email you@example.com
docker compose exec oriel oriel admin create-workspace --slug demo

The local endpoints are:

Endpoint	URL
UI and API	`http://localhost:6743`
OTLP gRPC	`localhost:4317`
OTLP HTTP	`http://localhost:4318`

Runtime Shape

Oriel runs as one binary with four runtime roles:

Role	Purpose
`all`	Runs ingest, query/API/UI, and worker in one process. This is the default documented path.
`ingest`	Runs OTLP gRPC and HTTP receivers.
`query`	Runs the UI, management API, query API, health checks, and metrics endpoint.
`worker`	Evaluates alert rules and rolls up service-map edges.

The binary requires PostgreSQL metadata storage, ClickHouse telemetry storage, and Valkey runtime cache/pub-sub.