aiqbench takeAI Products

Cloudflare Traces now provides end-to-end visibility into the proxy layer by converting internal events like caching and routing into OpenTelemetry spans, eliminating previous gaps where these steps were only inferred from logs. This update allows distributed tracing systems to accurately attribute latency and errors to specific infrastructure components within the edge network without requiring custom instrumentation.

Source coveringInfoQ

What this isA model's reading of the article and related coverage, written for aiqbench. Not the publisher's words.

Cloudflare Traces Turns the Proxy Layer into OpenTelemetry Spans, with New Volume-Based Pricing

InfoQOctober 10, 20264 min read

Cloudflare has put Traces into open beta, extending automatic tracing from Workers to security rules, transformations, cache, routing and origin handling as OpenTelemetry spans. Traces accept and forward W3C traceparent headers, and Trace Rules allow targeted sampling. Pricing moves to ingestion and retention volume from December 1. By Steef-Jan Wiggers

Cloudflare has recently made Traces available in open beta, extending automatic tracing from Workers to the rest of the request path. Security rules, transformations, cache decisions, routing, Worker execution, and origin handling now appear as OpenTelemetry spans in a single request-level timeline, without any instrumentation to write. A pricing change arrives with it, and it applies to Workers Tracing too. This fills a well-known gap for developers running distributed…

Excerpt shown under the publisher's RSS terms · 69 words · full text and figures are on the publisher's site

Read at InfoQ ↗Ask about this article