You can configure a stream to log various metrics called data set parameters or data set fields.

Depending on the log type you choose, you can select from parameters related to the request-response cycle, CDN health and performance metrics, and security data.

This includes data sets for midgress traffic within the ​Akamai​ platform, custom log fields, Reporting metrics and dimensions, and data for integrations with other products, such as EdgeWorkers, and fields from Log Delivery Service (LDS) available for EdgeDNS and Global Traffic Management.

To get a list of available parameters, run the List data set fields operation for each log type. For more information on the available stream types, see Log types.

Some fields may not be available depending on the product monitor or the log type (CDN, Edge DNS, EdgeWorkers, Global Traffic Manager) you choose. For example, Web security and EdgeWorkers information data set fields are not supported for the Cloud Wrapper products.

In JSON logs, fields reported as - or null are omitted by default. For the list of parameters and fields available for each log type, see the tables below. If you're looking for sample logs with actual data, see Log format.

Delivery fields

Here's the list of data set fields available for delivery (CDN) streams, for example, when you Create a CDN stream or Edit a CDN stream:

Data set field IDField nameData typeDescription
999Stream IDstringThe unique identifier of the stream that handled the request.
1000CP codestringThe Content Provider code associated with the request.
1002Request IDstringThe identifier of the request.
1005BytesintegerThe 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 codeintegerThe HTTP status code of the response.
1009Protocol typestringThe 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 portintegerThe client TCP port number of the requested service.
1015Response Content-LengthintegerThe 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 timeintegerThe 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.
1068Error codestringA string describing the problem with serving the request.
1100Request timeintegerThe time when the edge server accepted the request from the client.
1102Turn around timeintegerThe 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 timeintegerThe 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 timeintegerThe time in milliseconds between when the edge server accepts the connection and the completion of the SSL handshake.
2002TLS versionintegerThe protocol of the TLS handshake, either TLSv1.2 or TLSv1.3.
2003Object sizeintegerThe size of the object, excluding HTTP response headers.
2004Uncompressed sizeintegerThe size of the uncompressed object, if zipped before sending to the client.
2005Max-AgeintegerThe time in seconds that the object is valid for positive cache responses.
2006Overhead bytesintegerTCP overhead in bytes for the request and response, without HTTP or UDP overhead.
2007DNS lookup timeintegerThe time in seconds between the start of the request and the completion of the DNS lookup, if one was required.
2008Total bytesintegerThe 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 statusintegerReturns 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.
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.
2019CacheablestringReturns 1 if the object is cacheable based on response headers and metadata, 0 if the object is not cacheable.
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, 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.
2021Last byteintegerThe 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.
2022AsnumstringReturns a string with a single Autonomous System Number (ASN) or a colon-separated list of integers, if multiple ASNs are returned for the request's IP address.
2023File size bucketstringThis field groups the response content into different buckets by size in kilobytes, megabytes and gigabytes.
2024Edge attemptsintegerThe number of attempts to download the content from the edge in a specific time interval, based on the number of total manifest requests received.
2025Time to first byteintegerThe time taken to download the first byte of the received content in milliseconds.
2026Startup errorsintegerThe number of download initiation failures in a specific time interval.
2027Download timeintegerThe time taken to download the object in milliseconds.
2028ThroughputintegerThe byte transfer rate for the selected time interval in kilobits per second.
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.
2060Brotli statusstringThis 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.
2061Origin Content-LengthintegerThe 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.
2062Download InitiatedintegerThe number of successful download initiations in a specific time interval.
2063Download CompletedintegerThe number of complete successful downloads.
2080CMCDstringReturns 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.
2081Delivery typeintegerLimits logged data to a specific media delivery type, such as live, VOD (video on demand), or default:

3 - Download Delivery
2 - Adaptive Media Delivery VOD
1 - Adaptive Media Delivery Live
0 - default type
2082Delivery formatintegerReports 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:

