Cloudflare Deepens Observability with OpenTelemetry Spans Across Entire Request Path
OpenTelemetry
Cloudflare
Distributed Tracing
Observability
Edge Computing
API Gateway
This summary and analysis were generated by AI from the original article at InfoQ AI and may contain errors (how Viqus works). Read the source for full details.
7
Edge Observability Standardized
Media Hype
6/10
Real Impact
7/10
What is the Viqus Verdict?
We evaluate each news story based on its real impact versus its media hype to offer a clear and objective perspective.
AI Analysis:
The technical depth and standardization efforts suggest real, lasting infrastructure improvements, though the market hype is currently focused on the feature rollout rather than a paradigm shift.
Article Summary
Cloudflare's Traces feature is advancing significantly, extending automatic tracing from Workers to encompass the entire request path, making security rules, transformations, caching decisions, and routing all visible as granular OpenTelemetry spans. This provides unprecedented visibility into request latency and flow within the proxy layer. Crucially, the system supports W3C traceparent headers, enabling seamless context propagation with upstream services. The pricing structure is shifting from a span-based model to one based on data ingestion and retention, which developers must account for. Furthermore, the integration of an agent layer allows for querying and comparing traces against code repositories, moving observability from passive dashboards to active, actionable analysis.Key Points
- Cloudflare now exposes the entire request path—including security and transformation rules—as standardized OpenTelemetry spans for comprehensive visibility.
- The tracing system supports W3C context propagation, allowing traces to join and continue across multiple upstream services.
- Pricing is shifting from billing per span to a volume-based model charging for data ingestion and retention.