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.

Data set field IDField nameData typeDescription
1000CP codestringThe Content Provider code associated with the request.
1002Request IDstringThe identifier of the request.
1100Request timenumberThe time when the edge server accepted the request from the client.
1005BytesnumberThe content bytes served in the response body. For HTTP/2, this includes overhead bytes.
1006Client IPstringThe IPv4 or IPv6 address of the requesting client.
1008HTTP status codenumberThe HTTP status code of the response.
1009SchemestringThe scheme of the request-response cycle, either HTTP or HTTPS.
1011Request hoststringThe value of the Host header in the request.
1012Request methodstringThe HTTP method of the request.
1013Request pathstringThe path to a resource in the request, excluding query parameters.
1014Request portnumberThe client TCP port number of the requested service.
1015Response Content-LengthnumberThe size of the entity-body in bytes returned to the client.
1016Response Content-TypestringThe type of the content returned to the client.
1017User-AgentstringThe URI-encoded user agent making the request.
1019Accept-LanguagestringThe list of languages acceptable in the response.
1023CookiestringA list of HTTP cookies previously sent by the server with the Set-Cookie header.
1031RangestringThe part of an entity that the server is requested to return.
1032RefererstringThe address of the resource from which the requested URL was followed.
1037X-Forwarded-ForstringThe originating IP address of a client connecting to a web server through an HTTP proxy or load balancer.
1033Request end timenumberThe time in milliseconds it takes the edge server to fully read the request.
1066Edge IPstringThe IP address of the edge server that served the response to the client. This is useful when resolving issues with your account representative.
1102Turn around timenumberThe 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.
1103Transfer timenumberThe 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.
2001TLS overhead timenumberThe time in milliseconds between when the edge server accepts the connection and the completion of the SSL handshake.
2002TLS versionnumberThe protocol of the TLS handshake, either TLSv1.2 or TLSv1.3.
2003Object sizenumberThe size of the object, excluding HTTP response headers.
2004Uncompressed sizenumberThe size of the uncompressed object, if zipped before sending to the client.
2005Max-AgenumberThe time in seconds that the object is valid for positive cache responses.
2006Overhead bytesnumberTCP overhead in bytes for the request and response.
2007DNS lookup timenumberThe time in seconds between the start of the request and the completion of the DNS lookup, if one was required. For cached IP addresses, this value is zero.
2008Total bytesnumberThe total bytes served in the response, including content and HTTP overhead.
2009Query stringstringThe 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.
2010Cache statusnumberThe request was served from the edge cache or peer (1), or forwarded to parent or origin (0).
2012Country/RegionstringThe ISO code of the country or region where the request originated.
2013StatestringThe state where the request originated.
2014CitystringThe city where the request originated.
2020BreadcrumbsstringReturns 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, and Object Delivery products.
2021Last bytenumberThe last byte of the object that was served in this response. 0 indicates a part of a byte-range response. This field is available only for Download Delivery products.
2050Security rulesstringReturns 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.
2052Server country/regionstringThe ISO code of the country or region from where the request was served.
2053Billing regionstringThe Akamai geographical price zone from where the request was served.
3000EdgeWorkers usagestringReturns 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].
3001EdgeWorkers executionstringReturns 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.
1082Custom fieldN/AThe data specified in the Custom Log Field of the Log Requests Details that you want to receive in the stream. See Custom log field.

Midgress traffic

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.