Size of full Response (Bytes) sent, includes Header and Body.

The round trip time (RTT) in microseconds from when a request is submitted from a client to a CDN server and back again to the starting point.

The number of microseconds between receiving the request and writing the first byte of the response, as measured on the server.

Time-Taken since the first byte read to the last byte sent.

List of the headers sent in the request to the CDN.

List of the query parameters included in the request sent to the CDN.

Boolean value indicating if the response pulled from server's local cache.

Additional information that expands on the cacheHit data point describing the result or actions taken if the cache is unavailable.

The value of the HTTP Content-Type header of the response.

HTTP Status Code returned by the server.

The name of the domain that originated the request. Common referrers include search engines, other websites that link directly to your objects, and your own website.

Unique identifier of the log file.

Unique identifier for each event message fired by a Collector or log file received by Datazoom. The string includes an incremental counter at the end to allow for sequencing the events from a user session.

Content Distribution Network name

Host of the client's request.

Unique identifier for the user's current Datazoom session. Session will persist as long as the user is viewing content uninterrupted. A 20 minute pause in activity will close the session.

IP address of the user's device

A unique id for the current video playback session.

Contains a number of tokens that refer to aspects of the user device, including the user's browser name and version, rendering engine, device’s model number, operating system and its version, etc.

The city or town where the user is located

The country from which the browser initiated the event. For a list of country codes, see ISO 3166-1 alpha-2 .

The specific administrative division within a country where the event occurred. In the United States, regions correspond to state names ; for example, Washington or New York.

The specific administrative division within a country where the event occurred. In the United States, regions correspond to state codes ; for example, WA or NY.

Autonomous System Number: a unique number identifying a group of IP networks that serves the content to the end-user. Client ASN as determined from a lookup of the client IP

The organization that owns the Autonomous System Number. Often an ISP, sometimes a private company or institution.

Key is included without a value if the object is needed urgently due to startup, seeking or recovery after a buffer-empty event. The media SHOULD not be rendering when this request is made. This key MUST not be sent if it is FALSE.

The buffer length associated with the media object being requested.

Key is included without a value if the buffer was starved at some point between the prior request and this object request, resulting in the player being in a rebuffering state and the video or audio playback being stalled. This key MUST NOT be sent if the buffer was not starved since the prior request. If the object type ‘ot’ key is sent along with this key, then the ‘bs’ key refers to the buffer associated with the particular object type. If no object type is communicated, then the buffer state applies to the current session.

A unique string identifying the current content.

Deadline from the request time until the first sample of this Segment/Object needs to be available in order to not create a buffer underrun or any other playback problems.

The encoded bitrate of the audio or video object being requested. This may not be known precisely by the player; however, it MAY be estimated based upon playlist/manifest declarations. If the playlist declares both peak and average bitrate values, the peak value should be transmitted.

The throughput between client and server, as measured by the client and MUST be rounded to the nearest 100 kbps. This value, however derived, SHOULD be the value that the client is using to make its next Adaptive Bitrate switching decision. If the client is connected to multiple servers concurrently, it must take care to report only the throughput measured against the receiving server. If the client has multiple concurrent connections to the server, then the intent is that this value communicates the aggregate throughput the client sees across all those connections.

Relative path of the next object to be requested. This can be used to trigger pre-fetching by the CDN. This MUST be a path relative to the current request. This string MUST be URLEncoded [5]. The client SHOULD NOT depend upon any pre-fetch action being taken - it is merely a request for such a pre-fetch to take place.

If the next request will be a partial object request, then this string denotes the byte range to be requested. If the ‘nor’ field is not set, then the object is assumed to match the object currently being requested. The client SHOULD NOT depend upon any pre-fetch action being taken – it is merely a request for such a pre-fetch to take place. Formatting is similar to the HTTP Range header, except that the unit MUST be ‘byte’, the ‘Range:’ prefix is NOT required and specifying multiple ranges is NOT allowed. Valid combinations are: "<range-start>-" "<range-start>-<range-end>" "-<suffix-length>"

The playback duration in milliseconds of the object being requested. If a partial segment is being requested, then this value MUST indicate the playback duration of that part and not that of its parent segment. This value can be an approximation of the estimated duration if the explicit value is not known.

The media type of the current object being requested: m = text file, such as a manifest or playlist a = audio only v = video only av = muxed audio and video i = init segment c = caption or subtitle tt = ISOBMFF timed text track k = cryptographic key, license or certificate. o = other If the object type being requested is unknown, then this key MUST NOT be used.

1 if real-time, 2 if double speed, 0 if not playing. SHOULD only be sent if not equal to 1.

A unique identifier that is established to track an individual media object request made from the client to a CDN.

The requested maximum throughput that the client considers sufficient for delivery of the asset. Values MUST be rounded to the nearest 100kbps. For example, a client would indicate that the current segment, encoded at 2Mbps, is to be delivered at no more than 10Mbps, by using rtp=10000. Note: This can benefit clients by preventing buffer saturation through over-delivery and can also deliver a community benefit through fair-share delivery. The concept is that each client receives the throughput necessary for great performance, but no more. The CDN may not support the rtp feature.

A GUID identifying the current playback session. A playback session typically ties together segments belonging to a single media asset. Maximum length is 64 characters. It is RECOMMENDED to conform to the UUID specification [7].

Describes if the content being streamed is Live or On Demand.

The streaming format that defines the current request. d = MPEG DASH h = HTTP Live Streaming (HLS) s = Smooth Streaming o = other If the streaming format being requested is unknown, then this key MUST NOT be used.

A unique identifier that is established to track an internal CDN request where a media object cannot be fulfilled by the initial service receiving the request and gets passed to another node for fulfillment.

The highest bitrate rendition in the manifest or playlist that the client is allowed to play, given current codec, licensing and sizing constraints.

The version of the CMCD specification used for interpreting the defined key names and values.