You can configure a data stream to collect these parameters. To get a list of available parameters, you can run the List data set fields operation.
Some data sets may not be available for logging depending on the product enabled for the property you want to monitor. For example, Web security and EdgeWorkers information data set fields are not supported for the Cloud Wrapper products.
If you're looking for sample logs (JSON and structured) with data, see Log format.
|Data set field ID
|The unique identifier of the stream that handled the request.
|The Content Provider code associated with the request.
|The identifier of the request.
|The content bytes served in the response body. For HTTP/2, this includes overhead bytes.
|The IPv4 or IPv6 address of the requesting client.
|HTTP status code
|The HTTP status code of the response.
|The scheme of the request-response cycle, either HTTP or HTTPS.
|The value of the Host header in the request.
|The HTTP method of the request.
|The path to a resource in the request, excluding query parameters.
|The client TCP port number of the requested service.
|The size of the entity-body in bytes returned to the client.
|The type of the content returned to the client.
|The URI-encoded user agent making the request.
|The list of languages acceptable in the response.
|A list of HTTP cookies previously sent by the server with the Set-Cookie header.
|The part of an entity that the server is requested to return.
|The address of the resource from which the requested URL was followed.
|The originating IP address of a client connecting to a web server through an HTTP proxy or load balancer.
|Request end time
|The time in milliseconds it takes the edge server to fully read the request.
|The IP address of the edge server that served the response to the client. This is useful when resolving issues with your account representative.
|A string describing the problem with serving the request.
|The time when the edge server accepted the request from the client.
|Turn around time
|The time in milliseconds from when the edge server receives the last byte of the request to when it sends the first bytes of the response.
|The time in milliseconds from when the edge server is ready to send the first byte of the response to when the last byte reaches the kernel.
|TLS overhead time
|The time in milliseconds between when the edge server accepts the connection and the completion of the SSL handshake.
|The protocol of the TLS handshake, either TLSv1.2 or TLSv1.3.
|The size of the object, excluding HTTP response headers.
|The size of the uncompressed object, if zipped before sending to the client.
|The time in seconds that the object is valid for positive cache responses.
|TCP overhead in bytes for the request and response.
|DNS lookup time
|The time in seconds between the start of the request and the completion of the DNS lookup, if one was required.
|The total bytes served in the response, including content and HTTP overhead.
|The query string in the incoming URL from the client. To monitor this parameter in your logs, you need to update your property configuration to set the Cache Key Query Parameters behavior to include all parameters.
0 if there was no object in the cache, and
1 if the object was present in the cache. In the event of negatively cached errors or stale content, the object is served from upstream even if cached.
|The ISO code of the country or region where the request originated.
|The state where the request originated.
|The city where the request originated.
1 if the object is cacheable based on response headers and metadata,
0 if the object is not cacheable.
|Returns additional breadcrumbs data about the HTTP request-response cycle for improved visibility into the Akamai platform, such as the IP of the node or host, component (cache parent, edge host, peer host, origin, or Cloud Wrapper), request end, turnaround and DNS lookup time. This field is available only for Adaptive Media Delivery, Download Delivery, Object Delivery, Dynamic Site Accelerator, Ion Standard, Ion Premier, and API Acceleration products.
To log this parameter for Dynamic Site Accelerator, Ion Standard, and API Acceleration, you need to enable the
breadcrumbs behavior in your stream's property configuration. See Breadcrumbs in the Property Manager guide.
|The last byte of the object that was served in this response.
0 indicates a part of a byte-range response. This field is available for all products supported by DataStream 2.
|The Autonomous System Number (ASN) of the request's Internet service provider.
|File size bucket
|This field groups the response content into different buckets by size in kilobytes, megabytes and gigabytes.
|The number of attempts to download the content from the edge in a specific time interval, based on the number of total manifest requests received.
|Time to first byte
|The time taken to download the first byte of the received content in milliseconds.
|The number of download initiation failures in a specific time interval.
|The time taken to download the object in milliseconds.
|The byte transfer rate for the selected time interval in kilobits per second.
|Returns data on security policy ID, non-deny and deny rules when the request triggers any configured WAF or Bot Manager rules. Requires configuring the Web Application Firewall (WAF) behavior in Property Manager or adding hostnames in Security Configurations.
|The ISO code of the country or region from where the request was served.
|The Akamai geographical price zone from where the request was served.
|This field reports the status when serving a Brotli-compressed object. This field is available only for Ion Standard, Ion Premier and Ion Media Advanced products. See Brotli status in the DataStream user guide for details.
|The compressible Content-Length object value (in bytes) in the response header from the origin. This field is available only for Ion Standard, Ion Premier and Ion Media Advanced products.
|The number of successful download initiations in a specific time interval.
|The number of complete successful downloads.
|Returns a Common Media Client Data (CMCD) payload with detailed data on media traffic. This field is available only for the Adaptive Media Delivery product. See Common Media Client Data in the DataStream user guide for details.
|Limits logged data to a specific media delivery type, such as live, VOD (video on demand), or default.
|Reports the logged data's media delivery format, such as HDS and HLS fragmentation, HDS and HLS stream packaging, Dynamic Adaptive Streaming over HTTP (DASH), Microsoft Smooth streaming etc., including the default format.
1 if media encryption is enabled for the content delivered from the edge to the client.
|Prefetch midgress hits
1 if an edge server prefetched the content from a parent edge server other than the origin.
|Returns EdgeWorkers data for client requests and responses if EdgeWorkers is enabled. The field format is:
//[EdgeWorkers-Id]/[Version]/[Event Handler]/[Off Reason]/[Logic Executed]/[Status]/#[Metrics].
|Returns EdgeWorkers execution information if enabled, including the stage of execution, the EdgeWorker ID, process, total and total stage time (in milliseconds), used memory (in kilobytes), ghost flow, error code, HTTP status change when the response is generated using the API, CPU flits consumed during processing, tier ID for the request, indirect CPU time (in milliseconds) and ghost error code.
|Content protection information
|Returns Enhanced Proxy Detection data, including the GeoGuard category, and the action EPD performed on the request. See Reporting metrics and dimensions for details.
|The data specified in the Custom Log Field of the Log Requests Details that you want to receive in the stream. See Custom log field.
You can use DataStream 2 to log midgress traffic on your property, such as between two Akamai edge servers. Using the Create a stream or Edit a stream operations, set the
collectMidgress member to
true, and go to Property Manager to enable the Collect midgress traffic option in the DataStream behavior for your property. As a result, the second place in the log line contains a numeric value:
0, if the request was processed between the client device and edge server (
CLIENT_REQ), and isn't logged as midgress traffic
1, if the request was processed by an edge server within the region (
PEER_REQ), and is logged as midgress traffic
2, if the request was processed by a parent Akamai edge server in the parent-child hierarchy (
CHILD_REQ), and is logged as midgress traffic
When you enable logging midgress traffic from your stream, the Get a stream operation returns the
collectMidgress member as
true and lists the
isMidgress data set field together with other data set fields you log in the stream. If the logging midgress traffic feature is not enabled on your contract, contact the Akamai support team.