4 - DASH
3 - SILVERLIGHT
2 - ZERI
1 - IPHONE
0 - default format
2083Media encryptionintegerReturns 1 if media encryption is enabled for the content delivered from the edge to the client.
2084Prefetch midgress hitsintegerReturns 1 if an edge server prefetched the content from a parent edge server other than the origin.
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.
3011Content protection informationstringReturns Enhanced Proxy Detection data, including the GeoGuard category, and the action EPD performed on the request. See Reporting metrics and dimensions for details.
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.

Edge DNS fields

When you Create an Edge DNS stream or Edit an Edge DNS stream, you can choose from the data set fields you may know from Log Delivery Service (LDS):

Data set field IDField nameData typeDescription
4002Epoch timestampstringThe Unix epoch timestamp of the log entry and its transaction.
4003DatestringThe UTC date for log entry and its transaction.
4004Resolver IPstringThe IP address of the DNS resolver making the request.
4005Request portintegerThe port number of the DNS resolver making the request.
4006Request namestringThe query name of the request.
4007ClassstringThe DNS class of the request.
4008Request typestringThe request's DNS record type.
4009EDNS0 flagstringThe EDNS0 Client Subnet (ECS) indicator, either E or blank.
4010EDNS0 sizeintegerThe ECS field size in bytes.
4011DNSSEC flagstringThe DNSSEC indicator, either D or blank.
4012TCP flagstringThe TCP indicator, either T or blank.
4013AnswersstringThe request answers for a request query name.
4014TimestringThe UTC time for log entry and its transaction.

EdgeWorkers fields

When you Create an EdgeWorkers stream or Edit an EdgeWorkers stream, each stream comes with the following fields by default. They correspond to the OpenTelemetry (OTel) format log fields:

Data set field IDField nameData typeDescription
6000TimestringThe Unix epoch timestamp when the event occurred, measured by the origin clock, i.e. the time at the source.
6001FormatintegerA version number that specifies the log line's format for accurate parsing. In case additional fields need to be added, the version number can be used to determine how to parse.

The initial value is 1.
6002DS2idintegerThe DataStream 2 stream ID. You can use this value for several operations such as Get a stream.
6003SeveritystringIndicates the event's severity level. For details on each status, check the Range name column in the OTel Logs Data Model guide.
6004TraceIdintegerThe request's trace ID as defined in W3C Trace Context. Returns - if not present.
6005SpanIdintegerThe span ID for logs that belong to a particular processing span.
6006TraceflagsstringThe request's trace flag, either SAMPLED or -.
6007ResourcestringDescribes the source of the logged event in a comma-delimited name and value pair.
6008AttributesstringAdditional information about the specific event occurrence. Can contain information about the request context in a comma-delimited name and value pair.
6009BodystringThe URL-encoded body of the log record, such as a human-readable string message describing the event in a free form or a structured data composed of arrays and maps of other values.

Global Traffic Management fields

When you Create a GTM stream or Edit a Global Traffic Management stream, you can choose from the data set fields you may know from Log Delivery Service (LDS):

Data set field IDField nameData typeDescription
5002Epoch timestampstringThe Unix epoch timestamp of the log entry and its transaction.
5003DatestringThe UTC date for log entry and its transaction.
5004Resolver IPstringThe IP address of the DNS resolver making the request.
5005Request portintegerThe port number of the DNS resolver making the request.
5006Request namestringThe query name of the request.
5007ClassstringThe DNS class of the request.
5008Request typestringThe request's DNS record type.
5009EDNS0 flagstringThe EDNS0 Client Subnet (ECS) indicator, either E or blank.
5010EDNS0 sizeintegerThe ECS field size in bytes.
5011DNSSEC flagstringThe DNSSEC indicator, either D or blank.
5012TCP flagstringThe TCP indicator, either T or blank.
5013AnswersstringThe request answers for a request query name.

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.