Skip to content
Oriel

Overview

Oriel gives operators and teams one place to inspect OpenTelemetry traces, logs, and metrics. It keeps the deployment small: one oriel binary plus PostgreSQL for metadata, ClickHouse for telemetry, and Valkey for runtime cache/pub-sub.

The Oriel overview screen for the _oriel self-observability workspace, showing 24 hours of throughput, latency, and service data.

What Oriel Stores

Section titled “What Oriel Stores”

Oriel organizes telemetry by a fixed hierarchy:

workspace -> project -> environment -> service

Every telemetry row is resolved to a workspace, project, environment, and service during ingest. The workspace is the tenancy boundary; projects and environments are the operational slice users work inside.

What You Need

Section titled “What You Need”

For the local path:

  • Docker and Docker Compose
  • Ports 6743, 4317, 4318, 5432, 8123, and 9000 available locally
  • A browser for the UI

For a production path:

  • PostgreSQL for metadata
  • ClickHouse 25.3 or newer for telemetry
  • Valkey for runtime cache/pub-sub
  • A stable oriel.toml or equivalent ORIEL_* environment variables
  • TLS termination, either native Oriel TLS or a proxy
  • A migration step before serving a new binary

Main Workflows

Section titled “Main Workflows”

Use these pages first:

Then choose your path: