EINBLIQ.IO / Resources
Full Visibility for CMCD Headers

Connecting player reports with CDN logs
CMCD player reports are useful to a log-based investigation only when the CDN captures and exports them. This work with Gcore addressed requests that carry CMCD in headers, rather than in the URL query string.
Common Media Client Data (CMCD, CTA-5004) standardizes player reports that add context to the delivery record. These observations help investigate a bitrate change or a stall; they do not establish its cause on their own. Available fields include:
-
Encoded bitrate (
br) -
Buffer length (
bl) -
Measured throughput (
mtp) -
Object duration (
d) -
Buffer starvation events (
bs) -
Session identifiers (sid) and content identifiers (cid).
Historically, most web-based players transmitted CMCD via query strings. This integrates naturally with traditional CDN logging models and makes extraction straightforward.
A common concern is potential cache-key fragmentation. This is not an inherent limitation of query-string-based CMCD. Modern CDNs can and should exclude CMCD parameters from cache-key calculation. When configured correctly, query-string transport does not negatively impact caching efficiency. Players may also transmit CMCD via dedicated HTTP headers, including in Apple, Android and RDK environments where supported and configured:
-
CMCD-Object -
CMCD-Request -
CMCD-Session -
CMCD-Status
Header-based delivery keeps URLs clean and aligns with HTTP semantics by separating metadata from resource identity.
Operationally, however, this introduced an observability gap: many CDN logging systems were historically optimized around query parameters and did not fully extract structured CMCD header data.
The telemetry was present in the request. It was just not consistently available in logs.
Closing the Observability Gap: The Gcore Implementation
To ensure full transport neutrality, we worked closely with Gcore to define a clear implementation objective:
CMCD delivered via HTTP headers must be indistinguishable from CMCD delivered via query strings at the log level.
Together, we aligned on the technical requirements, and the Gcore engineering team implemented full support for CMCD via HTTP headers within their logging infrastructure. The solution includes:
-
CMCD header capture through the FastEdge application, alongside query-string capture
-
URL-encoded logging of CMCD values into a dedicated log field
-
Concatenation of all four CMCD header namespaces into a single, comma-separated field
-
Full equivalence between header-based and query-string-based CMCD in log output
The implemented solution operates directly at the CDN edge. When a request arrives, Gcore now:
-
Detects all CMCD-related headers
-
Extracts their values without semantic transformation
-
URL-encodes the combined key-value pairs
-
Concatenates them into a canonical representation
-
Writes the result into a dedicated
cmcdlog field
The application gives this integration a shared CMCD representation for both transmission modes. The export policy still determines which fields reach the downstream pipeline:
-
Query-based CMCD must be excluded from cache keys, as shown in the Gcore setup guide
-
Both forms can be handled through the agreed CMCD mapping
-
Header-based player reports can be examined alongside delivery records
Operational Availability
The feature is already available as the Log CMCD headers application within the Gcore CDN platform through the FastEdge service (Gcore documentation).
To enable it, customers simply add the Log CMCD headers application to their CDN configuration. For players already emitting the required CMCD headers, this CDN-side configuration captures that existing telemetry. Player version and configuration still determine the emitted fields. Once activated, CMCD values delivered via HTTP headers are automatically captured and written into the dedicated log field.
For the current export configuration and its remaining draft field list, use the Gcore integration guide.
Open full-size image Screenshot of the Gcore CDN interface showing the "Log CMCD headers" template option. A red circle highlights the description: "Log CMCD headers CMCD-Request, CMCD-Object, CMCD-Status and CMCD-Session into CDN access log as comma-separated list. ↗CMCD v2: Expanding Telemetry While Preserving Request Mode
CMCD v2 introduces a significantly expanded and refined telemetry model with many beneficial new keys. Read more here CMCD v2 released or access the specs at CTA WAVE: Common Media Client Data (CTA-5004-B)
In addition to the extended metric vocabulary, CMCD v2 formally introduces event mode, enabling players to report telemetry directly to a configured third-party endpoint.
At the same time, request mode remains a critical observability mechanism. Request mode continues to provide:
-
Large-scale batch analytics
-
Historical quality-of-experience correlation
-
Independent validation of player-side reporting
-
Deep dive root cause analysis at logline level
Detailed CDN logs allow engineers to correlate CMCD values with HTTP status codes, retry behavior, cache interactions, and edge-to-origin flows. For complex production incidents, per-request visibility remains indispensable.
For this reason, request mode will continue to play a central role in many environments, even as event mode adoption grows.
By ensuring that header-based CMCD is logged in canonical form, this implementation facilitates the logging of available CMCD v2 fields in request mode. New keys pass through transparently. Existing analytics pipelines remain stable. No structural redesign is required to benefit from the expanded standard.
A sincere thank you to the Gcore engineering team, especially Ilja Karamisevs, for the fast, precise, and high-quality implementation. This kind of collaboration is exactly how standards adoption should work in practice.
For current reporting options and player support, read CMCD v2: The state of open streaming analytics.
For the two reporting paths and their limits, read Common Media Client Data explained.