The Breadcrumbs response
The Breadcrumbs response header that's sent to a requesting app includes various sub-fields of data.
Sub-field key | Sub-field value | Details |
---|---|---|
|
| The IP address of the node/host currently processing the request. This can be an edge server or an origin. Note: If the node or host is not either of these two types, it's excluded. |
|
| A unique identifier assigned to the request. This helps Akamai support teams quickly pull the relevant log line in the request. |
|
| The number of milliseconds between the time the connection is accepted and the breadcrumb was gathered. This time includes the initial metadata parsing time, if metadata hadn't been loaded, as well as the metadata application time for this request, if they occurred between request acceptance and generation of the breadcrumb. |
|
| The time in milliseconds between receipt of the end of the request headers and when the breadcrumb was gathered. This includes the time it takes to fetch the object from another server in the case of a miss, or to perform (synchronous) validation of the object's freshness if the object was in cache. In both of these cases, there's a forward request corresponding to the client request. This time also may include the time to fetch the object from disk, perform ESI processing, and compute response headers. |
|
| The delta between the start of the request and the completion of the DNS lookup. |
|
| Geographic detailsfor the node or host currently processing the request. |
|
| The autonomous system number of the current node or host. |
|
| These are letter identifiers for the Akamai network component that was involved during that phase of the request. Your Akamai account representative can use this value to determine where in the request phase the breadcrumb was gathered. Component letters include the following:
|
Example 1: When served from within Akamai
In this example, the request flow is Edge to Peer. So, the Breadcrumbs format would be in this order, with each enclosed in brackets, and separated with commas:
- Edge:
[{component-ip},{request-id},{component-letter},{component-geo},{component-asn}]
- Peer:
[{component-letter},{component-geo},{component-asn}]
:
[a=12.34.567.89,b=12345678,c=g,n=US_CA_SANJOSE,o=20940],[c=p,n=US_CA_SANJOSE,o=55155]
Example 2: When served from an origin
In this example, the request flow is Edge to Cache to Origin. So, the Breadcrumbs format would be in this order, with each enclosed in brackets, and separated with commas:
- Edge:
[{component-ip},{request-id},{component-letter},{component-geo},{component-asn}]
- Cache:
[{component-letter},{component-geo},{component-asn}]
- Origin:
[{component-ip},{component-letter}]
[a=12.34.567.89,b=12345678,c=g,n=US_CA_SANJOSE,o=20940],[c=c,n=US_CA_SANJOSE,o=55155],[a=987.654.321.09,c=o]
Updated 29 days ago