Sending OTLP

Endpoints

The address is the DSN's host. With the DSN https://rzi_…@ingest.rezee.app/1042:

https://ingest.rezee.app/v1/traces
https://ingest.rezee.app/v1/logs
https://ingest.rezee.app/v1/metrics

Send the key as a bearer token, or in an x-rezee-key header. Use a server source's key: a browser key is refused, since it is public in a page.

With the standard exporter settings

OTEL_EXPORTER_OTLP_ENDPOINT=https://ingest.rezee.app
OTEL_EXPORTER_OTLP_HEADERS="authorization=Bearer rzi_…"
OTEL_SERVICE_NAME=orders-api
OTEL_RESOURCE_ATTRIBUTES="service.version=1.4.2,deployment.environment.name=production"

service.version is the release and deployment.environment.name the environment; with no environment, it is production.

The key says which source; service.name splits it, as in one source for every backend service. A source keeps its first 50 service names. What a new name past that sends is dropped and shown on the source page, and a JSON request is told which name in partialSuccess.

What becomes what

• Spans are traces in Signals → Performance. Each endpoint or page is compared release to release, and a release where its p95 got at least half again slower and 100 ms more, or its error rate three times higher and 2 points up, with 20 samples on each side, is called out.
• Log records are lines in Signals → Logs, tied to their trace.
• Metrics are charted on dashboards: gauges, sums and histograms with explicit buckets. Cumulative sums and histograms are kept as the change between points. Exponential histograms and summaries are not kept yet. An up-down counter is kept as a gauge, and metric points carry no release or environment.

At the limit

Past a workspace's monthly quota for spans or logs, a JSON request is answered 200 with a partial success saying how many were refused, so an exporter does not resend the batch. A protobuf request is answered 200 without one. Metrics are not metered.