Telemetry
OTLP resource attributes, traceparent exposure, span method and status, and split log sink.
Patches to what Cello records and where it sends it. The Telemetry page is the reference; these are the deltas over upstream denoland/celld. Each entry names its fork patch number.
0132— The OTLP resource parses the standardOTEL_RESOURCE_ATTRIBUTESenv var into ordered resource entries.service.namein the extra entries is ignored (the configured service name wins);service.versionin the extra entries names the application version, and Cello’s own build stays visible undercello.version, which cannot collide with an application key. Built-in resource keys win over colliding entries, and keys and values are percent-decoded before export.service.nameprecedence is env (OTEL_SERVICE_NAME), then resource attributes, then thecellodefault. Default behavior change: without an operator 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).0133— The handler reads 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).0136—CELLO_OTEL_LOGSsplits the log sink from traces: 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. A fleet can point its collector at traces while its logs land in the bucket (upstream #153).