Ingest

Use this page when exporters fail, partial-success responses include Oriel diagnostics, or new services do not appear after sending OTLP.

Symptoms

• Applications report OTLP export failures.
• Collector receives partial-success responses.
• New services do not appear.
• Only some signals arrive.

Checks

Confirm the right endpoint:

Exporter	Endpoint
OTLP gRPC	host:4317
OTLP HTTP	http://host:4318

Confirm the header:

Authorization: Bearer orl_...

Confirm the token permits the signal you are sending.

Common diagnostics

Code	Meaning	Fix
ORL-1001	Missing or malformed token	Check bearer header and token secret.
ORL-1002	Token revoked or expired	Create a new ingest token.
ORL-1003	Signal not permitted	Add the signal to the token or use another token.
ORL-1005	Environment unresolved	Set deployment.environment.name, create the environment, or pin the token.
ORL-1006	Environment cap exceeded	Delete stale environments or raise project cap.
ORL-1008	Unsupported content type or encoding	Use supported OTLP gRPC or HTTP encoding.
ORL-1010	Metric series cap exceeded	Reduce cardinality or adjust capacity policy.
ORL-1012	Backpressure	Retry with backoff and inspect ClickHouse health.

Recovery

1. Verify token scope and signal list.
2. Verify project and environment names in Oriel settings.
3. Confirm service.name is set.
4. Check ClickHouse reachability with oriel doctor.
5. Inspect collector logs for retry loops or unsupported compression.

See OTLP ingest reference for endpoint and token details.