In addition to the list of variables you can log here in our docs, we all have the following variables available:
fastly_info.state: logging the value of this internal variable will report misses, passes, hits, hit-passes, whether a request waited for request collapsing or whether it clustered. This provides more specific information than
resp.http.X-Cache, which differentiates between only HITs and MISSes.
obj.hits: number of hits for an asset from a cache node (
server.identitywill then tell you the specific cache node that received the hit)
obj.lastuse: approximate time elapsed since the object was last accessed, specific to each cache node. Per our other community post here:
obj.lastuse works a bit differently in Fastly. Each edge node will have it’s own last accessed time. If the object is cached within the node, returned is the relative time in seconds since the object was last requested. If it is not cached, returned is
now-lastuse. Except that lastuse is 0 if the cache does not remember seeing the object.
time.elapsed: the time between the start of the request when it hits Fastly and when we deliver the first byte in the response