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
Read the original at InfoQ: AI, ML and data engineering: Cloudflare Traces Turns the Proxy Layer into OpenTelemetry Spans, with New Volume-Based Pricing
How OpenSmartRoute helps
The router treats agents, tools and skills as targets in the same catalogue as models. An MCP tool or an A2A agent is one entry; the router picks it when it fits the request and learns from how it performs. The same guard and resource limits apply to a tool's arguments as to a prompt.
For a team that routes through the router, a release like this is one catalogue entry. The new model competes on the next request against what the team already runs, on quality, cost and speed. If it answers well it earns more traffic; if it fails it gets less, with no code change in the app.