Telemetry
OTLP resource attributes, traceparent exposure, span method and status, and split log sink.
Cello records the same traces and logs as upstream, but it tags them so your backend can route them. The Telemetry guide is the reference for what to set; these are the deltas over upstream denoland/celld. Each entry names its fork patch number.
Route exports with standard attributes
0132— The OTLP exporter parses the standardOTEL_RESOURCE_ATTRIBUTESenv var into ordered resource entries.service.namein the extra entries is ignored (the configured service name wins);service.versionnames your application version, and Cello’s own build stays visible undercello.version, which cannot collide with an application key. Built-in keys win over colliding entries, and keys and values are percent-decoded before export. Precedence for the service name is env (OTEL_SERVICE_NAME), then resource attributes, then thecellodefault. Behavior change: without an operator-set version there is noservice.versionat all — reporting Cello’s version there told every deployment-tracking backend that all applications run Cello’s build (upstream #314).
Correlate a request end to end
0133— Your handler can read the traceparent of the span it runs in throughgetCurrentTraceparent()fromcloudflare:workers, so it can return the value for end-to-end tracing (upstream #313).0134— Incoming spans carry the HTTP method and the response status, so worker spans and cell-fetch spans tell apart in export (upstream #285).
Send logs and traces to different sinks
0136—CELLO_OTEL_LOGSsplits the log sink from the traces sink: unset means logs follow the traces sink (the historical behavior);bucketsends logs to bucket Parquet whatever the traces sink is;0drops logs while traces keep exporting; any other value refuses startup. Point your collector at traces while your logs land in the bucket (upstream #153).