Send Telemetry

Oriel accepts OTLP only. Send traces, logs, and metrics to either the gRPC receiver on 4317 or the HTTP receiver on 4318. Operators can also enable OTLP/HTTP on the API/UI port with ingest.http_on_server = true when running the all-in-one server role.

Create An Ingest Token

Create ingest tokens in the Oriel UI under workspace settings. An ingest token is scoped to one workspace and project. It may optionally pin an environment and may restrict the permitted signals.

The token secret is shown once and has the orl_ prefix. Store it in your collector or application secret manager.

Collector Example

receivers:
  otlp:
    protocols:
      grpc:
      http:

processors:
  batch:

exporters:
  otlp/oriel:
    endpoint: localhost:4317
    tls:
      insecure: true
    headers:
      Authorization: Bearer ${ORIEL_INGEST_TOKEN}

service:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [batch]
      exporters: [otlp/oriel]
    metrics:
      receivers: [otlp]
      processors: [batch]
      exporters: [otlp/oriel]
    logs:
      receivers: [otlp]
      processors: [batch]
      exporters: [otlp/oriel]

Environment Resolution

Oriel resolves the environment in this order:

1. A token-pinned environment wins.
2. deployment.environment.name on the resource is used when no environment is pinned.
3. The legacy deployment.environment resource attribute is used as a fallback.
4. If the environment does not exist and project auto-registration is enabled, Oriel creates it until max_environments is reached.
5. If no environment can be resolved, the resource block is rejected.

Required Resource Attributes

Set at least:

service.name
deployment.environment.name

If service.name is missing, Oriel stores the service as unknown_service.

Verify

In the UI:

• Choose the workspace, project, and environment from the scope bar.
• Open Services to confirm the service catalog entry.
• Open Explore and run:

spans | limit 20

For logs:

logs | limit 20

For metrics:

metrics | limit 20