Skip to content
MeshedFlowMeshedFlow

Analytics & pilot reports

MeshedFlow measures real delivery. Everything you see is derived from the session reports the SDK posts during playback — offloaded bytes, fallback bytes, peer counts, buffer health, and the stall counters your player reports.

What you can see in the portal

Section titled “What you can see in the portal”

The Dashboard shows your streams and, per stream:

  • Offload % — the share of delivered bytes served by peers instead of your CDN (avgOffloadRatio).
  • Bytes offloaded vs. fallback — the peer-delivered and CDN-delivered byte totals.
  • Peers — average peer count per session over the window.
  • Sessions and buffer health — session totals and average buffer health.

The same figures are available over the HTTP API — GET /telemetry/streams?detail=1, GET /telemetry/metrics/:streamId, GET /telemetry/timeseries, and GET /telemetry/export.

The pilot report

Section titled “The pilot report”

A pilot report is a report of your event’s offload and savings — a structured document composed from your stream’s session reports, your billing rates, and the platform’s live configuration. Retrieve it from:

GET /control/reports/pilot/:streamId

The :streamId must be one of your own streams. See the HTTP API reference for auth and query params.

The three formats

Section titled “The three formats”

Pass ?format=:

  • json (default) — the full structured report object.
  • md / markdown — a downloadable Markdown document, structured to the MeshedFlow pilot report template, with operator-judgement fields left blank.
  • html — a self-contained, styled HTML document (the artifact typically emailed to a pilot company).
Terminal window
curl -H "Authorization: Bearer $TOKEN" \
  "https://app.meshedflow.com/control/reports/pilot/cust_20260808_eb8790f7:live-demo?format=html" \
  -o pilot-report.html

What the report contains

Section titled “What the report contains”

The rendered report includes:

  • Pilot metadata — date range, streams tested, viewer count and device mix, regions, and signaling deployment.
  • Configuration — SDK and signaling versions, remote-config policy, upload caps, auth mode, telemetry retention, and data region.
  • Results — total sessions and bytes, P2P-offloaded vs. CDN-fallback bytes, aggregate and steady-state offload ratio (with cold-start and final windows), rebuffer events, startup-time p95, average peer count, P2P connection success, and signaling errors — compared against a CDN-only control cohort when one ran.
  • Routing breakdown — fallback reasons, delivery modes and paths, validation failures, and busy-peer events.
  • Cost impact — offloaded GB, avoided CDN cost, the MeshedFlow fee, and net savings (see below).
  • Event economics — a peak-concurrency-based forecast cross-check.
  • Conclusion — an auto-assessed pass/review against explicit criteria, with risks and required fixes. Operator-judgement lines (approved public claims, final pass/fail sign-off) are left for a human to fill in — the system never writes the conclusion of its own evaluation.

How savings are computed

Section titled “How savings are computed”

The cost figures come from your offloaded bytes and your CDN rate — not an assumed benchmark:

offloaded GB       = bytesOffloaded / 1e9
avoided CDN cost   = offloaded GB × your CDN $/GB
MeshedFlow fee     = avoided CDN cost × savings-share %
net saving         = avoided CDN cost − MeshedFlow fee

MeshedFlow bills a share of the CDN spend you avoided, so the fee only exists where there were real savings. When no CDN rate is on file for your account, the report falls back to a platform-default rate and says so — a savings figure argued from an assumed rate always admits the assumption. Set your real CDN rate so the numbers are yours.

Section titled “Related”