Skip to content
Oriel

Self-observability

Self-observability writes Oriel’s own telemetry into the reserved _oriel workspace and exposes Prometheus-format process metrics.

Requirements

Section titled “Requirements”
  • Migrations applied
  • ClickHouse reachable
  • First admin bootstrapped if you need UI access to _oriel

Configure self-observability

Section titled “Configure self-observability”

Self-observability is enabled by default:

[self_observability]
enabled = true
interval = "30s"
sample_ratio = 1.0

Oriel writes its own telemetry into the reserved _oriel workspace, project oriel, environment default, service oriel.

Prometheus-format metrics are available at:

/internal/metrics

The route remains valid even when self-observability is disabled.

Check telemetry

Section titled “Check telemetry”
Terminal window
curl -fsS http://localhost:6743/internal/metrics

In the UI, switch to workspace _oriel after bootstrap grants the first admin owner access.

Recover

Section titled “Recover”
  • If self-observability cannot start, Oriel logs a warning and continues.
  • If ClickHouse is unavailable, self-observability may be disabled while core dependency failures appear elsewhere.
  • To reduce trace volume, lower self_observability.sample_ratio.