Origin fetch and bandwidth telemetry

Observability now records origin hops and bandwidth so you can see backend fetch cost next to edge traffic, not only client-facing request volume.

What you can measure

When the edge fetches from an origin or your functions pull remote data, Easel attributes those hops in telemetry. Bandwidth series show how much data moved at the edge and toward origins over your selected window.

That split matters when a “quiet” site still burns bandwidth on large API payloads or cache misses. You can tell whether growth is browser traffic or origin fetch cost.

Using it in practice

Open Observability and check bandwidth and origin-related series alongside request charts. Pair a bandwidth spike with the request explorer to find heavy paths.

CDN caching reduces repeat origin work when responses are cacheable. See CDN caching and CDN for how tiered cache interacts with origin fetch.